Index of every page on this site: llms.txt
All skills
jeffallan avatar

/the-fool

@67c1961
by jeffallanjeffallan/claude-skills12k stars
1,202
Run it yourself

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.

Use this Skill: https://skilld.dev/gh/jeffallan/claude-skills/the-fool

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈50 tokens for metadata: the name and description. ≈1.4k when used: this file. ≈10k more on demand in 6 files.

Description uses 2.5% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈202 characters, or 2.5%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

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

Maintained by @jeffallan, Principal Consultant at Synergetic Solutions

Documentation

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

1 alert1mo5 checks · Risk CRITICAL
  • Gen Agent Trust Hub1mo

    The skill consists of instructional Markdown files for critical reasoning frameworks. No executable code, scripts, or malicious patterns were identified in the source files.

  • Socket1mo

    No alerts

  • Snyk1mo

    Risk: LOW · No issues

  • Runlayer9mo

    7/7 files flagged

  • ZeroLeaks7mo

    Score: 93/100 · 2 sections analyzed

Signed by skilld at 67c1961. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 4 days ago.

Activeupdated 2 months ago
Other metadata
metadata
{
  "author": "https://github.com/Jeffallan",
  "company": "https://synergetic.solutions",
  "version": "1.0.0",
  "domain": "workflow",
  "triggers": "play the fool, devil's advocate, challenge this, stress test, poke holes, what could go wrong, red team, pre-mortem, test my assumptions",
  "role": "expert",
  "scope": "review",
  "output-format": "report",
  "related-skills": "architecture-designer, code-reviewer, feature-forge"
}

README badge

README badge for jeffallan/claude-skills/the-fool