Automate Starknet contract build, declare, deploy, and verify workflows.
npx skills add https://github.com/cartridge-gg/scoundrel --skill cairo-toolchain
Please help me install this Agent Skill. Skill: cairo-toolchain Source: https://github.com/cartridge-gg/scoundrel/tree/main/.agents/skills/cairo-toolchain Command: npx skills add https://github.com/cartridge-gg/scoundrel --skill cairo-toolchain
The Cairo Toolchain provides a deterministic, end-to-end workflow for Starknet contract lifecycles, unifying build, declare, deploy, and verify steps with clear provenance.
Pin the tool versions and run the default workflow to declare, deploy, and verify Starknet contracts.
High-intent search queries and answers about installing and using this skill.
Deploy and verify Cairo contracts on Starknet deterministically by pinning tool versions, generating reproducible artifacts, and following an explicit declare-before-deploy sequence across Sepolia and mainnet. This workflow automates the full lifecycle from build to release with provenance evidence.
The correct sequence to declare and deploy Starknet contracts requires an explicit declare-before-deploy workflow, ensuring class declaration occurs before contract deployment to maintain deterministic artifact generation and verifiable provenance across target networks.
Yes, this Starknet deployment workflow supports both Sepolia and mainnet networks, allowing you to build, declare, deploy, and verify Cairo contracts across different environments while maintaining deterministic artifacts and consistent release evidence.
Pinning tool versions for Cairo contract deployment is required to achieve deterministic artifact generation and reproducible builds, ensuring that compiled outputs remain identical across builds and enabling reliable verification of deployed contract provenance on Starknet.
Managing complex Cairo project lifecycles with reproducible builds is best handled through an end-to-end toolchain that unifies build, declare, deploy, and verify steps, providing deterministic artifact generation and release evidence for provenance across networks.
Deploying Starknet contracts requires declaring classes first, as the default workflow enforces an explicit declare-before-deploy sequence to ensure deterministic artifact generation and proper class registration before contract deployment on Sepolia or mainnet.
iamcapoteScaffold a Cairo project with OpenZeppelin dependencies in Scarb.toml.
zkp2pAutomate ZKP2P smart contract package releases with preflight validation and registry publication.
iamcapoteAutomate Cairo contract class hash upgrades on Starknet using OpenZeppelin's UpgradeableComponent.
JOHNNYWHITEMIKEList, authenticate, configure, and invoke MCP servers and tools via mcporter CLI.
