19 protocol-driven skills for Claude Code & Codex CLI: an adversarial reviewer, its evidence-grounded analysis spine, a production-ops discipline suite, and the gauntlet that A/B-tests any skill against a no-skill control — three of these lost to loading nothing until it was run.
Skill Claude CodeCodex
Build and test an explicit inventory of hidden assumptions using the Key Assumptions Check technique. Use for assumption check or what are we assuming. For general engineering review or what am I missing, use morpheus.
Skill Claude CodeCodex
Map the full solution space and evaluate approaches against evidence. Based on the CIA's Analysis of Competing Hypotheses (ACH). Use for DECISIONS - choosing between technologies, architectures, or strategies - or when the user needs counterpoints and alternatives. Triggers on "what are the alternatives", "compare…
Skill Claude CodeCodex
Deep technical investigation for complex systems, unfamiliar codebases, architecture, data flows, and dependencies - when the system works but is not understood. Use when the user asks for a deep dive, investigate deeply, map the system, understand how it works, break down complexity, or produce an evidence-backed…
Skill Claude CodeCodex
Argue the opposing position: construct the strongest possible case for the alternative or against a pending decision. Use for make the case for NOT doing this, argue the other side, steelman the alternative, what would critics say. Produces an opposing-counsel brief, not a code review. For evidence-based critique of…
Skill Claude CodeCodex
Identify and prioritize concrete component and dependency failure modes, their consequences, containment and recovery. Use for FMEA, reliability assessment, single points of failure, or "how could this fail". General engineering verdicts belong to morpheus; active debugging to the troubleshooting reference in…
Skill Claude Code
Empirically test whether a skill actually improves model output — before trusting it. Runs a controlled experiment: planted-flaw fixture, no-skill control arm, skill arm(s), optional cross-model arms via installed CLIs, blind judging with shuffled labels, and a pressure test for verdict stability. Produces…
Skill Claude Code
Adversarial collaborator who pushes back like a senior engineer - the default adversarial reviewer. Surfaces hidden assumptions, grounds every challenge in evidence, presents real counterpoints with proven alternatives, drives toward synthesis, and records settled claims as verdict nodes in docs/verdicts/ so an…
Skill Codex
Create a compact handoff document for another Codex session or agent to continue the work. Use when the user asks for a handoff, next-agent context, continuation note, session summary, resume brief, or wants another agent to pick up without reconstructing the thread.
Skill Claude CodeCodex
Senior adversarial QA that proves what a change does and how, and leaves the proof on the pull request. Reviews the change for development gaps (unmet acceptance criteria, untested paths, config and flag gaps, rollback, observability), runs API, data and real-browser cases, and publishes every command, request…
Skill Claude CodeCodex
Run premortems before risky work and postmortems after incidents or failures. Use when the user asks for premortem, postmortem, incident review, retrospective, launch risk, "how will this fail", or "what killed this". Build the causal chain from evidence and produce the premortem/postmortem document with owners and…
Skill Claude CodeCodex
Examine concrete attack and failure paths, then design prevention, detection, containment and recovery. Use for red team, blue team, threat models, attack paths or defense plans. General engineering review belongs to morpheus; component failure inventories belong to failure-analysis.
Skill Claude CodeCodex
Safely perform authorized remote, destructive or security-relevant operations, including Git push/merge, releases, infrastructure and data mutations, credential changes and bulk cleanup. Not required for routine read-only inspection or ordinary scoped repository edits.
Skill Claude CodeCodex
Generate or review technical specs and Architecture Decision Records. Use when the user asks for specs, ADRs, RFCs, design docs, decision records, technical requirements, non-goals, alternatives, rollout, or rollback documents. For user-research requirements elicitation use user-research.
Skill Claude CodeCodex
Toolshed — durable, model-agnostic working state for ONE coding task (feature, investigation) as docs/work/SLUG/ under docs/, DELETED at close. Seeds STATE + decisions/questions/evidence with grades and reproduction commands. Use for "start a toolshed", "seed the task", "/toolshed start|resume|session-end|close", or…
Skill Claude CodeCodex
Turn a raw alert payload into a one-screen incident brief: blast radius, suspected cause, the three checks that discriminate between causes, and the containment action. Use when paged, when triaging an alert, or when handing an incident to the next responder.
Skill Claude CodeCodex
Second opinion and final verdict for engineering decisions. Challenges a plan, design, PR, claim, fix, or bug theory with cited evidence, steelmans the user's position first, asks when an assumption would flip the verdict, labels how each claim is known, and always lands on a verdict or a recommended option with…
Skill Claude Code
Adversarial review toolkit for code, PRs, designs, plans, migrations, incident fixes, and strategy. One skill, several lenses: red team / blue team, premortem, devil's advocate, competing alternatives, failure modes (FMEA, dependency chains), assumptions check, and inversion. Every challenge is grounded in evidence…
Skill Claude CodeCodex
Drive a real browser through a UI change and prove it works with captured evidence — screenshots, console output, and network activity — then publish that evidence (attached to the PR via gh image, or as a local markdown proof doc when there's no PR). Uses the Chrome DevTools MCP against a persistent…
Skill Claude CodeCodex
Behaviour-driven development, the method, not the tool. Use whenever the work involves acceptance criteria, examples, scenarios, Gherkin or .feature files, "given when then", example mapping, or deciding what "done" means for a story. Use it to discover rules and examples from a ticket, write scenarios, review…
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: