the-fool

jeffallan/claude-skills · updated May 13, 2026

MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.

$npx skills add https://github.com/jeffallan/claude-skills --skill the-fool
0 commentsdiscussion
summary

Structured critical reasoning to stress-test ideas, plans, and decisions through five distinct challenge modes.

  • Five reasoning modes: expose assumptions (Socratic), argue the other side (dialectic), find failure modes (pre-mortem), attack this (red team), and test evidence (falsification)
  • Two-step mode selection guides users to the right challenge approach based on their goal
  • Steelmans positions before challenging them, grounds objections in concrete reasoning, and synthesizes insigh
skill.md

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

how to use the-fool

How to use the-fool on Cursor

AI-first code editor with Composer

1

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

  • Cursor installed and configured on your development machine
  • Node.js version 16.0+ with npm package manager (verify with node --version)
  • Active project directory or workspace where you want to add the-fool
2

Execute installation command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/jeffallan/claude-skills --skill the-fool

The skills CLI fetches the-fool from GitHub repository jeffallan/claude-skills and configures it for Cursor.

3

Select Cursor when prompted

The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:

◆ Which agents do you want to install to?
│ ── Universal (.agents/skills) ── always included ────
│ • Amp
│ • Antigravity
│ • Cline
│ • Codex
│ ●Cursor(selected)
│ • Cursor
│ • Windsurf
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/the-fool

Reload or restart Cursor to activate the-fool. Access the skill through slash commands (e.g., /the-fool) or your agent's skill management interface.

Security & Verification Notice

We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.

Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.

List & Monetize Your Skill

Submit your Claude Code skill and start earning

GET_STARTED →

Use Cases

User Story & Requirements Generation

Create detailed user stories, acceptance criteria, and feature specs

Example

Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios

Reduce spec writing time by 50%, ensure comprehensive coverage

Competitive Analysis

Research competitors, compare features, identify gaps

Example

Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities

Complete competitive research in 2 hours instead of 2 days

Roadmap Prioritization

Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs

Example

Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale

Make data-driven prioritization decisions faster

Stakeholder Communication

Draft PRDs, status updates, and stakeholder presentations

Example

Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement

Save 3-5 hours/week on communication overhead

Implementation Guide

Prerequisites

  • Claude Desktop or compatible AI client
  • Access to product documentation and roadmap tools (Jira, Notion, etc.)
  • Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
  • Stakeholder contact information and communication channels

Time Estimate

30-60 minutes to see productivity improvements

Installation Steps

  1. 1.Install product management skill
  2. 2.Start with user story generation for known feature
  3. 3.Progress to competitive analysis: research 2-3 competitors
  4. 4.Use for roadmap prioritization: apply RICE/ICE scoring
  5. 5.Draft stakeholder communications and refine based on feedback
  6. 6.Build template library for recurring PM tasks
  7. 7.Share effective prompts with product team

Common Pitfalls

  • Not validating competitive research—verify facts before sharing
  • Accepting user stories without involving engineering team
  • Over-relying on frameworks without qualitative judgment
  • Not customizing outputs to company culture and communication style
  • Skipping stakeholder validation of generated requirements

Best Practices

✓ Do

  • +Validate research and competitive analysis with real data
  • +Collaborate with engineering when generating technical requirements
  • +Customize frameworks and templates to your company context
  • +Use skill for first drafts, refine with stakeholder input
  • +Document successful prompt patterns for PM tasks
  • +Combine AI efficiency with human judgment and intuition

✗ Don't

  • Don't publish competitive analysis without fact-checking
  • Don't finalize user stories without engineering review
  • Don't make prioritization decisions solely on AI scoring
  • Don't skip customer validation of generated requirements
  • Don't ignore company-specific context and culture

💡 Pro Tips

  • Provide context: company goals, constraints, customer feedback
  • Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
  • Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
  • Use skill for 70% generation + 30% customization to company needs

When to Use This

✓ Use When

Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.

✗ Avoid When

Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.

Learning Path

  1. 1Basic: user stories, feature specs, status updates
  2. 2Intermediate: competitive analysis, prioritization frameworks, PRDs
  3. 3Advanced: product strategy, go-to-market planning, OKR setting
  4. 4Expert: product vision, market positioning, business model innovation

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.767 reviews
  • Maya Bansal· Dec 24, 2024

    Useful defaults in the-fool — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • Valentina Zhang· Dec 24, 2024

    Keeps context tight: the-fool is the kind of skill you can hand to a new teammate without a long onboarding doc.

  • Dhruvi Jain· Dec 20, 2024

    the-fool reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • Isabella Sharma· Dec 20, 2024

    the-fool has been reliable in day-to-day use. Documentation quality is above average for community skills.

  • Anaya Dixit· Dec 16, 2024

    We added the-fool from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • Advait Perez· Dec 16, 2024

    the-fool reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • Advait Flores· Dec 8, 2024

    We added the-fool from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • Isabella Kapoor· Nov 15, 2024

    the-fool fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • Advait Gonzalez· Nov 15, 2024

    Registry listing for the-fool matched our evaluation — installs cleanly and behaves as described in the markdown.

  • Oshnikdeep· Nov 11, 2024

    I recommend the-fool for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

showing 1-10 of 67

1 / 7