Use eth2-quickstart to autonomously deploy a hardened Ethereum node, install execution and consensus clients, configure validator metadata, expose RPC safely, and inspect node health with structured JSON output.
Install
npx skills add https://github.com/hkuds/cli-anything --skill cli-anything-eth2-quickstartSKILL.md
cli-anything-eth2-quickstart
Agent-native harness for the chimera-defi/eth2-quickstart automation repo.
This CLI wraps the repo's canonical shell scripts instead of replacing them.
When To Use
Use this skill when the task involves:
- bootstrapping a fresh Ethereum node host
- installing execution and consensus clients with explicit client diversity
- enabling MEV-Boost or Commit-Boost workflows
- exposing RPC through Nginx or Caddy
- updating validator fee recipient or graffiti settings without handling secrets
- checking machine-readable health with
--json
Core Commands
# Canonical machine-readable health
cli-anything-eth2-quickstart --json health-check
# Phase 2 install with explicit client choices
cli-anything-eth2-quickstart --json install-clients \
--network mainnet \
--execution-client geth \
--consensus-client lighthouse \
--mev mev-boost \
--confirm
# Guided node setup
cli-anything-eth2-quickstart --json setup-node \
--phase auto \
--execution-client geth \
--consensus-client prysm \
--mev commit-boost \
--confirm
# Validator metadata only; no key import
cli-anything-eth2-quickstart --json configure-validator \
--consensus-client prysm \
--fee-recipient 0x1111111111111111111111111111111111111111 \
--graffiti "CLI-Anything"
# Install nginx-backed RPC exposure
cli-anything-eth2-quickstart --json start-rpc \
--web-stack nginx \
--server-name rpc.example.org \
--confirm
Safety Rules
- Always use
--jsonfor agent parsing. - Require human confirmation before
setup-node,install-clients, orstart-rpc. - Do not generate validator keys.
- Do not remove secrets or wallet material.
- Treat
configure-validatoras metadata and operator-guidance only. - Respect the reboot boundary between Phase 1 and Phase 2.
Runtime Expectations
- Operates on a local
eth2-quickstartcheckout. - Discovers repo root from
--repo-root,ETH2QS_REPO_ROOT, or current working directory. - Writes compatible overrides into
config/user_config.envwhen flags map directly to repo settings.
Related skills
azure-diagnosticsmicrosoft608KDebug Azure production issues on Azure using AppLens, Azure Monitor, resource health, and safe triage. WHEN: debug production issues, troubleshoot app service, app service high CPU, app service deployment failure, troubleshoot container apps, troubleshoot functions, troubleshoot AKS, VM RDP, Linux SSH, VM black screen, can't connect to VM, reset VM password, NSG or firewall blocking, kubectl cannot connect, kube-system/CoreDNS failures, pod pending, crashloop, node not ready, upgrade failures, aazure-preparemicrosoft608KPrepare azd-based Azure projects for deployment: generates azure.yaml, infrastructure (Bicep/Terraform), and Dockerfiles for the Azure Developer CLI (azd) workflow. USE ONLY when the user explicitly wants to use azd as the deployment tool, or the project already has an azure.yaml file. DO NOT USE FOR: non-azd deployments, Python App Service code-only deploys (use python-appservice-deploy), or cross-cloud migration (use azure-cloud-migrate). WHEN: prepare app for azd, create azure.yaml, set up azazure-aimicrosoft608KUse for Azure AI: Search, Speech, OpenAI, Document Intelligence. Helps with search, vector/hybrid search, speech-to-text, text-to-speech, transcription, OCR. WHEN: AI Search, query search, vector search, hybrid search, semantic search, speech-to-text, text-to-speech, transcribe, OCR, convert text to speech.azure-deploymicrosoft607KExecute Azure deployments for ALREADY-PREPARED applications that have existing .azure/deployment-plan.md and infrastructure files. DO NOT use this skill when the user asks to CREATE a new application — use azure-prepare instead. This skill runs azd up, azd deploy, terraform apply, and az deployment commands with built-in error recovery. Requires .azure/deployment-plan.md from azure-prepare and validated status from azure-validate. WHEN: \"run azd up\", \"run azd deploy\", \"execute deployment\",
