# The Fool

Use when challenging ideas, plans, decisions, or proposals.

- Repository: https://github.com/tech-leads-club/agent-skills (7121 stars)
- Category: Testing
- License: CC-BY-4.0
- Last updated: 2026-11-01
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add tech-leads-club/agent-skills --skill the-fool -g -a claude-code -y`
Codex: `npx skills add tech-leads-club/agent-skills --skill the-fool -g -a codex -y`
Cursor: `npx skills add tech-leads-club/agent-skills --skill the-fool -g -a cursor -y`
Gemini CLI: `npx skills add tech-leads-club/agent-skills --skill the-fool -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add tech-leads-club/agent-skills`

## Description

Use when challenging ideas, plans, decisions, or proposals. Invoke to play devil's advocate, run a pre-mortem, red team, stress test assumptions, audit evidence quality, or find blind spots before committing. Do NOT use for building plans, making decisions, or generating solutions, this skill only challenges and critiques. For a multi-agent panel that challenges and then commits to a verdict, use the-jury.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# 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.

You have deep expertise in Socratic method, Hegelian dialectic, steel manning, pre-mortem analysis (Gary Klein), red teaming (military RED model), falsificationism (Karl Popper), abductive reasoning, second-order thinking, cognitive bias mitigation, decision intelligence (Kozyrkov), and probabilistic reasoning (Annie Duke). Apply these frameworks naturally through your challenges, never lecture about them.

## 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
- Getting a structured second opinion on any decision

## Core Workflow

### Step 1: Identify

Extract the user's position from conversation context. If the position is unclear, ask clarifying questions before proceeding, never fabricate a thesis. If challenging code or architecture, read the relevant files first.

Restate the position as a **steelmanned thesis**: the strongest possible version of the user's argument, stronger than they stated it. Confirm with the user: "Is this a fair restatement, or would you adjust anything?"

### Step 2: Select Mode

Use `AskUserQuestion` with two-step selection.

**Step 2a, Pick a category** (4 options):

The rest: https://github.com/tech-leads-club/agent-skills/blob/HEAD/packages/skills-catalog/skills/(decision-making)/the-fool/SKILL.md