skill
Skill1 starsChanged 8 months agoMITView on GitHub
Run multi-agent team workflows using your existing Claude Code subscription. No extra tools, no extra cost -- just Markdown blueprints and Claude Code Hooks. One command dispatches a team of specialized agents that research, draft, assemble, review, and polish your deliverable through a structured pipeline. The Conductor breaks down the requirement and dispatches Task Agents. Two Assemblers then create competing drafts -- one emotional, one structural. The Judge merges the best of both versions and runs a quality checklist. The…
62 other projects use a version of this.
Adopted by
Most recently taken up by
- thenavidm/skill-buildertheir own version, first seen Nov 8, 2026
- TheAlejo160/orchestratheir own version, first seen Nov 8, 2026
- blamechris/chroxytheir own version, first seen Nov 8, 2026
- nexoral/AxioDBtheir own version, first seen Nov 8, 2026
- Yeachan-Heo/oh-my-claudecodetheir own version, first seen Nov 8, 2026
- szarkans/multitheir own version, first seen Nov 2, 2026
Used with
Projects with it also use ai-slop-cleaner, ralplan and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
Jurel89Skillai-slop-cleaner
Clean AI-generated code slop with a regression-safe, deletion-first workflow and optional reviewer-only mode
Also in 5 projects that use this
ibahgatSkillralplan
Create a strict, quality-first execution plan with explicit gates and rollback-ready sequencing.
Also in 5 projects that use this
ibahgatSkillhud
Control omi visual HUD profile and keep status output readable in normal, compact, or hidden mode.
Also in 5 projects that use this
Jurel89Skillultraqa
QA cycling loop — build/lint/test, fix, retry up to 5 cycles
Also in 3 projects that use this
LucasCooperBeySkillvisual-verdict
Structured visual QA verdict for screenshot-to-reference comparisons. Returns JSON scores driving edit iterations. Use after any UI implementation to verify visual fidelity.
Also in 3 projects that use this
Yeachan-HeoSkillultragoal
Create and execute durable repo-native multi-goal plans over Codex goal mode artifacts.
Also in 3 projects that use this
Other versions62 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 62
- Yeachan-Heo/oh-my-claude-sisyphus★ 41ksame name
- Yeachan-Heo/oh-my-claudecode★ 41ksame name
- Yeachan-Heo/oh-my-codex★ 34ksame name
- tradecatlabs/vibe-coding-cn★ 18ksame name
- tukuaiai/vibe-coding-cn★ 18ksame name
- liyue-aigc/female-portrait-director★ 1.6ksame name
- sundial-org/skills★ 151same name
- build23w/fdv.lol★ 128same name
- builders-toronto/fdv.lol★ 128same name
- redf0x1/camofox-mcp★ 124same name
52 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 1 is distinctive, and 1 is very specific to this project.
0
Common
Most of the 45 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 5
Run multi-agent team workflows using your existing Claude Code subscription.
- Very specific: line 49
Run /teams to launch a blueprint workflow.
“Common” is measured: kept by at least 6 in 10 of the 45 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Claude Teams Go
What It Does
Run multi-agent team workflows using your existing Claude Code subscription. No extra tools, no extra cost -- just Markdown blueprints and Claude Code Hooks. One command dispatches a team of specialized agents that research, draft, assemble, review, and polish your deliverable through a structured pipeline.
Core Concept
User Request
|
Conductor (Claude Code main agent)
|-- clarifies requirements
|-- selects blueprint
|-- dispatches Task Agents
v
Task Agents (parallel subagents)
|
v
Assembler A (Empath) + Assembler B (Architect) [parallel]
|
v
Judge (Checker) -- merge + quality checklist
|
v
Polisher -- refine + deliver
|
v
User <-> Polisher negotiationThe Conductor breaks down the requirement and dispatches Task Agents. Two Assemblers then create competing drafts -- one emotional, one structural. The Judge merges the best of both versions and runs a quality checklist. The Polisher applies final refinements and delivers to the user.
File Structure
roles/ Resident role personas (Empath, Architect, Judge, Polisher)
blueprints/ Workflow definitions -- each blueprint = one team configuration
_template.md Blank blueprint for creating new ones
hooks/ teams-router.js -- detects blueprint triggers on user input
commands/ Slash commands (/teams, /blueprint, /roles) in EN and ZHQuick Start
- Copy
roles/andblueprints/into your project root. - Install the hook: copy
hooks/teams-router.jsto.claude/hooks/. - Copy
commands/to.claude/commands/. - Run
/teamsto launch a blueprint workflow.
That's it. No dependencies to install.
Commands
| Command | Alias | What It Does |
/teams | /組隊 | Launch a blueprint workflow |
/blueprint | /規劃 | List, create, or edit blueprints |
/roles | /角色設定 | View or modify resident role personas |
Blueprint Format
Each blueprint is a Markdown file with these sections:
| Section | Purpose |
| Meta | Name, trigger words, one-line description |
| Agents | Task Agent table -- roles and memory references (tasks assigned at runtime) |
| Flow | Execution order: parallel, then stages |
| Roles Memory | Optional memory file injection for resident roles |
| Checklist | Quality gates the Judge must verify before passing |
| On Fail | Retry behavior when the Judge rejects a deliverable |
See blueprints/_template.md for the full template.
Memory Integration
Works standalone, but pairs with claude-memory-engine for richer context.
| Condition | Behavior |
| Memory engine installed | Reads blueprint memory fields; injects memory into subagent prompts |
| Memory engine not installed | Skips injection; subagents rely on blueprint task descriptions alone |
Resident Roles
Four permanent roles that stay consistent across every workflow:
| Role | Codename | Focus |
| Assembler A | Empath | Emotional resonance, storytelling, rhythm -- finds the warmest angle |
| Assembler B | Architect | Structure, keyword placement, evidence -- builds the most persuasive frame |
| Checker | Judge | Merges both versions, decides the empath/architect ratio, runs quality checklist |
| Polisher | Polisher | Final refinement, AI-trace removal, and sole point of contact with the user |
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

