combo
Skill1 starsChanged 4 months agoMITView on GitHub
Recommend and explain Conductor pillar combos A–H and their workflows (daily, chessboard, remnant, crucible, max-effort, heal, evidence, full-stack).
1 other project uses a version of this.
Adopted by
Most recently taken up by
- Tariux/AI-Skills-Not-Awesometheir own version, first seen Nov 15, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- Tariux/AI-Skills-Not-Awesome★ 48same name
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.
In this repository5 other files it gives its agents.
- batch-for-hostSkill
- pillarsSkill
- planSkill
- remnant-guideSkill
- reviewSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 42
Do not invent combos outside A–H.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Combo router
Pick which pillar stack to run for the current intent. Specs:
docs/PILLAR_COMBOS.md— pillars + named combosdocs/WORKFLOWS.md— step flows and mermaid diagrams
Combos (short)
| ID | Name | Use |
| A | Daily driver | Default work under SOUL + host tools |
| B | Chessboard | Track System map before fan-out |
| C | Parallel push | Remnant spawn/merge when parallel pays off |
| D | Deep forge | Crucible/Noesis simulation + distill |
| E | Max Effort | Ethics + four voices + 24–48h action |
| F | Integrity cascade | Heal wound, scar/seal, advance (no thrash) |
| G | Evidence gate | Plan → review → artifacts; done = proven |
| H | Full stack | Rare multi-pillar day |
When invoked
- Intent — restate the user goal in one line
- Primary combo — A–H with one-line why
- Secondary — up to two alternates if close
- Fold G? — yes when shipping / claiming done
- Workflow — numbered steps for the primary (from
docs/WORKFLOWS.md) - Tools / skills — which Conductor tools and slash skills to call next
- Next action — single concrete step
Ops (prefer runtime helpers when available):
/combo recommend <intent>/combo workflow <A-H>- tool
combo_routewith actionrecommend|workflow|list|get
Do not invent combos outside A–H. Prefer A when signals are weak. Never skip G when the user wants to ship or declare done.
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.