Token导航 LogoToken导航TokenDH.com
待分类只读github未标认证来源可访问许可证需确认审计通过

critical-reasoning批判性推理

Agent Skill

critical-reasoning 用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要围绕仓库状态、代码变更或协作事项进行整理时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

总安装

1,236

周安装

50

GitHub Stars

25

下载量

388
CodexClaudeCursorGemini CLI

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:critical-reasoning(批判性推理)
来源仓库:https://github.com/andrewgleave/skills
仓库路径:skills/critical-reasoning
安装命令:
npx skills add https://github.com/andrewgleave/skills --skill critical-reasoning
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/andrewgleave/skills --skill critical-reasoning

简介

该技能应用波普尔式批判理性主义,帮助用户识别认知偏差、检验假设有效性。

  • 适用于科学研究、哲学思辨或复杂问题拆解,培养可证伪与持续修正的思维习惯。
  • 核心原则包括可证伪性要求、理论优选标准与错误驱动的知识进化观。
  • 需明确其不提供确定性答案,而是构建抗辩式思维训练环境。
  • critical-reasoning 属于待分类类 Skill,可作为该场景下的辅助能力补充。

SKILL.md

Critical Reasoning

Apply Popperian critical rationalism to help users reason clearly, identify errors, and refine their understanding.

Core Approach

Knowledge grows through conjecture and refutation - proposing bold ideas and subjecting them to severe criticism. The goal is not to prove things true (impossible) but to identify and eliminate errors, arriving at theories that have survived criticism.

Key Principles

  1. Falsifiability: Rational claims must be criticizable. Ask: what would refute this?
  2. Critical preference: Prefer theories that explain more, predict more precisely, and have survived more severe tests
  3. Fallibilism: All knowledge is tentative. We're probably wrong in ways we don't yet understand
  4. Problems first: Start with problems, not observations. What problem is this solving?
  5. Good explanations: Prefer explanations that are hard to vary - where all details play a functional role

When to Surface Criticisms

Always engage when explicitly asked: "help me think through", "any flaws", "critique this", etc.

Proactively surface criticisms when they are material - when errors could significantly affect the user's goals:

  • Unfalsifiable claims presented as factual
  • Logical contradictions in the reasoning
  • Arguments that prove too much (would prove false things if valid)
  • Key assumptions that are unexamined
  • Conclusions that don't follow from premises

Be judicious when not explicitly asked: Not every conversation needs epistemological scrutiny. Surface errors that matter; don't nitpick or derail.

Applying the Method

Examining Arguments

  1. Identify the claim: What exactly is being asserted?
  2. Steel-man first: Construct the strongest version of the argument before criticizing. What is the best case for this position? What would a thoughtful proponent say? Only after articulating the strongest form should criticism proceed.
  3. Test falsifiability: What would have to be true for this to be false?
  4. Check explanation quality: Is it hard to vary? Could it explain the opposite?
  5. Look for error patterns: Ad hoc modifications, justificationism, straw men, etc.
  6. Consider alternatives: What other explanations exist? Why prefer this one?

Helping Users Think Through Problems

  1. Clarify the problem: What exactly needs solving? (Problems, not observations, come first)
  2. Elicit conjectures: What tentative solutions exist?
  3. Stress test: What criticism could each conjecture face? What would refute it?
  4. Compare critically: Which conjecture survives criticism best? Why?
  5. Identify new problems: What questions does the surviving conjecture raise?

Response Style

Adapt to context:

  • For quick checks: Direct identification of issues
  • For complex reasoning: Structured analysis
  • For exploration: Socratic questioning
  • For refinement: Collaborative iteration

Always explain *why* something is an error - connect to epistemological principles so users can internalize the method.

Reference Material

Load as needed based on the task:

  • popper.md: Core Popperian concepts - falsifiability, critical preference, verisimilitude, the growth of knowledge, three worlds, rationality as criticism
  • deutsch.md: Deutsch's refinements - good explanations (hard to vary), reach, problems are soluble, unbounded fallibilism
  • error-patterns.md: Common fallacies and errors through a CR lens - unfalsifiable claims, ad hoc modifications, straw men, bad explanations, appeals to authority/popularity/tradition, etc.

适合场景

01

用户想查找某类 Agent Skill 时

02

需要根据任务场景推荐可安装能力包时

03

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

Codex

36.67%
按下载量换算142

Claude

27.22%
按下载量换算106

Cursor

20.1%
按下载量换算78

Gemini CLI

9.64%
按下载量换算37

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

只读

该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills