Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Use when managing Crunch coordinators, competitions (crunches), rewards, checkpoints, staking, or cruncher accounts via the crunch-cli.
Use when managing Crunch coordinators, competitions (crunches), rewards, checkpoints, staking, or cruncher accounts via the crunch-cli.
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
Translates natural language queries into crunch-cli commands. Supports profiles and output formatting for Slack, Telegram, Discord, or plain text.
Node.js 18+ with npm Solana wallet keypair (for on-chain operations)
This skill installs packages via npm (global): PackageSourcePurpose@crunchdao/crunch-clinpmCrunchDAO protocol CLI (coordinators, competitions, staking) Agent rules for package installation: Only install @crunchdao/crunch-cli from the official npm registry No custom registry URLs โ no --registry overrides Ask the user before installing if not already present
What it is: A JSON file containing a Solana private key, used to sign transactions How it's configured: Set via crunch-cli config set wallet /path/to/wallet.json or -w flag per command Stored in: User-managed file on disk; path referenced in ~/.crunch/config.json Agent rules for wallets: Never create or generate wallet keypairs unless the user explicitly asks and understands the security implications Never read or display the contents of wallet keypair files Never commit wallet files to git โ always verify .gitignore covers them Ask the user for the wallet path โ never assume or search for keypair files
Stores network, wallet path, and RPC URL per profile Managed via crunch-cli config commands โ no need to edit manually Never modify or delete existing profiles unless explicitly asked
npm install -g @crunchdao/crunch-cli crunch-cli --version
The CLI has built-in profile management via ~/.crunch/config.json: crunch-cli config show # Show current config crunch-cli config active # Show resolved active values crunch-cli config list-profiles # List available profiles crunch-cli config save-profile <name> # Save current config as profile crunch-cli config use <profile> # Switch profile crunch-cli config set <key> <value> # Set config value Global flags can override config per-command: FlagDescription-n, --networkSolana network: mainnet-beta, devnet, localhost-u, --urlCustom RPC URL-w, --walletPath to Solana keypair-o, --outputOutput format: json, table, yaml
User PhraseCLI Commandget/show crunch <name>crunch-cli crunch get "<name>"list crunchescrunch-cli crunch listget/show coordinator [address]crunch-cli coordinator get [address]list coordinatorscrunch-cli coordinator listget configcrunch-cli coordinator get-configcheckpoint for <name>crunch-cli crunch checkpoint-get-current "<name>"create checkpoint <name>crunch-cli crunch checkpoint-create "<name>" prizes.jsondeposit reward <name> <amount>crunch-cli crunch deposit-reward "<name>" <amount>drain <name>crunch-cli crunch drain "<name>"create/register crunchercrunch-cli cruncher createregister for <name>crunch-cli cruncher register "<name>"claim rewards <name>crunch-cli cruncher claim "<name>"show staking positionscrunch-cli staking positionsstake/deposit <amount>crunch-cli staking deposit <amount>delegate to <coordinator>crunch-cli staking delegate "<coordinator>" <amount>show staking rewardscrunch-cli staking rewardsclaim staking rewardscrunch-cli staking claimundelegate from <coordinator>crunch-cli staking undelegate "<coordinator>" <amount>withdraw stake <amount>crunch-cli staking withdraw <amount>init workspace <name>crunch-cli init-workspace "<name>"list scenarios/simulationscrunch-cli model listrun simulation <scenario>crunch-cli model run "<scenario>"register coordinator <name>crunch-cli coordinator register "<name>"create crunch <name>crunch-cli crunch create "<name>" <amount> [maxModels]start/end crunch <name>crunch-cli crunch start/end "<name>"
Parse โ Identify action, target, name/identifier, parameters Resolve profile โ If mentioned, switch profile or use flags Map โ Use phrase mapping table Execute โ Run command Format โ Output for requested medium (Slack/Telegram/Discord/plain)
Detect medium from user request ("for slack", "telegram format", etc.): Slack: *bold*, โข bullets, โ separators Telegram: <b>bold</b>, emoji prefixes Discord: ## headers, **bold** Plain: Simple key: value pairs
If command fails, suggest fixes: Wrong network? Add -n mainnet-beta or -n devnet Missing wallet? Add -w /path/to/wallet.json Not found? List available with crunch-cli crunch list
Scaffold a new competition workspace: crunch-cli init-workspace my-challenge This generates a full node workspace. See the coordinator-node-starter skill for customization.
For full CLI documentation: references/cli-reference.md
Code helpers, APIs, CLIs, browser automation, testing, and developer operations.
Largest current source with strong distribution and engagement signals.