The Fool
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.
MCP get_skill({ skillId: "the-fool-cb436fd0" })Use this skill with your agent
Create a free account and connect via MCP
# 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 1. **Identify** — Extract the user's position from conversation context. Restate it as a steelmanned thesis for confirmation. 2. **Select** — Use `AskUserQuestion` with two-step mode selection (see below). 3. **Challenge** — Apply the selected mode's method. Load the corresponding reference file for deep guidance. 4. **Engage** — Present the 3-5 strongest challenges. Ask the user to respond before proceeding. 5. **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: 1. **Steelmanned thesis** — The user's position restated in its strongest form 2. **Challenges** — 3-5 strongest points from the selected mode 3. **User response** — Space for the user to engage before synthesis 4. **Synthesis** — Strengthened position integrating the challenges 5. **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](https://jeffallan.github.io/claude-skills/skills/workflow/the-fool/)
Related Skills
More skills in Business, Marketing & Sales
Ab Testing
When the user wants to plan, design, or implement an A/B test or experiment, or build a growth experimentation program. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "should I test this," "which version is better," "test two versions," "statistical significance," "how long should I run this test," "growth experiments," "experiment velocity," "experiment backlog," "ICE score," "experimentation program," or "experiment playbook." Use this whenever someone is comparing two approaches and wants to measure which performs better, or when they want to build a systematic experimentation practice. For tracking implementation, see analytics. For page-level conversion optimization, see cro.
Ab Test Setup
When the user wants to plan, design, or implement an A/B test or experiment. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "conversion experiment," "statistical significance," or "test this." For tracking implementation, see analytics-tracking.
Ab Test Setup
Ab Test Setup linked from Corey Haines marketing skills, with the upstream skill instructions available on GitHub.
Ab Test Store Listing
When the user wants to A/B test App Store product page elements to improve conversion rate. Also use when the user mentions "A/B test", "product page optimization", "test my screenshots", "test my icon", "conversion rate optimization", "CPP", or "custom product pages". For screenshot design, see screenshot-optimization. For metadata optimization, see metadata-optimization.
Account Research
Research a company or person and get actionable sales intel. Works standalone with web search, supercharged when you connect enrichment tools or your CRM. Trigger with "research [company]", "look up [person]", "intel on [prospect]", "who is [name] at [company]", or "tell me about [company]".
Account Research
Research a company using Common Room data. Triggers on 'research [company]', 'tell me about [domain]', 'pull up signals for [account]', 'what's going on with [company]', or any account-level question.
Explore Other Categories
Skills from other categories with shared topics
Angular Architect
Generates Angular 17+ standalone components, configures advanced routing with lazy loading and guards, implements NgRx state management, applies RxJS patterns, and optimizes bundle performance. Use when building Angular 17+ applications with standalone components or signals, setting up NgRx stores, establishing RxJS reactive patterns, performance tuning, or writing Angular tests for enterprise apps.
API Designer
Use when designing REST or GraphQL APIs, creating OpenAPI specifications, or planning API architecture. Invoke for resource modeling, versioning strategies, pagination patterns, error handling standards.
Architecture Designer
Use when designing new high-level system architecture, reviewing existing designs, or making architectural decisions. Invoke to create architecture diagrams, write Architecture Decision Records (ADRs), evaluate technology trade-offs, design component interactions, and plan for scalability. Use for system design, architecture review, microservices structuring, ADR authoring, scalability planning, and infrastructure pattern selection — distinct from code-level design patterns or database-only design tasks.