Agent skill

crank

Hands-free epic execution for Codex using wave-based sub-agents and lead-side validation. Triggers: "crank", "run epic", "execute epic", "run all tasks", "hands-free execution", "crank it".

majiayu000github.com/majiayu000GitHub ↗
claude-codeMIT
Install
npx skills add majiayu000/claude-skill-registry --skill crank-boshu2-agentops-3 --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 2
SKILL.md size: 2 KB
Bundled scripts: none
Path: skills/agent/crank-boshu2-agentops-3/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 534
Language: HTML

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# $crank — Autonomous Epic Execution (Codex Tailoring) This override captures the Codex-native execution model for multi-issue epic work. ## Core Model - The lead agent owns wave planning, validation, and issue state transitions. - Workers are spawned with `spawn_agent(...)`. - Each worker gets a bounded task, explicit owned files, and validation steps. - The lead agent uses `wait_agent(...)` only when integration is blocked on a worker result. ## Codex-Native Wave Loop ### Step 1: Select the wave Use `bd ready --json` when available, or the current plan artifact when beads is unavailable. Only include unblocked work with disjoint file ownership in the same wave. ### Step 2: Prepare worker packets For each issue, include: - issue id and subject - short implementation brief - owned files - validation commands - reminder that the worker is not alone in the repo ### Step 3: Spawn workers Use one `spawn_agent(...)` call per issue with `agent_type="worker"`. ### Step 4: Monitor and correct Collect worker results with `wait_agent(...)`. If a worker needs rework, use `send_input(...)` with a focused correction or launch a new wave for the remaining work. ### Step 5: Validate centrally The

What's inside
Steps it walks through
  1. Core Model
  2. Codex-Native Wave Loop
  3. Step 1: Select the wave
  4. Step 2: Prepare worker packets
  5. Step 3: Spawn workers
  6. Step 4: Monitor and correct
  7. Step 5: Validate centrally
  8. Step 6: Repeat
  9. Constraints
Ships with 1 file
  • metadata.json
More from claude-skill-registry
All skills →
About this skill
What does the crank skill do?

Hands-free epic execution for Codex using wave-based sub-agents and lead-side validation. Triggers: "crank", "run epic", "execute epic", "run all tasks", "hands-free execution", "crank it".

How do I install it?

Run `npx skills add majiayu000/claude-skill-registry --skill crank-boshu2-agentops-3 --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going