Agent skill

devils-advocate

Systematically challenge current assumptions before major decisions. Counters confirmation bias, groupthink, and overconfidence.

majiayu000github.com/majiayu000GitHub ↗
claude-codeMIT
Install
npx skills add majiayu000/claude-skill-registry --skill devils-advocate-haabe-mycelium-2 --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-haabe-mycelium-2/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

# Devil's Advocate Run before every major diamond transition and architecture decision. Source: Kahneman, Shotton. ## Technique 1: Pre-Mortem Imagine it's 6 months from now and this decision FAILED spectacularly. 1. What went wrong? 2. What assumption was the weakest link? 3. What signal did we ignore? 4. Who was affected and how? ## Technique 2: Assumption Reversal For each key assumption: - State the assumption explicitly - Ask: "What if the OPPOSITE is true?" - What evidence would support the opposite? - Is there any evidence we've dismissed? ## Technique 3: Red Team Attack your own position: - What would a competitor say about this approach? - What would a skeptical user say? - What would a security auditor find? - What would an accessibility advocate flag? ## 10 Challenge Questions 1. What are we most confident about? (That's where overconfidence hides) 2. What evidence have we dismissed or downweighted? 3. Are we anchored on our first idea? (Shotton - anchoring bias) 4. Have we tested with users who DON'T match our ideal profile? 5. What would make us abandon this direction entirely? 6. Are we building for ourselves or for actual users? 7. What's the simplest version that cou

What's inside
Steps it walks through
  1. Technique 1: Pre-Mortem
  2. Technique 2: Assumption Reversal
  3. Technique 3: Red Team
  4. 10 Challenge Questions
  5. Technique 4: Attribution-vs-Consistency Check
  6. Technique 5: Ambient triggering on assertion-shaped patterns
  7. Technique 6: Cunningham's Law check (publish-rough-then-iterate)
  8. When to Use
  9. Output
Ships with 1 file
  • metadata.json
More from claude-skill-registry
All skills →
About this skill
What does the devils-advocate skill do?

Systematically challenge current assumptions before major decisions. Counters confirmation bias, groupthink, and overconfidence.

How do I install it?

Run `npx skills add majiayu000/claude-skill-registry --skill devils-advocate-haabe-mycelium-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.

Keep going