orchestration

Orchestrate three-phase Scaffold-ETH 2 dApp deployments from Anvil forks to production.

Updated Mar 6, 2026
One-click install
npx skills add https://github.com/andginja/ethskills --skill orchestration-andginja
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: orchestration
Source: https://github.com/andginja/ethskills/tree/main/skills/orchestration
Command: npx skills add https://github.com/andginja/ethskills --skill orchestration-andginja

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill guides you through the essential three-phase process for building and deploying decentralized applications (dApps) using the Scaffold-ETH 2 framework, preventing common pitfalls and ensuring a smooth transition from development to production.

Core Features & Use Cases

  • Three-Phase Deployment: Enforces a structured approach: Localhost (Anvil fork), Testnet/Mainnet, and Production.
  • Scaffold-ETH 2 Hooks: Promotes the use of useScaffoldWriteContract and useScaffoldReadContract over raw wagmi hooks for enhanced reliability and type safety.
  • Environment Management: Emphasizes secure handling of private keys and RPC URLs using environment variables.
  • Use Case: You are building a new DeFi protocol. This Skill ensures you first develop and test thoroughly on a local fork, then deploy to a testnet for further validation, before finally launching to mainnet, minimizing risks at each stage.

Quick Start

Follow the three-phase deployment process outlined in this skill to build and launch your dApp.

Frequently Asked Questions about orchestration

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

FAQPage Schema
How do I deploy a Scaffold-ETH 2 dapp from localhost to mainnet?

Deploying a Scaffold-ETH 2 dapp requires a three-phase pipeline: local development on an Anvil fork, testnet validation, and production mainnet launch. This structured approach minimizes deployment risks by validating contract interactions at each stage.

Why should I use Scaffold-ETH 2 hooks instead of raw wagmi hooks for contract interactions?

Using Scaffold-ETH 2 hooks like useScaffoldWriteContract and useScaffoldReadContract instead of raw wagmi hooks provides enhanced reliability and type safety. This prevents common agent mistakes during dapp development and ensures secure contract interactions.

What is the best way to manage private keys when deploying web3 smart contracts?

The best way to manage private keys for smart contract deployment is using environment variables. This secure environment variable management approach protects sensitive credentials like private keys and RPC URLs during testnet and production deployments.

How does Anvil fork testing work before Ethereum testnet deployment?

Anvil fork testing works by simulating the Ethereum mainnet environment locally before testnet deployment. This localhost phase allows developers to thoroughly test smart contract interactions and validate dapp functionality using Scaffold-ETH 2 hooks in a risk-free environment.

What are common smart contract deployment mistakes when building DeFi protocols?

Common smart contract deployment mistakes include using raw wagmi hooks, hardcoding contract addresses, and skipping contract verification. Following a structured three-phase deployment pipeline prevents these errors during DeFi protocol development and production launches.

Do I need to verify smart contracts when moving from testnet to production?

Yes, you need to verify smart contracts when moving from testnet to production. Contract verification is a critical step in the deployment pipeline that addresses common agent mistakes and ensures transparency for your dapp on the Ethereum blockchain.