Challenge that
Skill onfire7777/universal-ai-skills-library/skills/challenge-that
Router-first AI skill system for Codex, Claude, Cursor, Hermes, Paperclip, OpenCode, and local AI stacks: search, preflight-route, and load 1,812 skills on demand without duplicating the corpus.
npx -y skills add onfire7777/universal-ai-skills-library --skill challenge-thatAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 13 stars13 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Force critical evaluation of any proposal, decision, or approach from 5 adversarial perspectives. Use when you've just agreed to something, accepted a plan, or want to stress-test an idea before committing. Triggers on: 'challenge this', 'stress test', 'devil's advocate', 'what could go wrong', 'poke holes', 'is this a good idea', 'evaluate this critically'.
SKILL.md
2.4 KB, 471 tokens by cl100k_base, as published. Nobody here has run it
Challenge That
Force critical evaluation by analyzing from multiple adversarial perspectives.
When Invoked
- Identify what was just accepted/proposed in this conversation
- State it clearly: "Challenging: [the proposal/decision]"
- Analyze from each of the five perspectives below
- Synthesize into actionable concerns
- Ask: "Which concerns should we address before proceeding?"
The Five Hats
| Hat | Focus | Key Questions |
|---|---|---|
| 🔴 Skeptic | Evidence & proof | "What evidence supports this? Has this been validated? Are we guessing?" |
| 🟡 Pragmatist | Cost/benefit | "Is this the simplest fix? What's the maintenance burden? Is it worth it?" |
| 🟢 Edge Case Hunter | Failure modes | "What breaks this? What's the worst case? What did we miss?" |
| 🔵 Structural Critic | Architecture | "Is this the right location? Does it fit the existing design? Will it cause problems elsewhere?" |
| 🟣 Root Cause Analyst | Problem diagnosis | "Is the problem correctly identified? Are we treating symptoms? What's the actual cause?" |
Output Format
## Challenging: [proposal/decision being challenged]
### 🔴 Skeptic
[Challenge from evidence/proof perspective]
### 🟡 Pragmatist
[Challenge from cost/benefit perspective]
### 🟢 Edge Case Hunter
[Challenge from failure modes perspective]
### 🔵 Structural Critic
[Challenge from architecture perspective]
### 🟣 Root Cause Analyst
[Challenge from problem diagnosis perspective]
---
**Key Concerns:**
1. [Most significant concern]
2. [Second concern]
3. [Third concern]
Which of these should we address before proceeding?
Rules
🚨 Be genuinely adversarial. Don't softball the challenges. If a perspective finds nothing wrong, say so—but look hard first. 🚨 Challenge the proposal, not the person. Focus on the idea's weaknesses, not who suggested it. 🚨 Provide actionable output. Each challenge should point to something that could be investigated or changed.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.