Proposal: canister-calls skill — Candid discovery + consolidated canister workflows

[marc0olo]

Summary

Proposal for a canister-calls skill that consolidates canister interaction into a single entry point, based on the idea that Candid is to canisters what --help is to CLIs.

• Main SKILL.md teaches agents how to discover any canister's API via Candid (fetch .did, read types, generate bindings, call)
• Reference files provide curated workflows for well-known infrastructure canisters where raw Candid alone isn't enough (multi-step flows, fees, pitfalls)
• Includes evaluation file with 9 output evals and trigger evals

Structure

skills/canister-calls/
├── SKILL.md                        # Lean router (~130 lines)
└── references/
    ├── ckbtc.md                    # BTC deposit/withdrawal workflows
    ├── icrc-ledger.md              # ICRC-1/2 token transfers
    └── evm-rpc.md                  # Ethereum/EVM JSON-RPC proxy

Open questions

• Should this supersede the standalone ckbtc, icrc-ledger, and evm-rpc skills, or coexist?
• Initial trigger evals show the dedicated skills win when both exist (more specific descriptions). Removing the dedicated skills would make canister-calls the single entry point.

cc @gregorydemay — this builds on your suggestion for a generic canister interaction skill. Feel free to adopt, modify, or drop any of this.

[gregorydemay]

@marc0olo : Thanks for the draft! My suggestion is actually more radical:

1. Build a skill to learn how to talk to a canister, like --help for CLIs. This is feat: --help for canisters #89
2. Remove all the "skills" regarding specific canisters, like the one that were moved in this PR as references.