Skills
19 skills, listed alphabetically. Each is a standalone Markdown file under skills/ in the repo. The agent loads only name + description for discovery; the full SKILL.md loads when the skill is selected.
| Skill | What it does |
|---|---|
assess-constitutionality | Assesses whether a Cardano governance action complies with the Constitution: a live on-chain action, a signed or unsigned transaction before submission, or a draft. Produces a provision-by-provision findings report against the mirrored constitutional text. Triggers: “is this governance action constitutional”, “assess constitutionality”, “constitutional review”, “check this proposal against the Constitution”, “will this treasury withdrawal pass CC review”, “review my governance action draft”, “check my governance action before I submit”, “check this unsigned transaction”, “constitutional defects”. |
build-transaction | Build Cardano transaction, send ADA, mint NFT, mint token, interact with smart contract, delegate stake, register DRep, vote on-chain using Mesh SDK, Evolution SDK, PyCardano, cardano-client-lib, or Haskell cardano-ledger (Aiken CIP-57 + haskell.nix + CHaP). |
cardano-context | Enable durable Cardano development context in a project for Claude Code and Codex by installing one shared directive into CLAUDE.md and AGENTS.md. Trigger phrases: “enable cardano context”, “set up cardano for this project”, “configure claude and codex for cardano”, “mark this as a cardano project”, “cardano-context”. |
connect-wallet | Guides integrating a Cardano wallet into a web dApp using CIP-30. Triggers: “connect wallet”, “CIP-30”, “wallet integration”, “browser wallet”, “sign transaction”, “wallet connector”, “dApp wallet”, “Nami”, “Eternl”, “Lace”. |
debug-transaction | Debug failing Cardano transaction, fix transaction error, diagnose ValueNotConservedUTxO, InsufficientCollateral, script failure, budget exceeded, datum mismatch, missing signer, min-UTxO error. |
design-token | Design Cardano native token, NFT, NFT collection, fungible token, CIP-25 metadata, CIP-68 reference tokens, CIP-113 programmable tokens, minting policy, token architecture. |
explain-cip | Explain Cardano Improvement Proposals (CIPs) to developers. Trigger phrases: “explain CIP”, “what is CIP-30”, “CIP-68 metadata”, “what CIP covers”, “which CIP for wallets”, “governance CIP”, “token metadata standard”. |
explain-eutxo | Explain Cardano’s extended UTxO model to developers. Trigger phrases: “explain datum”, “what is a redeemer”, “eUTxO vs account model”, “how do validators work”, “what is a script context”, “UTxO model”, “how does Cardano differ from Ethereum”. |
explain-zk | Zero-knowledge and the BLS12-381 primitive family on Cardano: verify SNARK proofs on-chain, aggregate BLS signatures, run VRFs, derive keys, and check BBS+ credentials in Aiken. Triggers: “explain zero-knowledge”, “ZK on Cardano”, “verify a SNARK on-chain”, “Groth16 in Aiken”, “zk-SNARK verifier”, “BLS signatures in Aiken”, “aggregate signatures”, “VRF on Cardano”, “verifiable randomness”, “BBS+ / selective disclosure”, “anonymous credentials”, “range proof”, “Bulletproofs”, “prove knowledge without revealing it”. |
give-feedback | Send feedback about cardano-dev-skills itself to its maintainers as a GitHub issue: a bundled skill or doc that was wrong, stale, confusing, or missing something, a prompt that should have triggered a skill but didn’t, or a skill that saved real time. Drafts the issue from the current context, scrubs secrets, asks once, then files it with gh. Trigger phrases: “give feedback”, “send feedback”, “report this skill”, “this doc is wrong”, “that skill is stale”, “feedback to cardano-dev-skills”, “/cardano-dev-skills:give-feedback”, “$give-feedback”. |
governance-guide | Guides Cardano on-chain governance under CIP-1694 and the Conway era. Triggers: “governance”, “DRep”, “CIP-1694”, “Conway era”, “governance action”, “vote on proposal”, “constitutional committee”, “treasury withdrawal”, “GovTool”. |
optimize-validator | Optimize Aiken validators for lower execution costs and smaller script size. Covers CPU/memory reduction, script size, data structures, and benchmarking. Trigger: “optimize validator”, “reduce script size”, “lower execution cost”, “reduce CPU”, “reduce memory”, “script too large”, “transaction too expensive”. |
query-chain | Guides finding the best way to query Cardano blockchain data. Triggers: “query chain”, “read UTxOs”, “fetch blockchain data”, “Blockfrost vs Ogmios”, “chain indexer”, “query Cardano”, “get transaction data”, “read on-chain state”, “query chain from Go”. |
review-contract | Security review for Cardano smart contracts written in Aiken, Plutus, or OpShin. Trigger: “review contract”, “audit validator”, “check security”, “find vulnerabilities”, “security review”, “smart contract audit”, “check for exploits”. |
scaffold-project | Scaffold a new Cardano project with on-chain + off-chain toolchain wired up. Helps pick a use case from the Cardano Foundation templates (or a custom one), a stack (Aiken on-chain; Evolution SDK, Mesh SDK, PyCardano, or cardano-client-lib off-chain), a network (Yaci DevKit, preview, preprod), and optionally a Next.js frontend. Produces a canonical directory layout, config files, devnet wiring, and starter validator + transaction skeletons. Triggers: “scaffold project”, “new Cardano project”, “project structure”, “init Cardano”, “starter template”, “project layout”, “bootstrap dApp”, “set up Cardano monorepo”, “Cardano project skeleton”, “scaffold dApp”. |
setup-devnet | Guides setting up a local Cardano development environment. Triggers: “setup devnet”, “local testnet”, “Yaci DevKit”, “development environment”, “local Cardano node”, “devnet”, “preview testnet”, “preprod testnet”. |
suggest-scalability | Decide whether a Cardano project needs Layer 2 / scaling at all, and if so which approach and topology fits — then route to the bundled implementation docs. Covers the L1-first sufficiency check (including the Leios throughput horizon), Hydra Head (the only mainnet-ready L2) vs Mithril vs in-development rollups (Midgard, Gummiworm), and Hydra topology selection (basic 2-party, delegated head, managed, star-shaped). Triggers: “do I need Layer 2”, “which L2”, “scale my dApp”, “Hydra vs rollup”, “Midgard”, “Gummiworm”, “state channel”, “payment channel”, “sidechain”, “increase throughput”, “sub-second finality”, “which Hydra topology”, “off-chain scaling”, “reduce fees at scale”. |
suggest-tooling | Recommends Cardano developer tools and SDKs for a specific project. Triggers: “which SDK”, “recommend tools”, “best library for”, “Cardano SDK”, “Mesh vs Evolution SDK”, “Aiken vs Plutus”, “what tools should I use”, “Cardano ecosystem”, “haskell.nix”, “CHaP”, “cardano-ledger off-chain”, “Haskell Cardano stack”, “Cardano in Go”, “x402”, “HTTP 402”, “pay per request”, “charge per API call”, “x402 facilitator”. |
write-validator | Guide writing a Cardano validator from a specification. Covers datum/redeemer design, validator logic, security checks, and test planning. Default language is Aiken. Trigger: “write validator”, “create contract”, “build smart contract”, “new validator”, “implement spending validator”, “write minting policy”. |
How to invoke
In Claude Code, use the plugin-qualified name /cardano-dev-skills:write-validator; in Codex, use $write-validator. Or describe the task in natural language — skills carry trigger phrases that auto-match. See How it works for the matching mechanism and what to do when it misses.