dfinity · Agent Skills
17 Skill con documentazione sostanziale e fonti verificate. Apri una scheda per leggere le istruzioni originali e verificare pacchetto e installazione.
autoupgrade-icp-cli
One-time installer that keeps a project's Internet Computer CLI toolchain current. Sets up a SessionStart hook plus a script that compares the installed icp and ic-wasm against the latest release and either reports the upgrade or applies it, using whichever channel each tool was installed from (npm, Homebrew, or the shell installer). Use when a user wants to install, bootstrap, or enable automatic icp-cli / ic-wasm updates, asks to stop running an outdated icp, asks how to upgrade or check the v
- Installazioni / 1h
- 1
- GitHub Stars
- 39
- Aggiornato
- 11 nov
buy-cycles
Buy cycles with a credit card for the CLI's own identity with icp cycles buy, through CyclePay's on-chain gateway, then continue deploying. Use when a mainnet deploy or canister creation fails for lack of cycles, the user has no ICP, no wallet or no exchange account, or asks to pay for cycles by card, Stripe, fiat or USD. Do NOT use for converting ICP you already hold (cycles-management: icp cycles mint), for topping up a canister from an existing balance, or for Internet Identity sign-in (agent
- Installazioni / 1h
- 1
- GitHub Stars
- 39
- Aggiornato
- 11 nov
canhelp
Display a human-readable summary of a canister's interface given its mainnet canister ID or a human-readable name. Like --help but for canisters. Only for mainnet canisters — for local canisters, read the generated .did file in your project directly.
- Installazioni / 1h
- 1
- GitHub Stars
- 39
- Aggiornato
- 11 nov
canister-security
IC-specific security patterns for canister development in Motoko and Rust. Covers access control, anonymous principal rejection, reentrancy prevention (CallerGuard pattern), async safety (saga pattern), callback trap handling, cycle drain protection, and safe upgrade patterns. Use when writing or modifying any canister that modifies state, handles tokens, makes inter-canister calls, or implements access control.
- Installazioni / 1h
- 1
- GitHub Stars
- 39
- Aggiornato
- 11 nov
ckbtc
Accept, send, and manage ckBTC (chain-key Bitcoin). Covers BTC deposit flow via minter, ckBTC transfers, withdrawal to BTC, subaccount derivation, and UTXO management. Use when integrating Bitcoin, ckBTC, BTC deposits, or BTC withdrawals in a canister. Do NOT use for plain token transfers without BTC minting/withdrawal — use icrc-ledger instead.
- Installazioni / 1h
- 1
- GitHub Stars
- 39
- Aggiornato
- 11 nov
cloud-engine-canisters
Rules for canister code on a cloud engine (CloudEngine subnet, e.g. OpenCloud). Engine canisters hold 0 cycles: never attach cycles you computed: drop (with cycles = …) clauses (IC0504). Cross-subnet calls must be bounded-wait and cycle-free ((with timeout = N), Call::boundedwait) or rejected: 'Unbounded-wait calls and calls with cycles are not allowed to CloudEngine subnets'. HTTPS outcalls use the ordinary wrapper and are free; never via the proxy ('Replicas had different responses', Insuffici
- Installazioni / 1h
- 1
- GitHub Stars
- 39
- Aggiornato
- 11 nov
cycles-management
Manage cycles and canister lifecycle. Covers cycle balance checks, top-ups, freezing thresholds, canister creation, and ICP-to-cycles conversion via the CMC. Use when working with cycles, canister funding, freezing threshold, frozen canister, out of cycles, top-up, canister creation, or cycle balance. Do NOT use for wallet-to-dApp integration or ICRC signer flows — use wallet-integration instead.
- Installazioni / 1h
- 1
- GitHub Stars
- 39
- Aggiornato
- 11 nov
deploy-to-cloud-engine
Deploys a built Internet Computer project to a cloud engine (OpenCloud). From a sandboxed chat or cloud session with the ICP MCP connector (ChatGPT, Claude, https://mcp.internetcomputer.org/mcp): install the wasm through the engine-operator's proxy. Otherwise with the icp CLI: icp identity link web (defaults to https://opencloud.org), icp deploy on the engine's subnet. Also: META for a named console app, version metadata (service:git:sha), and the proxy canister for Bitcoin/Ethereum signing, Vet
- Installazioni / 1h
- 1
- GitHub Stars
- 39
- Aggiornato
- 11 nov
encrypted-maps
Add access-controlled, end-to-end encrypted key-value storage to a canister with the vetKeys EncryptedMaps library (ic-vetkeys for Rust and Motoko backends, @icp-sdk/vetkeys for the frontend). Values are encrypted client-side under vetKeys and shared between principals with per-user access rights (Read, ReadWrite, ReadWriteManage). Use when building a password manager, encrypted notes, a secure vault, or any app that stores and shares encrypted data on-chain. Start here for encrypted storage; es
- Installazioni / 1h
- 1
- GitHub Stars
- 39
- Aggiornato
- 11 nov
https-outcalls
Make HTTPS requests from canisters to external web APIs. Covers replicated, non-replicated and flexible outcalls, transform functions for consensus, both cycle pricing versions (legacy and pay-as-you-go via ic0.costhttprequestv2), response size limits, and idempotency patterns. Use when a canister needs to call an external API, fetch data from the web, make HTTP requests, choose a pricingversion, or use flexiblehttprequest. Do NOT use for EVM/Ethereum calls — use evm-rpc instead.
- Installazioni / 1h
- 1
- GitHub Stars
- 39
- Aggiornato
- 11 nov
ic-dashboard
Query the public REST APIs that power dashboard.internetcomputer.org. Covers canister metadata, ICRC ledger data, SNS data, ICP ledger, and network metrics with cursor-based pagination. Use when fetching canister info, token data, SNS proposals, or network stats via HTTP from off-chain code. No canister deployment or cycles needed.
- Installazioni / 1h
- 1
- GitHub Stars
- 39
- Aggiornato
- 11 nov
organization-sign-in
Set up an organization's own single sign-on for Internet Identity, so staff sign in to II-powered apps against Okta, Entra ID, Google Workspace or Auth0. Nothing registers with II: it discovers the configuration from /.well-known/ii-openid-configuration on the organization's domain. Covers the OIDC client, the discovery file and every field, per-app clients including salted-hash keys, gateallapps, stableidentifierclaim, the limits that reject the whole file, and II's caching windows. Use when an
- Installazioni / 1h
- 1
- GitHub Stars
- 39
- Aggiornato
- 11 nov
service-discoverability
Make a canister app discoverable to an AI agent from just its URL, including through ICP MCP. Covers publishing a /.well-known/ic-architecture manifest of your canisters — generated at deploy time from real canister IDs via the static-site recipe's presync hook and envsubst — plus exposing candid:service (interface), a getApiDoc query method (behavior), an optional OQL schema/execute data surface, and a /.well-known/ii-derivation-origin file (identity). Publishing that manifest opts the app into
- Installazioni / 1h
- 1
- GitHub Stars
- 39
- Aggiornato
- 11 nov
static-site
Deploy a frontend or any static site to the IC with the @dfinity/static-site recipe (the certified-assets canister). Covers icp.yaml recipe config, SPA routing with redirects, custom headers/CSP with headers, clean URLs, access protection for private apps, custom domains, and building against canister IDs. This is the recommended way to host frontends and static files on the IC. Also the entry point for the legacy @dfinity/asset-canister recipe and .ic-assets.json5 (see the legacy reference) and
- Installazioni / 1h
- 1
- GitHub Stars
- 39
- Aggiornato
- 11 nov
troubleshooting-motoko-migrations
Deep reference for when the Motoko migration chain misbehaves — upgrade compatibility errors you cannot explain, migration files you cannot write, a first migration whose OldActor is non-empty, a project converted from legacy persistence, or a request to delete/remove the migrations directory or revert to inline (with migration = ...). Load only when the rules in migrating-motoko-actors do not explain what you are seeing.
- Installazioni / 1h
- 1
- GitHub Stars
- 39
- Aggiornato
- 11 nov
wallet-integration
Integrate an external wallet (signer) into an IC dapp with @icp-sdk/signer — the relying-party side of the ICRC signer standards. Covers picking a transport (popup via ICRC-29 / top-level redirect via ICRC-167 / browser extension via ICRC-94) then negotiating capabilities, the permission and account lifecycle, and executing canister calls the user approves through SignerAgent (ICRC-49). Uses OISY as the worked example but applies to any ICRC-25 signer. Do NOT use for Internet Identity login (use
- Installazioni / 1h
- 1
- GitHub Stars
- 39
- Aggiornato
- 11 nov
writing-motoko
Motoko language pitfalls, modern syntax, and architecture patterns for the Internet Computer. Covers persistent actors, stable types, mo:core standard library, dot notation, mixins, and common compilation errors. Use when writing Motoko canister code, fixing Motoko compiler errors, or generating Motoko actors. Do NOT use for deployment, icp.yaml, or CLI commands; for design review or audit of existing Motoko code, load reviewing-motoko instead.
- Installazioni / 1h
- 1
- GitHub Stars
- 39
- Aggiornato
- 11 nov