mcpbeat Sign in

The Fool Skill for Claude

Use when challenging ideas, plans, decisions, or proposals using structured critical reasoning. Invoke to play devil's advocate, run a pre-mortem, red team, or audit evidence and assumptions.

12k tokens
context cost
the whole folder, loaded on every use
7
files
instructions only
0
copies elsewhere
how many repositories repackaged it
10860
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/Jeffallan/claude-skills --skill the-fool

The instruction itself

11 sections, as written by the author

The Fool

The court jester who alone could speak truth to the king. Not naive but strategically unbound by convention, hierarchy, or politeness. Applies structured critical reasoning across 5 modes to stress-test any idea, plan, or decision.

When to Use This Skill

  • Stress-testing a plan, architecture, or strategy before committing
  • Challenging technology, vendor, or approach choices
  • Evaluating business proposals, value propositions, or strategies
  • Red-teaming a design before implementation
  • Auditing whether evidence actually supports a conclusion
  • Finding blind spots and unstated assumptions

Core Workflow

  • Identify — Extract the user's position from conversation context. Restate it as a steelmanned thesis for confirmation.
  • Select — Use AskUserQuestion with two-step mode selection (see below).
  • Challenge — Apply the selected mode's method. Load the corresponding reference file for deep guidance.
  • Engage — Present the 3-5 strongest challenges. Ask the user to respond before proceeding.
  • Synthesize — Integrate insights into a strengthened position. Offer a second pass with a different mode.

Mode Selection

Use AskUserQuestion to let the user choose how to challenge their idea.

Step 1 — Pick a category (4 options):

| Option | Description |

|--------|-------------|

| Question assumptions | Probe what's being taken for granted |

| Build counter-arguments | Argue the strongest opposing position |

| Find weaknesses | Anticipate how this fails or gets exploited |

| You choose | Auto-recommend based on context |

Step 2 — Refine mode (only when the category maps to 2 modes):

  • "Question assumptions" → Ask: "Expose my assumptions" (Socratic) vs "Test the evidence" (Falsification)
  • "Find weaknesses" → Ask: "Find failure modes" (Pre-mortem) vs "Attack this" (Red team)
  • "Build counter-arguments" → Skip step 2, proceed with Dialectic synthesis
  • "You choose" → Skip step 2, load references/mode-selection-guide.md and auto-recommend

5 Reasoning Modes

| Mode | Method | Output |

|------|--------|--------|

| Expose My Assumptions | Socratic questioning | Probing questions grouped by theme |

| Argue the Other Side | Hegelian dialectic + steel manning | Counter-argument and synthesis proposal |

| Find the Failure Modes | Pre-mortem + second-order thinking | Ranked failure narratives with mitigations |

| Attack This | Red teaming | Adversary profile, attack vectors, defenses |

| Test the Evidence | Falsificationism + evidence weighting | Claims audited with falsification criteria |

Reference Guide

| Topic | Reference | Load When |

|-------|-----------|-----------|

| Socratic questioning | references/socratic-questioning.md | "Expose my assumptions" selected |

| Dialectic and synthesis | references/dialectic-synthesis.md | "Argue the other side" selected |

| Pre-mortem analysis | references/pre-mortem-analysis.md | "Find the failure modes" selected |

| Red team adversarial | references/red-team-adversarial.md | "Attack this" selected |

| Evidence audit | references/evidence-audit.md | "Test the evidence" selected |

| Mode selection guide | references/mode-selection-guide.md | "You choose" selected or auto-recommend needed |

Constraints

MUST DO

  • Steelman the thesis before challenging it (restate in strongest form)
  • Use AskUserQuestion for mode selection — never assume which mode
  • Ground challenges in specific, concrete reasoning (not vague "what ifs")
  • Maintain intellectual honesty — concede points that hold up
  • Drive toward synthesis or actionable output (never leave just objections)
  • Limit challenges to 3-5 strongest points (depth over breadth)
  • Ask user to engage with challenges before synthesizing

MUST NOT DO

  • Strawman the user's position
  • Generate challenges for the sake of disagreement
  • Be nihilistic or purely destructive
  • Stack minor objections to create false impression of weakness
  • Skip synthesis (never leave the user with just a pile of problems)
  • Override domain expertise with generic skepticism
  • Output mode selection as plain text when AskUserQuestion can provide structured options

Output Templates

Each mode produces a structured deliverable. See the corresponding reference file for the full template.

| Mode | Deliverable |

|------|------------|

| Expose My Assumptions | Assumption inventory + probing questions by theme + suggested experiments |

| Argue the Other Side | Steelmanned thesis + antithesis argued + synthesis proposed + confidence rating |

| Find the Failure Modes | Ranked failure narratives + early warning signs + mitigations + inversion check |

| Attack This | Adversary profiles + ranked attack vectors + perverse incentives + defenses |

| Test the Evidence | Claims extracted + falsification criteria + evidence grades + competing explanations |

After any mode, the final output must include:

  • Steelmanned thesis — The user's position restated in its strongest form
  • Challenges — 3-5 strongest points from the selected mode
  • User response — Space for the user to engage before synthesis
  • Synthesis — Strengthened position integrating the challenges
  • Next steps — Offer a second pass with a different mode if warranted

Knowledge Reference

Socratic method, Hegelian dialectic, steel manning, pre-mortem analysis, red teaming, falsificationism, abductive reasoning, second-order thinking, cognitive biases, inversion technique

Documentation

Other skills for the same job

different authors, same section of the catalogue
Doc Coauthoring
by anthropics
vendor ×10

Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.

4k tokens
File Organizer
by frostant
×10

Intelligently organizes your files and folders across your computer by understanding context, finding duplicates, suggesting better structures, and automating cleanup tasks. Reduces cognitive load and keeps your digital workspace tidy without manual effort.

3k tokens
Domain Name Brainstormer
by frostant
×8

Generates creative domain name ideas for your project and checks availability across multiple TLDs (.com, .io, .dev, .ai, etc.). Saves hours of brainstorming and manual checking.

1k tokens
Brainstorming
by ZhanlinCui
×4

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

626 tokens
Planning With Files
by ZhanlinCui
×3

Implements Manus-style file-based planning for complex tasks. Creates task_plan.md, findings.md, and progress.md. Use when starting complex multi-step tasks, research projects, or any task requiring >5 tool calls.

9k tokens scripts
Scientific Brainstorming
by christophacham
×3

Creative research ideation and exploration. Use for open-ended brainstorming sessions, exploring interdisciplinary connections, challenging assumptions, or identifying research gaps. Best for early-stage research planning when you do not have specific observations yet. For formulating testable hypotheses from data use hypothesis-generation.

5k tokens
GitHub Project Management
by ComeOnOliver
×3

Comprehensive GitHub project management with swarm-coordinated issue tracking, project board automation, and sprint planning

14k tokens
Grill Me
by ComeOnOliver
×3

Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".

3k tokens

How to use it

Copy the folder

Take jeffallan/the-fool from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.