cyhole

Use this skill when implementing a new crypto API Interaction in the cyhole library. Trigger whenever the user says "add a new interaction", "implement [API name] interaction", "integrate [API name]", "create [API name] connector", or similar requests to wrap a new external crypto/blockchain API. Also trigger when the user provides an API documentation URL and asks to connect it to cyhole. This skill enforces all cyhole conventions (file structure, naming, overload pattern, tests, docs) and prevents duplicate work. Do NOT skip this skill even for "simple" single-endpoint APIs — the conventions must be applied consistently.

Use this skill when updating an existing cyhole Interaction to reflect API changes. Trigger whenever the user says "update [API name] interaction", "[API name] API changed", "add endpoint to [API name]", "remove deprecated endpoint from [API name]", "[API name] now requires an API key", "sync [API name] with latest docs", or similar requests to evolve an already-implemented Interaction. Also trigger when the user provides a new documentation URL for an API that is already in cyhole. Do NOT skip this skill even for "small" changes like adding one endpoint or updating one schema — conventions must be applied consistently.

Use when creating any git commit - enforces structured commit messages with a 3-letter action code, title, and description following the project convention

Use when new functionality requires documentation, existing docs need updating after feature changes, documentation must be created or reorganized in the docs/ folder, or when a significant system behavior or data flow changes