[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M72ZMWCFQSSV468JAMAM6MCE":3,"skill-same:01M72ZMWCFQSSV468JAMAM6MCE":78},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":32,"commitSha":33,"skillDirectory":34,"forksCount":13,"repositoryHtmlUrl":35,"repositoryHomepageUrl":6,"ownerHtmlUrl":36,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":37,"install":38,"resources":51},"01M72ZMWCFQSSV468JAMAM6MCE","the-fool",null,"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.","andrewthomastaylor\u002FSkills","andrewthomastaylor","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F249856925?v=4","01M72Z00NZWQPWA1TVXZPKXXWJ","01M72Z00PJ210Z6DAD1N93P2HG",0,"MIT","https:\u002F\u002Fgithub.com\u002Fandrewthomastaylor\u002FSkills\u002Fblob\u002Fmain\u002Fclaude-skills\u002Fskills\u002Fthe-fool\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: the-fool\ndescription: 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.\nlicense: MIT\nmetadata:\n  author: https:\u002F\u002Fgithub.com\u002FJeffallan\n  version: \"1.0.0\"\n  domain: workflow\n  triggers: play the fool, devil's advocate, challenge this, stress test, poke holes, what could go wrong, red team, pre-mortem, test my assumptions\n  role: expert\n  scope: review\n  output-format: report\n  related-skills: architecture-designer, code-reviewer, feature-forge\n---\n\n# The Fool\n\nThe 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.\n\n## When to Use This Skill\n\n- Stress-testing a plan, architecture, or strategy before committing\n- Challenging technology, vendor, or approach choices\n- Evaluating business proposals, value propositions, or strategies\n- Red-teaming a design before implementation\n- Auditing whether evidence actually supports a conclusion\n- Finding blind spots and unstated assumptions\n\n## Core Workflow\n\n1. **Identify** — Extract the user's position from conversation context. Restate it as a steelmanned thesis for confirmation.\n2. **Select** — Use `AskUserQuestion` with two-step mode selection (see below).\n3. **Challenge** — Apply the selected mode's method. Load the corresponding reference file for deep guidance.\n4. **Engage** — Present the 3-5 strongest challenges. Ask the user to respond before proceeding.\n5. **Synthesize** — Integrate insights into a strengthened position. Offer a second pass with a different mode.\n\n## Mode Selection\n\nUse `AskUserQuestion` to let the user choose how to challenge their idea.\n\n**Step 1 — Pick a category** (4 options):\n\n| Option | Description |\n|--------|-------------|\n| Question assumptions | Probe what's being taken for granted |\n| Build counter-arguments | Argue the strongest opposing position |\n| Find weaknesses | Anticipate how this fails or gets exploited |\n| You choose | Auto-recommend based on context |\n\n**Step 2 — Refine mode** (only when the category maps to 2 modes):\n\n- \"Question assumptions\" → Ask: \"Expose my assumptions\" (Socratic) vs \"Test the evidence\" (Falsification)\n- \"Find weaknesses\" → Ask: \"Find failure modes\" (Pre-mortem) vs \"Attack this\" (Red team)\n- \"Build counter-arguments\" → Skip step 2, proceed with Dialectic synthesis\n- \"You choose\" → Skip step 2, load `references\u002Fmode-selection-guide.md` and auto-recommend\n\n## 5 Reasoning Modes\n\n| Mode | Method | Output |\n|------|--------|--------|\n| Expose My Assumptions | Socratic questioning | Probing questions grouped by theme |\n| Argue the Other Side | Hegelian dialectic + steel manning | Counter-argument and synthesis proposal |\n| Find the Failure Modes | Pre-mortem + second-order thinking | Ranked failure narratives with mitigations |\n| Attack This | Red teaming | Adversary profile, attack vectors, defenses |\n| Test the Evidence | Falsificationism + evidence weighting | Claims audited with falsification criteria |\n\n## Reference Guide\n\n| Topic | Reference | Load When |\n|-------|-----------|-----------|\n| Socratic questioning | `references\u002Fsocratic-questioning.md` | \"Expose my assumptions\" selected |\n| Dialectic and synthesis | `references\u002Fdialectic-synthesis.md` | \"Argue the other side\" selected |\n| Pre-mortem analysis | `references\u002Fpre-mortem-analysis.md` | \"Find the failure modes\" selected |\n| Red team adversarial | `references\u002Fred-team-adversarial.md` | \"Attack this\" selected |\n| Evidence audit | `references\u002Fevidence-audit.md` | \"Test the evidence\" selected |\n| Mode selection guide | `references\u002Fmode-selection-guide.md` | \"You choose\" selected or auto-recommend needed |\n\n## Constraints\n\n### MUST DO\n- Steelman the thesis before challenging it (restate in strongest form)\n- Use `AskUserQuestion` for mode selection — never assume which mode\n- Ground challenges in specific, concrete reasoning (not vague \"what ifs\")\n- Maintain intellectual honesty — concede points that hold up\n- Drive toward synthesis or actionable output (never leave just objections)\n- Limit challenges to 3-5 strongest points (depth over breadth)\n- Ask user to engage with challenges before synthesizing\n\n### MUST NOT DO\n- Strawman the user's position\n- Generate challenges for the sake of disagreement\n- Be nihilistic or purely destructive\n- Stack minor objections to create false impression of weakness\n- Skip synthesis (never leave the user with just a pile of problems)\n- Override domain expertise with generic skepticism\n- Output mode selection as plain text when `AskUserQuestion` can provide structured options\n\n## Output Templates\n\nEach mode produces a structured deliverable. See the corresponding reference file for the full template.\n\n| Mode | Deliverable |\n|------|------------|\n| Expose My Assumptions | Assumption inventory + probing questions by theme + suggested experiments |\n| Argue the Other Side | Steelmanned thesis + antithesis argued + synthesis proposed + confidence rating |\n| Find the Failure Modes | Ranked failure narratives + early warning signs + mitigations + inversion check |\n| Attack This | Adversary profiles + ranked attack vectors + perverse incentives + defenses |\n| Test the Evidence | Claims extracted + falsification criteria + evidence grades + competing explanations |\n\nAfter any mode, the final output must include:\n\n1. **Steelmanned thesis** — The user's position restated in its strongest form\n2. **Challenges** — 3-5 strongest points from the selected mode\n3. **User response** — Space for the user to engage before synthesis\n4. **Synthesis** — Strengthened position integrating the challenges\n5. **Next steps** — Offer a second pass with a different mode if warranted\n\n## Knowledge Reference\n\nSocratic method, Hegelian dialectic, steel manning, pre-mortem analysis, red teaming, falsificationism, abductive reasoning, second-order thinking, cognitive biases, inversion technique\n\n[Documentation](https:\u002F\u002Fjeffallan.github.io\u002Fclaude-skills\u002Fskills\u002Fworkflow\u002Fthe-fool\u002F)\n","# The Fool\n\nThe 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.\n\n## When to Use This Skill\n\n- Stress-testing a plan, architecture, or strategy before committing\n- Challenging technology, vendor, or approach choices\n- Evaluating business proposals, value propositions, or strategies\n- Red-teaming a design before implementation\n- Auditing whether evidence actually supports a conclusion\n- Finding blind spots and unstated assumptions\n\n## Core Workflow\n\n1. **Identify** — Extract the user's position from conversation context. Restate it as a steelmanned thesis for confirmation.\n2. **Select** — Use `AskUserQuestion` with two-step mode selection (see below).\n3. **Challenge** — Apply the selected mode's method. Load the corresponding reference file for deep guidance.\n4. **Engage** — Present the 3-5 strongest challenges. Ask the user to respond before proceeding.\n5. **Synthesize** — Integrate insights into a strengthened position. Offer a second pass with a different mode.\n\n## Mode Selection\n\nUse `AskUserQuestion` to let the user choose how to challenge their idea.\n\n**Step 1 — Pick a category** (4 options):\n\n| Option | Description |\n|--------|-------------|\n| Question assumptions | Probe what's being taken for granted |\n| Build counter-arguments | Argue the strongest opposing position |\n| Find weaknesses | Anticipate how this fails or gets exploited |\n| You choose | Auto-recommend based on context |\n\n**Step 2 — Refine mode** (only when the category maps to 2 modes):\n\n- \"Question assumptions\" → Ask: \"Expose my assumptions\" (Socratic) vs \"Test the evidence\" (Falsification)\n- \"Find weaknesses\" → Ask: \"Find failure modes\" (Pre-mortem) vs \"Attack this\" (Red team)\n- \"Build counter-arguments\" → Skip step 2, proceed with Dialectic synthesis\n- \"You choose\" → Skip step 2, load `references\u002Fmode-selection-guide.md` and auto-recommend\n\n## 5 Reasoning Modes\n\n| Mode | Method | Output |\n|------|--------|--------|\n| Expose My Assumptions | Socratic questioning | Probing questions grouped by theme |\n| Argue the Other Side | Hegelian dialectic + steel manning | Counter-argument and synthesis proposal |\n| Find the Failure Modes | Pre-mortem + second-order thinking | Ranked failure narratives with mitigations |\n| Attack This | Red teaming | Adversary profile, attack vectors, defenses |\n| Test the Evidence | Falsificationism + evidence weighting | Claims audited with falsification criteria |\n\n## Reference Guide\n\n| Topic | Reference | Load When |\n|-------|-----------|-----------|\n| Socratic questioning | `references\u002Fsocratic-questioning.md` | \"Expose my assumptions\" selected |\n| Dialectic and synthesis | `references\u002Fdialectic-synthesis.md` | \"Argue the other side\" selected |\n| Pre-mortem analysis | `references\u002Fpre-mortem-analysis.md` | \"Find the failure modes\" selected |\n| Red team adversarial | `references\u002Fred-team-adversarial.md` | \"Attack this\" selected |\n| Evidence audit | `references\u002Fevidence-audit.md` | \"Test the evidence\" selected |\n| Mode selection guide | `references\u002Fmode-selection-guide.md` | \"You choose\" selected or auto-recommend needed |\n\n## Constraints\n\n### MUST DO\n- Steelman the thesis before challenging it (restate in strongest form)\n- Use `AskUserQuestion` for mode selection — never assume which mode\n- Ground challenges in specific, concrete reasoning (not vague \"what ifs\")\n- Maintain intellectual honesty — concede points that hold up\n- Drive toward synthesis or actionable output (never leave just objections)\n- Limit challenges to 3-5 strongest points (depth over breadth)\n- Ask user to engage with challenges before synthesizing\n\n### MUST NOT DO\n- Strawman the user's position\n- Generate challenges for the sake of disagreement\n- Be nihilistic or purely destructive\n- Stack minor objections to create false impression of weakness\n- Skip synthesis (never leave the user with just a pile of problems)\n- Override domain expertise with generic skepticism\n- Output mode selection as plain text when `AskUserQuestion` can provide structured options\n\n## Output Templates\n\nEach mode produces a structured deliverable. See the corresponding reference file for the full template.\n\n| Mode | Deliverable |\n|------|------------|\n| Expose My Assumptions | Assumption inventory + probing questions by theme + suggested experiments |\n| Argue the Other Side | Steelmanned thesis + antithesis argued + synthesis proposed + confidence rating |\n| Find the Failure Modes | Ranked failure narratives + early warning signs + mitigations + inversion check |\n| Attack This | Adversary profiles + ranked attack vectors + perverse incentives + defenses |\n| Test the Evidence | Claims extracted + falsification criteria + evidence grades + competing explanations |\n\nAfter any mode, the final output must include:\n\n1. **Steelmanned thesis** — The user's position restated in its strongest form\n2. **Challenges** — 3-5 strongest points from the selected mode\n3. **User response** — Space for the user to engage before synthesis\n4. **Synthesis** — Strengthened position integrating the challenges\n5. **Next steps** — Offer a second pass with a different mode if warranted\n\n## Knowledge Reference\n\nSocratic method, Hegelian dialectic, steel manning, pre-mortem analysis, red teaming, falsificationism, abductive reasoning, second-order thinking, cognitive biases, inversion technique\n\n[Documentation](https:\u002F\u002Fjeffallan.github.io\u002Fclaude-skills\u002Fskills\u002Fworkflow\u002Fthe-fool\u002F)\n",{"name":5,"license":14,"metadata":23,"description":7},{"role":24,"scope":25,"author":26,"domain":27,"version":28,"triggers":29,"output-format":30,"related-skills":31},"expert","review","https:\u002F\u002Fgithub.com\u002FJeffallan","workflow","1.0.0","play the fool, devil's advocate, challenge this, stress test, poke holes, what could go wrong, red team, pre-mortem, test my assumptions","report","architecture-designer, code-reviewer, feature-forge","main","cb7b4065bacb4b06224de86d509ccef568f68b79","claude-skills\u002Fskills\u002Fthe-fool","https:\u002F\u002Fgithub.com\u002Fandrewthomastaylor\u002FSkills","https:\u002F\u002Fgithub.com\u002Fandrewthomastaylor","2026-05-29 06:53:07",{"source":8,"skillName":5,"commands":39,"prompt":49,"zipAvailable":50},[40,43,46],{"tool":41,"command":42},"npx","npx skills add andrewthomastaylor\u002FSkills --skill the-fool",{"tool":44,"command":45},"bunx","bunx skills add andrewthomastaylor\u002FSkills --skill the-fool",{"tool":47,"command":48},"pnpm","pnpm dlx skills add andrewthomastaylor\u002FSkills --skill the-fool","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fandrewthomastaylor\u002FSkills\u002Fblob\u002Fmain\u002Fclaude-skills\u002Fskills\u002Fthe-fool\u002FSKILL.md",true,[52,58,62,66,70,74],{"path":53,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":56,"sourceHtmlUrl":57},"references\u002Fdialectic-synthesis.md","REFERENCE","参考文档",6456,"https:\u002F\u002Fgithub.com\u002Fandrewthomastaylor\u002FSkills\u002Fblob\u002Fmain\u002Fclaude-skills\u002Fskills\u002Fthe-fool\u002Freferences\u002Fdialectic-synthesis.md",{"path":59,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":60,"sourceHtmlUrl":61},"references\u002Fevidence-audit.md",8453,"https:\u002F\u002Fgithub.com\u002Fandrewthomastaylor\u002FSkills\u002Fblob\u002Fmain\u002Fclaude-skills\u002Fskills\u002Fthe-fool\u002Freferences\u002Fevidence-audit.md",{"path":63,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":64,"sourceHtmlUrl":65},"references\u002Fmode-selection-guide.md",4604,"https:\u002F\u002Fgithub.com\u002Fandrewthomastaylor\u002FSkills\u002Fblob\u002Fmain\u002Fclaude-skills\u002Fskills\u002Fthe-fool\u002Freferences\u002Fmode-selection-guide.md",{"path":67,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":68,"sourceHtmlUrl":69},"references\u002Fpre-mortem-analysis.md",8064,"https:\u002F\u002Fgithub.com\u002Fandrewthomastaylor\u002FSkills\u002Fblob\u002Fmain\u002Fclaude-skills\u002Fskills\u002Fthe-fool\u002Freferences\u002Fpre-mortem-analysis.md",{"path":71,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":72,"sourceHtmlUrl":73},"references\u002Fred-team-adversarial.md",7169,"https:\u002F\u002Fgithub.com\u002Fandrewthomastaylor\u002FSkills\u002Fblob\u002Fmain\u002Fclaude-skills\u002Fskills\u002Fthe-fool\u002Freferences\u002Fred-team-adversarial.md",{"path":75,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":76,"sourceHtmlUrl":77},"references\u002Fsocratic-questioning.md",5289,"https:\u002F\u002Fgithub.com\u002Fandrewthomastaylor\u002FSkills\u002Fblob\u002Fmain\u002Fclaude-skills\u002Fskills\u002Fthe-fool\u002Freferences\u002Fsocratic-questioning.md",[79,88,96,103,110,117],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":83,"licenseFileUrl":84,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":18},"01M732GDQJ0CWHBAW4D7ENMA3N","skill-creator","Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fandrewthomastaylor\u002FSkills\u002Fblob\u002Fmain\u002Fskill-creator\u002Fskills\u002Fskill-creator\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fandrewthomastaylor\u002FSkills\u002Fblob\u002Fmain\u002Fskill-creator\u002Fskills\u002Fskill-creator\u002FSKILL.md",[],[],{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":92,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":18},"01M731QVEE2QCT389Z3X1JWFVQ","humanizer-zh","去除文本中的 AI 生成痕迹。适用于编辑或审阅文本，使其听起来更自然、更像人类书写。\n基于维基百科的\"AI 写作特征\"综合指南。检测并修复以下模式：夸大的象征意义、\n宣传性语言、以 -ing 结尾的肤浅分析、模糊的归因、破折号过度使用、三段式法则、\nAI 词汇、否定式排比、过多的连接性短语。","https:\u002F\u002Fgithub.com\u002Fandrewthomastaylor\u002FSkills\u002Fblob\u002Fmain\u002Fhumanizer-zh\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fandrewthomastaylor\u002FSkills\u002Fblob\u002Fmain\u002Fhumanizer-zh\u002FSKILL.md",[],[],{"skillNo":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":83,"licenseFileUrl":6,"sourceHtmlUrl":100,"categories":101,"keywords":102,"publishedAt":18},"01M731AMWEC72GFFNFS55F0TTC","returns-reverse-logistics","Codified expertise for returns authorization, receipt and inspection, disposition decisions, refund processing, fraud detection, and warranty claims management. Informed by returns operations managers with 15+ years experience. Includes grading frameworks, disposition economics, fraud pattern recognition, and vendor recovery processes. Use when handling product returns, reverse logistics, refund decisions, return fraud detection, or warranty claims.","https:\u002F\u002Fgithub.com\u002Fandrewthomastaylor\u002FSkills\u002Fblob\u002Fmain\u002Feverything-claude-code\u002Fskills\u002Freturns-reverse-logistics\u002FSKILL.md",[],[],{"skillNo":104,"name":105,"nameZh":6,"description":106,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":83,"licenseFileUrl":6,"sourceHtmlUrl":107,"categories":108,"keywords":109,"publishedAt":18},"01M7319BJFM3CBX39C85QWSMD1","quality-nonconformance","Codified expertise for quality control, non-conformance investigation, root cause analysis, corrective action, and supplier quality management in regulated manufacturing. Informed by quality engineers with 15+ years experience across FDA, IATF 16949, and AS9100 environments. Includes NCR lifecycle management, CAPA systems, SPC interpretation, and audit methodology. Use when investigating non-conformances, performing root cause analysis, managing CAPAs, interpreting SPC data, or handling supplier quality issues.","https:\u002F\u002Fgithub.com\u002Fandrewthomastaylor\u002FSkills\u002Fblob\u002Fmain\u002Feverything-claude-code\u002Fskills\u002Fquality-nonconformance\u002FSKILL.md",[],[],{"skillNo":111,"name":112,"nameZh":6,"description":113,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":83,"licenseFileUrl":6,"sourceHtmlUrl":114,"categories":115,"keywords":116,"publishedAt":18},"01M7318DPHWK6CEVCVT7PHNKDZ","production-scheduling","Codified expertise for production scheduling, job sequencing, line balancing, changeover optimization, and bottleneck resolution in discrete and batch manufacturing. Informed by production schedulers with 15+ years experience. Includes TOC\u002Fdrum-buffer-rope, SMED, OEE analysis, disruption response frameworks, and ERP\u002FMES interaction patterns. Use when scheduling production, resolving bottlenecks, optimizing changeovers, responding to disruptions, or balancing manufacturing lines.","https:\u002F\u002Fgithub.com\u002Fandrewthomastaylor\u002FSkills\u002Fblob\u002Fmain\u002Feverything-claude-code\u002Fskills\u002Fproduction-scheduling\u002FSKILL.md",[],[],{"skillNo":118,"name":119,"nameZh":6,"description":120,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":83,"licenseFileUrl":6,"sourceHtmlUrl":121,"categories":122,"keywords":123,"publishedAt":18},"01M7315ZE0J0AB6KTQAFGCYF5V","logistics-exception-management","Codified expertise for handling freight exceptions, shipment delays, damages, losses, and carrier disputes. Informed by logistics professionals with 15+ years operational experience. Includes escalation protocols, carrier-specific behaviors, claims procedures, and judgment frameworks. Use when handling shipping exceptions, freight claims, delivery issues, or carrier disputes.","https:\u002F\u002Fgithub.com\u002Fandrewthomastaylor\u002FSkills\u002Fblob\u002Fmain\u002Feverything-claude-code\u002Fskills\u002Flogistics-exception-management\u002FSKILL.md",[],[]]