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.
68
81%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Passed
No findings from the security scan
Agent-native harness for the chimera-defi/eth2-quickstart automation repo.
This CLI wraps the repo's canonical shell scripts instead of replacing them.
Use this skill when the task involves:
--json# 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--json for agent parsing.setup-node, install-clients, or start-rpc.configure-validator as metadata and operator-guidance only.eth2-quickstart checkout.--repo-root, ETH2QS_REPO_ROOT, or current working directory.config/user_config.env when flags map directly to repo settings.34f5195
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.