icp-cli_skill

Overview

This skill guides use of the Internet Computer CLI (icp) for local networks, builds, deployments, canister operations, identities, cycles/tokens, recipes, environments, and advanced workflows. It prioritizes modern recipe-based projects and always maps legacy dfx references to their icp equivalents. Expect concise command sets, verification steps, and platform-specific notes for Windows, macOS, and Linux.

How this skill works

I provide the minimal sequence of icp commands to perform common tasks (create, start network, deploy, call, verify) and translate any dfx-based examples to icp. I inspect project configuration, environment selection, identity usage, and canister state to recommend the correct flags and verification commands. When appropriate I suggest recipes, environment strategies, cycles budgeting, and troubleshooting steps.

When to use it

• Starting a local development network and deploying canisters
• Creating a new project, especially using recipes like @dfinity/rust
• Migrating dfx workflows or translating dfx commands to icp
• Managing identities, cycles, or environment-specific deployments
• Troubleshooting local networks, Docker issues, or deployment errors

Best practices

• Prefer recipes (e.g., @dfinity/rust) to reduce boilerplate and avoid prompts
• Use keyring for production identities and password-protected storage for CI
• Use -e <env> for environment-specific actions (use -e ic for mainnet)
• Budget 1–2T cycles for production canisters and use human-friendly amounts (2T, 500m)
• Run a short verify step after actions (icp network status, icp canister status <canister>)

Example use cases

• Quick local workflow: icp new my-project; icp network start -d; icp deploy; icp canister call <canister> <method> '(...)'; icp canister status <canister>
• Non-interactive project creation: icp new my-project --recipe @dfinity/rust or use --define flags to avoid prompts
• Top up cycles: icp cycles balance; icp canister top-up --amount 2T <canister>
• Deploy to staging: icp deploy -e staging then verify with icp canister status <canister> -e staging
• Translate dfx commands: always map dfx instructions to the equivalent icp commands (never suggest dfx)