ctx-dispatch
Coordinate nontrivial work in the ctx repository when a task has independent investigation, implementation, or test lanes; compute-heavy checks; or repetitive changes suited to scripts or codemods. Use for decomposition and concurrency decisions, not simple edits or questions.
npx skills add stevesolun/ctx --skill ctx-dispatch --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Dispatch ctx work 1. Identify the requested outcome, dependencies, and independently executable lanes. Keep simple work local. 2. Reserve subagents for bounded semantic work that benefits from isolated context. 3. Run lanes concurrently only when this reduces elapsed time without duplicate work or competing writes. Give each writer disjoint ownership; keep shared files with one owner. 4. Inspect CPU, memory, and disk pressure only before genuinely compute-heavy work, then size concurrency to the available capacity. 5. Keep scope, dependency resolution, and synthesis with one coordinator. Merge evidence from every required lane before reporting completion.
What does the ctx-dispatch skill do?
Coordinate nontrivial work in the ctx repository when a task has independent investigation, implementation, or test lanes; compute-heavy checks; or repetitive changes suited to scripts or codemods. Use for decomposition and concurrency decisions, not simple edits or questions.
How do I install it?
Run `npx skills add stevesolun/ctx --skill ctx-dispatch --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 stevesolun/ctx, a repository with 569 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.