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.
- License 许可
- MIT
- 最近更新
- 2026-11-08
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- the-fool
- license
- MIT
- metadata
- { "role": "expert", "scope": "review", "author": "https://github.com/Jeffallan", "domain": "workflow", "version": "1.0.0", "triggers": "play the fool, devil's advocate, challenge this, stress test, poke holes, what could go wrong, red team, pre-mortem, test my assumptions", "output-format": "report", "related-skills": "architecture-designer, code-reviewer, feature-forge" }
- description
- 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.
02 资源文件 6
- 参考文档references/dialectic-synthesis.md6.3 KB
- 参考文档references/evidence-audit.md8.3 KB
- 参考文档references/mode-selection-guide.md4.5 KB
- 参考文档references/pre-mortem-analysis.md7.9 KB
- 参考文档references/red-team-adversarial.md7.0 KB
- 参考文档references/socratic-questioning.md5.2 KB
03 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
- Identify — Extract the user's position from conversation context. Restate it as a steelmanned thesis for confirmation.
- Select — Use
AskUserQuestionwith 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.mdand 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
AskUserQuestionfor 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
AskUserQuestioncan 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
04 同仓库更多 Skills
vss-summarize-video
Use to summarize a recorded video via the LVS summarization microservice (HITL-gated) with a VLM fallback. Not for report generation or live RTSP captioning.
vss-setup-video-analytics-api
Use to deploy the vss-video-analytics-api REST service standalone (config-source, data-log bind, Elasticsearch, optional Kafka). Not for full warehouse deploy.
vss-setup-behavior-analytics
Use to deploy the vss-behavior-analytics service standalone (entrypoint, config-source, optional calibration). Not for the full warehouse deploy.
vss-search-archive
Use this skill to run top-level VSS fusion search on archived video, or to ingest video files / RTSP streams for search. Do NOT use for ad-hoc visual Q&A (use vss-ask-video), live captioning (use vss-deploy-dense-captioning), or video summarization and reports (use vss-summarize-video).
vss-query-analytics
Use this skill when reading video-analytics metrics, incidents, alerts, and sensor data via the VA-MCP server (port 9901). Not for live VLM or incident-range narrative reports.
vss-manage-video-io-storage
Use to call the VIOS REST API (sensor list, timelines, clip extraction, snapshots, add/delete sensors and streams). Not for VLM inference or search.