devils-advocate
Use before design phase to challenge assumptions and surface risks
npx skills add majiayu000/claude-skill-registry --skill devils-advocate-axiomantic-spellbook-2 --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
<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") |
- Invariant Principles
- Applicability
- Inputs
- Outputs
- Review Protocol
- Required Sections (flag missing as CRITICAL)
- Challenge Categories
- Challenge Template
- Output Format
- Self-Check
What does the devils-advocate skill do?
Use before design phase to challenge assumptions and surface risks
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill devils-advocate-axiomantic-spellbook-2 --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.