Agent skill · Code Review & Quality

devils-advocate

Use when challenging assumptions, surfacing risks, or stress-testing designs and decisions. Triggers: 'challenge this', 'play devil's advocate', 'what could go wrong', 'poke holes', 'find the flaws', 'what am I missing', 'is this solid', 'red team this', 'what are the weaknesses', 'risk assessment', 'sanity check'. Works on design docs, architecture decisions, or any artifact needing adversarial review.

majiayu000github.com/majiayu000GitHub ↗
claude-codeMIT
Install
npx skills add majiayu000/claude-skill-registry --skill devils-advocate-axiomantic-spellbook-3 --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 2
SKILL.md size: 6 KB
Bundled scripts: none
Path: skills/analysis/devils-advocate-axiomantic-spellbook-3/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 534
Language: HTML

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

<ROLE> Devil's Advocate Reviewer. Find flaws, not validate. Assume every decision wrong until proven otherwise. Zero issues found = not trying hard enough. </ROLE> ## Invariant Principles 1. **Untested assumptions become production bugs.** Every claim needs evidence or explicit "unvalidated" flag. 2. **Vague scope enables scope creep.** Boundaries must be testable, not interpretive. 3. **Optimistic architecture fails at scale.** Every design decision needs "what if 10x/failure/deprecated" analysis. 4. **Undocumented failure modes become incidents.** Every integration needs explicit failure handling. 5. **Unmeasured success is unfalsifiable.** Metrics require numbers, baselines, percentiles. ## Applicability | Use | Skip | |-----|------| | Understanding/design doc complete | Active user discovery | | "Challenge this" request | Code review (use code-reviewer) | | Before architectural decision | Implementation validation (use fact-checking) | ## Inputs | Input | Required | Description | |-------|----------|-------------| | `document_path` | Yes | Path to understanding or design document to review | | `focus_areas` | No | Specific areas to prioritize (e.g., "security", "scalability") |

What's inside
Steps it walks through
  1. Invariant Principles
  2. Applicability
  3. Inputs
  4. Outputs
  5. Review Protocol
  6. Required Sections (flag missing as CRITICAL)
  7. Challenge Categories
  8. Challenge Template
  9. Output Format
  10. Self-Check
Ships with 1 file
  • metadata.json
More from claude-skill-registry
All skills →
About this skill
What does the devils-advocate skill do?

Use when challenging assumptions, surfacing risks, or stress-testing designs and decisions. Triggers: 'challenge this', 'play devil's advocate', 'what could go wrong', 'poke holes', 'find the flaws', 'what am I missing', 'is this solid', 'red team this', 'what are the weaknesses', 'risk assessment', 'sanity check'. Works on design docs, architecture decisions, or any artifact needing adversarial review.

How do I install it?

Run `npx skills add majiayu000/claude-skill-registry --skill devils-advocate-axiomantic-spellbook-3 --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going