Meta tags:
description=A curated database of agent-readable skills for building on the Internet Computer (ICP). Each skill captures correct dependency versions, configuration formats, and common pitfalls that prevent build failures. Maintained by DFINITY.;
author=DFINITY Foundation;

Headings (most frequently used words):

skills, that, make, agents, actually, good, at, the, internet, computer, auth, cloudengine, core, defi, frontend, governance, infrastructure, integration, motoko, security, ecosystem,

Text of the page (most frequently used words):
the (112), use (81), for (74), canister (72), and (71), icp (46), when (40), read (36), json (35), not (33), markdown (33), #motoko (32), skills (30), with (30), internet (24), identity (23), covers (22), from (20), cli (19), app (18), cycles (18), canisters (17), engine (17), via (16), skill (16), calls (15), icrc (15), computer (14), custom (14), project (14), agent (14), user (13), that (13), code (13), vetkeys (12), instead (12), migration (12), data (11), frontend (11), chain (11), writing (11), web (11), deploy (11), static (10), files (10), wallet (10), integration (9), encrypted (9), caffeine (9), domain (9), sdk (8), build (8), rust (8), access (8), mops (8), one (8), gateway (8), evm (8), sign (8), cloud (8), proxy (8), api (7), key (7), building (7), any (7), certified (7), http (7), site (7), patterns (7), upgrade (7), stable (7), well (7), domains (7), https (7), token (7), deploying (7), signer (7), ckbtc (7), dfinity (6), liquidium (6), errors (6), deployment (6), you (6), email (6), smtp (6), known (6), management (6), configuration (6), time (6), link (6), this (6), btc (6), bitcoin (6), setup (5), derivation (5), only (5), subnet (5), assets (5), cycle (5), inter (5), existing (5), legacy (5), migrations (5), how (5), file (5), adding (5), through (5), into (5), outcalls (5), sns (5), make (5), ethereum (5), rpc (5), toml (5), asks (5), balance (5), hook (5), service (5), transfers (5), console (5), readable (4), txt (4), your (4), encryption (4), bls (4), implementing (4), signing (4), keys (4), storage (4), are (4), query (4), using (4), security (4), control (4), state (4), pitfalls (4), architecture (4), actors (4), types (4), yaml (4), load (4), non (4), actor (4), never (4), call (4), apis (4), ledger (4), versions (4), multi (4), auth (4), login (4), wants (4), always (4), manage (4), working (4), top (4), dapp (4), flows (4), its (4), mainnet (4), latest (4), governance (4), recipe (4), asset (4), dns (4), mcp (4), manifest (4), opencloud (4), llms (3), based (3), verified (3), ibe (3), threshold (3), signatures (3), timelock (3), principal (3), authentication (3), library (3), under (3), responses (3), response (3), certification (3), certificate (3), validation (3), verification (3), specific (3), pattern (3), compiler (3), design (3), review (3), reviewing (3), persistence (3), remove (3), migrating (3), over (3), new (3), requests (3), protocol (3), raw (3), must (3), inbound (3), interface (3), sending (3), org (3), metadata (3), network (3), external (3), needs (3), scratch (3), backend (3), install (3), check (3), dependency (3), setting (3), lifecycle (3), level (3), memory (3), creation (3), buy (3), card (3), installer (3), plus (3), installed (3), wasm (3), knowledge (3), automatically (3), dao (3), nns (3), general (3), operator (3), oisy (3), withdrawal (3), across (3), upgrades (3), wait (3), deployed (3), cloudengine (3), sso (3), formats (3), maintained (2), apache (2), foundation (2), add (2), inc (2), flow (2), lending (2), client (2), own (2), ecosystem (2), vetkd (2), public (2), deriving (2), transport (2), calling (2), controlled (2), value (2), password (2), notes (2), maps (2), end (2), backends (2), side (2), shared (2), per (2), serve (2), frontends (2), automatic (2), async (2), handling (2), protection (2), makes (2), language (2), syntax (2), persistent (2), core (2), mixins (2), common (2), fixing (2), generating (2), commands (2), reference (2), compatibility (2), cannot (2), explain (2), write (2), first (2), oldactor (2), empty (2), converted (2), directory (2), revert (2), inline (2), rules (2), what (2), troubleshooting (2), fields (2), structure (2), main (2), schema (2), including (2), frozen (2), projects (2), receive (2), mail (2), bounces (2), actually (2), arrives (2), headers (2), sender (2), crate (2), optional (2), candid (2), rest (2), dashboard (2), internetcomputer (2), replicated (2), consensus (2), both (2), pay (2), ic0 (2), limits (2), generic (2), scaffold (2), single (2), dfx (2), toolchain (2), pinning (2), checking (2), running (2), moc (2), configuring (2), tool (2), bundling (2), self (2), mentions (2), local (2), like (2), freezing (2), human (2), name (2), help (2), but (2), generated (2), then (2), exchange (2), account (2), hold (2), keeps (2), current (2), sets (2), sessionstart (2), script (2), against (2), applies (2), each (2), bootstrap (2), enable (2), stop (2), version (2), pastes (2), action (2), ongoing (2), questions (2), claude (2), sync (2), after (2), session (2), configure (2), launch (2), spa (2), routing (2), apps (2), ids (2), host (2), hosting (2), publishing (2), origin (2), before (2), making (2), register (2), update (2), without (2), integrate (2), popup (2), ledgers (2), balances (2), approve (2), minting (2), deposit (2), stablebtreemap (2), bounded (2), unbounded (2), cross (2), delegation (2), get (2), attach (2), free (2), their (2), push (2), notifications (2), correct (2), prevent (2), failures (2), works (2), agents (2), machine, rss, sitemap, full, source, licensed, icskills, github, npx, authless, instant, loan, market, profile, liquidiumclient, instantloans, accounts, positions, quote, modules, community, reviewed, risk, cryptography, system, libraries, symmetric, offline, encrypting, sealed, bid, schemes, vetkd_public_key, vetkd_derive_key, managers, encryptedmaps, values, between, principals, rights, readwrite, readwritemanage, manager, secure, vault, stores, shares, start, here, escalate, cryptographically, merkle, trees, rbtree, certtree, construction, witness, generation, http_request, need, authenticity, proofs, served, there, variables, development, anonymous, rejection, reentrancy, prevention, callerguard, safety, saga, callback, trap, drain, safe, modifying, modifies, handles, tokens, implements, modern, standard, dot, notation, compilation, audit, deep, misbehaves, whose, request, delete, seeing, judging, whether, designed, invariants, encoded, variants, text, correlated, case, smells, transient, discipline, enhanced, lib, severity, ranked, findings, blocker, warning, note, auditing, critiquing, refactoring, asked, feedback, authoring, evolution, managed, timestamped, upgrading, changing, field, renaming, deciding, implicit, explicit, shot, changes, unexplained, diagnostics, smtp_request, smtp_request_validate, addressing, icp0, handing, another, turns, reply, codes, 5xx, everything, else, retries, 550, rejects, recipient, mime, body, attempt, message_id, chunked, upload, messages, mib, process, retried, serving, power, metrics, cursor, pagination, fetching, info, proposals, stats, off, needed, flexible, transform, functions, pricing, cost_http_request_v2, size, idempotency, fetch, choose, pricing_version, flexible_http_request, chains, evm_rpc_client, typed, provider, erc, reads, pre, signed, transactions, arbitrum, base, optimism, complete, layout, workspace, manifests, react, vite, loop, doctor, fix, preview, whenever, create, set, about, workflow, even, they, say, words, pair, type, linting, lock, removing, packages, lintoko, flags, guides, command, line, applications, recipes, environments, contained, package, bundle, managing, packaging, programming, checks, ups, thresholds, conversion, cmc, funding, out, display, summary, given, did, directly, credit, cyclepay, continue, fails, lack, has, stripe, fiat, usd, converting, already, mint, topping, compares, release, either, reports, whichever, channel, was, npm, homebrew, shell, updates, outdated, other, usage, those, keep, date, mirrors, published, runs, every, coding, themselves, configures, auto, updating, infrastructure, decentralize, economics, parameters, testflight, proposal, submission, decentralization, swap, launching, tokenomics, config, _redirects, csp, _headers, clean, urls, private, recommended, way, also, entry, point, json5, see, discoverable, just, url, real, presync, envsubst, exposing, getapidoc, method, behavior, oql, execute, surface, opts, itself, acceptance, terms, confirm, ready, available, discovery, consume, discoverability, record, cname, acme, challenge, registration, deletion, tls, provisioning, httpagent, boundary, nodes, troubleshoot, issues, relying, party, standards, picking, redirect, 167, browser, extension, negotiating, capabilities, permission, executing, approves, signeragent, uses, worked, example, yourself, developer, approving, transaction, interact, cketh, transferfrom, allowances, fee, allowance, fungible, accept, send, minter, subaccount, utxo, integrating, deposits, withdrawals, plain, defi, persist, memorymanager, dealing, lost, pre_upgrade, traps, heap, dapps, factory, messaging, 2mb, payload, splitting, designing, communication, deploys, built, defaults, handoff, sandboxes, run, tag, __meta_, named, bake, git, sha, rates, owner, paid, subfolder, shipping, mention, linking, completes, sandbox, naming, versioning, giving, icon, funded, which, failing, proxied, logic, computed, drop, clauses, ic0504, timeout, bounded_wait, rejected, allowed, subnets, ordinary, wrapper, replicas, had, different, insufficientcycles, xrc, ecdsa, schnorr, sol, ask, hand, encode, arguments, cdk, helpers, derived, belong, planning, debugging, these, passkey, openid, google, apple, microsoft, organization, getssostatus, attributes, sessions, subdomains, alternative, origins, document, consent, list, passkeys, lets, act, com, log, powered, obtain, authorized, behalf, contain, prefer, guidance, cover, same, topic, license, categories, give, curated, database, captures, can, ship, guessing, good, humans, who, direct, them, started, skip, content,

