cairo-toolchain

Name: cairo-toolchain
Availability: InStock
Author: cartridge-gg

Automate Starknet contract build, declare, deploy, and verify workflows.

Updated Apr 3, 2026

Search Tags:#workflow #deploy #verify #toolchain #cairo #starknet #declare

Ready to run

npx skills add https://github.com/cartridge-gg/scoundrel --skill cairo-toolchain

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

The Cairo Toolchain provides a deterministic, end-to-end workflow for Starknet contract lifecycles, unifying build, declare, deploy, and verify steps with clear provenance.

Core Features & Use Cases

Deterministic artifact generation and class declaration for Starknet contracts.
End-to-end deployment workflow including declare, deploy, and verification with release evidence.
Use case: manage complex Cairo project lifecycles with reproducible builds across networks.

Quick Start

Pin the tool versions and run the default workflow to declare, deploy, and verify Starknet contracts.

Frequently Asked Questions about cairo-toolchain

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I deploy and verify Cairo contracts on Starknet with deterministic builds?▼

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.

What is the correct sequence to declare and deploy Starknet contracts?▼

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.

Can I use this Starknet deployment workflow across both Sepolia and mainnet?▼

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.

Why do I need to pin tool versions for Cairo contract deployment?▼

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.

What's the best way to manage complex Cairo project lifecycles with reproducible builds?▼

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.

Does deploying Starknet contracts require declaring classes first?▼

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.