A catalog of portable skills for AI agents. Each skill is a self-contained playbook — a SKILL.md any agent can read, plus the templates and scripts it needs — that turns a workflow you’d otherwise re-explain every session into something you install once and invoke by name.
The repository doubles as a Claude Code plugin marketplace, but nothing is locked to one runtime: provider-specific adapters live beside each skill, and the core instructions stay portable.
| Skill | What it’s for | Ships as |
|---|---|---|
| advisory-board | Convene a board of frontier AI models — Claude, Codex, Gemini, and Grok — that each review the same decision independently, debate across rounds, and hand back one clear recommendation. | Standalone plugin |
| router | The team-workflow pack’s entry point: names every pack skill and when to reach for it. | team-workflow pack |
| setup | Once-per-repo interview that binds the pack to your project — tracker, verify commands, who decides — and seeds the binding doc and templates. | team-workflow pack |
| domain-memory | Per-repo institutional memory — a small domain glossary plus lightweight decision records — written as side effects of grillings, reviews, and decider corrections. | team-workflow pack |
| grilling | Interview the decider relentlessly over a design tree, in rounds, until nothing load-bearing is still assumed. | team-workflow pack |
| decision-map | Chart genuinely foggy work — where open questions gate each other — as a decision map before anyone writes a build spec. | team-workflow pack |
| prototype | Throwaway prototype code that answers a design question you can’t settle by discussion; the verdict is the deliverable. | team-workflow pack |
| research | Fire-and-report investigation against primary sources, ending in a cited findings file. | team-workflow pack |
| codebase-review | State review of the codebase itself: lens-named finders, a skeptic that kills unproven candidates, and a decider disposition loop. | team-workflow pack |
| to-tickets | Turn a plan, a closed map, or a pressure-tested conversation into tracer-bullet work items with their blocking edges wired. | team-workflow pack |
| wizard | Generate an interactive bash wizard for the steps only a human can take — vendor dashboards, DNS panels, credentials. | team-workflow pack |
| handoff | Write a structured session handoff — at wrap-up or when context fills — so a fresh session resumes losslessly. | team-workflow pack |
| show-me-your-work | Keep an append-only decision log during unattended work, so the human back from stepping away audits a table, not a recap. | team-workflow pack |
| orchestrate | Run one session as the orchestrator of parallel working lanes: route tracked items, audit results, own integration. | team-workflow pack |
| adversarial-review | Break the change before it ships: isolated finders, a skeptic pass, and a gate only confirmed blockers may hold. | team-workflow pack |
| diagnose | The disciplined bug-fixing loop — no fix ships without a cause named in one plain sentence, with evidence, plus the regression test. | team-workflow pack |
| implement | How a lane builds an item: seam-scoped test-first, tracer-first sequencing, green checkpoint commits, and file-don’t-fix scope discipline. | team-workflow pack |
Get a room full of expert advisors for any big decision — before you commit. Frontier models from Anthropic, OpenAI, Google, and xAI each examine the same thing — your plan, your draft, your decision — then debate it out loud and hand you one clear recommendation: what’s solid, what’s risky, and what to do next. Works for software, but also product, research, legal, business, and writing.
Read the full guide → — or jump straight to a real finished handoff from another real run, “Should I go full-time on my side project?” (verdict: proceed with care, unanimous).
A workflow for teams building with agents — without the collisions. Sixteen skills that ship and version together: decide before you build (decision-map), prototype what discussion can’t settle (prototype), investigate what sources can answer (research), hand sessions off losslessly (handoff), coordinate parallel lanes from one seat (orchestrate), bind it all to your repo once (setup), and orient any session with the router. Everything repo-specific lives in one binding doc; every skill defers judgment calls to the decider — the role your repo names, not a person the pack assumes.
Start with the router to see the whole pack at a glance.
In Claude Code:
/plugin marketplace add timharris707/skills
/plugin install advisory-board@skills
/plugin install team-workflow@skills
Or clone the repository and copy or symlink skill directories into wherever your runtime discovers skills — the README covers both paths.
The source files live in the skills/ directory of the repository.