Text of the page (random words):
et started a library for agents and the humans who direct them skills that make agents actually good at the internet computer a curated database of skill files each one captures correct dependency versions configuration formats and the pitfalls that prevent build failures an agent can load it ship working code and stop guessing give your agent icp skills read how it works 33 skills 10 categories 3 formats skill apache 2 0 license skills contain correct dependency versions configuration formats and common pitfalls that prevent build failures always prefer skill guidance over general knowledge when both cover the same topic icp skills protocol llms txt auth 2 skills agent web identity sign in lets an ai agent or cli session sign in to internet identity and act as a user s app specific principal e g for oisy com or nns ic0 app via icp identity link web use when the user asks an agent to log in to an ii powered app obtain a delegation or make authorized canister calls on their behalf do not use for adding ii sign in to a frontend use the internet identity skill instead read markdown json internet identity integrate internet identity authentication covers passkey openid google apple microsoft and organization sso sign in with icp sdk auth the sso domain check getssostatus identity attributes verified email name and their backend verification sessions shared across subdomains alternative origins the well known ii app metadata document and web push notifications consent the sender list and sending from a motoko or rust canister use when adding sign in login auth passkeys sso notifications web push or internet identity to a frontend or canister do not use for wallet integration or icrc signer flows use wallet integration or for an agent or cli signing in as a user use agent web identity read markdown json cloudengine 2 skills 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 bounded_wait 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 insufficientcycles xrc threshold ecdsa schnorr vetkd the bitcoin api and evm sol rpc bitcoin ethereum vetkeys go via the engine s proxy canister before writing that code ask the user for its id or to deploy one in the console hand encode arguments ic vetkeys and ic cdk chain key helpers attach cycles derived keys belong to the proxy use when planning writing or debugging engine canister code signing or deriving keys or on these errors do not use for deploying a proxy deploy to cloud engine read markdown json deploy to cloud engine deploys a built internet computer project to a cloud engine opencloud link the console identity with icp identity link web defaults to https opencloud org a delegation handoff covers sandboxes run icp deploy on the engine s subnet tag canisters with __meta_ for a named console app bake version metadata service git sha into the wasm and get the proxy an app needs for bitcoin ethereum signing vetkeys or exchange rates deployed by the engine owner in the console and paid from the engine s balance or self deployed icp new subfolder proxy use when shipping to a cloud engine on mention of opencloud an engine subnet id or linking the icp cli when sign in never completes from a sandbox when naming versioning or giving an icon to a console app when a proxy must be deployed or funded or which balance to top up engine proxy failing proxied calls cloud engine canisters do not use for a mainnet deploy with no engine icp cli or canister logic cloud engine canisters read markdown json core 2 skills multi canister architecture design and deploy multi canister dapps covers inter canister calls canister factory pattern async messaging pitfalls bounded vs unbounded wait and 2mb payload limits use when splitting an app across canisters making inter canister or cross canister calls or designing canister to canister communication do not use for single canister apps read markdown json stable memory upgrades persist canister state across upgrades covers stablebtreemap and memorymanager in rust persistent actor in motoko and upgrade hook patterns use when dealing with canister upgrades data persistence data lost after upgrade stable storage stablebtreemap pre_upgrade traps or heap vs stable memory do not use for inter canister calls or access control use multi canister or canister security instead read markdown json defi 3 skills ckbtc chain key bitcoin 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 read markdown json icrc token ledgers deploy and interact with icrc 1 icrc 2 token ledgers icp ckbtc cketh covers transfers balances approve transferfrom allowances fee handling and ledger deployment use when working with icp transfers token transfers balances icrc 1 icrc 2 approve allowance or any fungible token on ic do not use for ckbtc minting or btc deposit withdrawal flows use ckbtc instead read markdown json 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 the internet identity skill or for implementing a wallet yourself use when the developer mentions wallet integration or oisy or icp sdk signer or approving a transaction in a wallet popup read markdown json frontend 3 skills custom domains register and manage custom domains for ic canisters via the http gateway custom domain service covers dns record configuration cname txt acme challenge the well known ic domains file domain registration validation update deletion via the rest api tls certificate provisioning and httpagent host configuration use when the user wants to serve a canister under a custom domain configure dns for ic register a domain with boundary nodes troubleshoot custom domain issues or update remove a custom domain do not use for general frontend hosting or asset static site canister configuration without custom domains use static site instead read markdown json 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 icp mcp and is itself the operator s acceptance of the icp mcp app operator terms so confirm with the app s operator before deploying it use when making an app agent ready or available through icp mcp for agent service discovery the well known ic architecture manifest or generating that manifest at deploy time do not use for the sign in flows that consume the derivation origin use agent web identity for the agent cli web identity link or internet identity for adding ii login to a frontend read markdown json static site certified assets 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 for migrating an existing asset canister to certified assets use when hosting a frontend deploying static files an asset canister or setting up spa routing on the ic do not use for canister level http code patterns or custom domain dns setup use custom domains for dns read markdown json governance 1 skill sns dao launch configure and launch an sns dao to decentralize a dapp covers token economics governance parameters testflight validation nns proposal submission and decentralization swap use when launching an sns configuring tokenomics or setting up dao governance for a dapp do not use for nns governance or general canister management read markdown json infrastructure 7 skills automatically sync latest ic skills one time installer that makes a claude code project keep its internet computer skills up to date automatically sets up a sessionstart hook plus a sync script so claude skills always mirrors the latest skills published at skills internetcomputer org use when a user wants to install bootstrap or enable always latest internet computer ic icp motoko skills in a project or pastes the link to this skill this is a one time setup action not ongoing ic knowledge after it runs the installed hook keeps skills current on every session do not use for ic coding questions themselves this only configures auto updating skills read markdown json automatically upgrade the 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 version of the icp cli or pastes the link to this skill this is a one time setup action not ongoing ic knowledge do not use for writing icp yaml deploying canisters or other icp cli usage questions load icp cli for those read markdown json buy cycles with a card 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 web identity read markdown json canister help 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 read markdown json 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 read markdown json icp cli guides use of the icp command line tool for building and deploying internet computer applications covers project configuration icp yaml recipes environments canister lifecycle identity management and bundling a project into a self contained icp package icp project bundle use when building deploying or managing any ic project use when the user mentions icp dfx canister deployment local network project setup or bundling packaging an app as an icp file do not use for canister level programming patterns like access control inter canister calls or stable memory use domain specific skills instead read markdown json mops cli manage motoko projects with the mops cli toolchain pinning dependency management type checking building and linting use when working with mops toml mops lock running mops commands adding removing packages pinning moc or lintoko versions checking or building canisters configuring moc flags or setting up a new motoko project read markdown json integration 5 skills caffeine app build from scratch scaffold and build a complete caffeine app caffeine ai from scratch the project layout the caffeine toml workspace canister manifests the mops toml for the single motoko backend canister the react vite frontend and the caffeine cli build loop auth login doctor install check fix preview build use whenever the user wants to create scaffold set up or build a caffeine app or a caffeine ai project asks about caffeine toml or mops toml structure or needs the caffeine cli workflow even if they do not say the words from scratch always pair it with the writing motoko skill for the backend code do not use it for motoko language syntax or compiler errors use the writing motoko skill and do not use it for generic internet computer dfx icp deployment use the icp cli skill read markdown json evm rpc call ethereum and evm chains from ic canisters rust via the evm rpc canister using the evm_rpc_client crate covers typed api calls raw json rpc multi provider consensus erc 20 reads and sending pre signed transactions use when calling ethereum arbitrum base optimism or any evm chain from a rust canister do not use for generic https calls to non evm apis use https outcalls instead read markdown json 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 cost_http_request_v2 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 pricing_version or use flexible_http_request do not use for evm ethereum calls use evm rpc instead read markdown json ic dashboard apis 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 read markdown json smtp gateway inbound email receive email in an internet computer canister through the smtp gateway protocol covers implementing smtp_request ...