swarm
Fan out N independent workers, collect their results, and return one report for coverage, races, gauntlets, or exploration.
Skill by painhardcore
Install
Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.
npx agentmarket install skill/painhardcore-swarm
Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.
Get the weekly diff
The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.
About
Use cases: documents, testing
Reviews
Write a reviewNo reviews yet. Installed it? Reviews come from verified installers only. How reviews work
Permissions
What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.
- Tools
- No tools found
- Secrets
- None asked for
- Install scripts
- None found
Network hosts it talks to 1
codeload.github.com· found in install command
Files it touches
~/.claude/skills/swarm
What's inside
- Skill name
swarm- Description
- Fan out N independent workers, collect their results, and return one report for coverage, races, gauntlets, or exploration.
- License
- MIT
- Instructions
- 42 lines in SKILL.md · view on GitHub
Files (1)
- SKILL.md
SKILL.md (first lines)
# Swarm Fan out N independent workers. They may cover separate slices, race the same brief, or mix both. The parent waits, aggregates, and returns one report. ## Start Open a todolist with one entry per phase before launching anything. 1. Frame 2. Fan out 3. Aggregate 4. Report ## Phase A: Frame 1. State the done predicate and the artifact or report the swarm must return. 2. Choose the shape. Partition into slices, race N workers on identical briefs, or mix both. For a race or mixed shape, declare `first pass`, `rank all`, or `best-of` before spawning. 3. Set N from the user or derive it from the shape. N is total workers, not the cloud concurrency limit. 4. Inherit the parent model unless the host supports model selection and the race explicitly compares models. Name each model-race arm up front. 5. Give each worker its own writable output when it writes. Use a worktree, branch, or `/tmp/swarm-<slug>/worker-<n>/`. ## Phase B: Fan out Use the host's native subagent tool to start all N workers concurrently. Give each worker the minimum file and tool access its slice needs. If subagents are unavailable or forbidden, run each slice inline and preserve the same result schema. When a worker needs a non-default branch, name that branch in its brief and use an isolated checkout or worktree. Every brief stands alone. Include the goal, scope, exact slice or race arm, how to verify, and what to report. Reports use `PASS`, `ISSUES`, or `BLOCKED` with evidence. If a worker drops out, proceed with N-1 and note it. ## Phase C: Aggregate Read the terminal results. For coverage, every required slice needs a result. For a race, apply the selection rule declared up front. Use first pass, rank all, or best-of. Do not paste raw worker dumps. Keep a compact result table, one-line evidenced issues, and explicit gaps or dropouts. ## Phase D: Report Return one consolidated in-chat report with the table, issue one-liners, gaps or dropouts, and the race rule when used.
From painhardcore/pstack, MIT.
More from painhardcore/pstack
- 0.596score
how
painhardcore
Explain how a subsystem works, trace a runtime flow, or determine where code and ownership belong before making a change.
SkillBFreshness: B★ 12Claude Code +9 - 0.596score
poteto-mode
painhardcore
Apply poteto's rigorous engineering workflow to non-trivial coding, investigation, review, migration, and verification tasks.
SkillBFreshness: B★ 12Claude Code +9 - 0.593score
no-comments
painhardcore
Use before review when the user asks to strip, remove, or clean up comments in code.
SkillBFreshness: B★ 12Claude Code +9 - 0.571score
interrogate
painhardcore
Use for "interrogate", "adversarial review", "multi-model review", "challenge this", "stress test this code", "find blind spots", or "tear this apart".
SkillBFreshness: B★ 12Claude Code +9 - 0.571score
create-verification-skill
painhardcore
Generate a project-local verification skill that drives your app the way a user does — any language, framework, or platform.
SkillBFreshness: B★ 12Claude Code +9 - 0.571score
architect
painhardcore
Sketch types, signatures, and module structure before code, then stay in the loop while implementation fills in.
SkillBFreshness: B★ 12Claude Code +9 - 0.569score
figure-it-out
painhardcore
Design an auditable playbook when no narrower one fits: a large migration, an ambitious multi-part change, or work a human reviews after stepping away.
SkillBFreshness: B★ 12Claude Code +9 - 0.566score
blast-radius
painhardcore
Find what a change could break somewhere else before it ships, beyond the diff, and prove the one fact it's safe because of by running real code instead of…
SkillBFreshness: B★ 12Claude Code +9 - 0.566score
arena
painhardcore
Spawn N parallel candidates at the same task, pick a base, graft the strongest parts of the losers into it.
SkillBFreshness: B★ 12Claude Code +9 - 0.566score
maintain-verification-skill
painhardcore
Periodic pass that keeps a project's verification skill and feature map honest: parallel source readers per feature, one live session driving every feature…
SkillBFreshness: B★ 12Claude Code +9 - 0.561score
principle-build-the-lever
painhardcore
Apply to any non-trivial work, not just bulk work: edits, migrations, analyses, checks.
SkillBFreshness: B★ 12Claude Code +9 - 0.561score
principle-exhaust-the-design-space
painhardcore
Apply when facing a novel UI interaction or architectural decision with no precedent in the codebase.
SkillBFreshness: B★ 12Claude Code +9
Signals
- Stars
- 12
- Forks
- 3
- Open issues
- 0
- Last commit (this folder)
- Aug 27, 2026 (2 months ago)
- Last release
- Aug 26, 2026 (2 months ago)
From GitHub (fetched Oct 24, 2026).
Details
- License
- MIT
- Repository
- github.com/painhardcore/pstack
- First seen
- Oct 24, 2026
- Last checked
- Oct 24, 2026
- Source
- GitHubgithub-graphql
More from painhardcore
- 0.596score
how
painhardcore
Explain how a subsystem works, trace a runtime flow, or determine where code and ownership belong before making a change.
SkillBFreshness: B★ 12Claude Code +9 - 0.596score
poteto-mode
painhardcore
Apply poteto's rigorous engineering workflow to non-trivial coding, investigation, review, migration, and verification tasks.
SkillBFreshness: B★ 12Claude Code +9 - 0.593score
no-comments
painhardcore
Use before review when the user asks to strip, remove, or clean up comments in code.
SkillBFreshness: B★ 12Claude Code +9 - 0.571score
interrogate
painhardcore
Use for "interrogate", "adversarial review", "multi-model review", "challenge this", "stress test this code", "find blind spots", or "tear this apart".
SkillBFreshness: B★ 12Claude Code +9 - 0.571score
create-verification-skill
painhardcore
Generate a project-local verification skill that drives your app the way a user does — any language, framework, or platform.
SkillBFreshness: B★ 12Claude Code +9 - 0.571score
architect
painhardcore
Sketch types, signatures, and module structure before code, then stay in the loop while implementation fills in.
SkillBFreshness: B★ 12Claude Code +9
Cite this page
swarm skill. Agent Mart. https://agentmart.dev/skills/painhardcore-swarm (last updated 2026-10-24)