Token导航 LogoToken导航

Agent Skill · 待分类

critical-reasoning(批判性推理)

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

critical-reasoning 是待分类类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为只读;许可证信息还不明确,第三方扫描已通过,按安装量在待分类类的 11,209 个 Skill 里排第 2,991。

总安装 1,236周安装 50GitHub Stars 25下载 388核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
unknown

安装方式

通过对话安装

复制提示词发给支持本地命令或 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

这个 Skill 是做什么的

这个 Skill 的分类还没最终确定,用法以来源仓库的说明为准。

该技能应用波普尔式批判理性主义,帮助用户识别认知偏差、检验假设有效性。适用于科学研究、哲学思辨或复杂问题拆解,培养可证伪与持续修正的思维习惯。核心原则包括可证伪性要求、理论优选标准与错误驱动的知识进化观。需明确其不提供确定性答案,而是构建抗辩式思维训练环境。

critical-reasoning 属于待分类类 Skill,可作为该场景下的辅助能力补充。

来源仓库内路径:skills/critical-reasoning

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 Codex、Claude、Cursor、Gemini CLI;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add https://github.com/andrewgleave/skills --skill critical-reasoning;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它标注为只读,先用只读任务试一次,确认行为符合预期再扩大使用范围。

常见问题

6 条

critical-reasoning 怎么安装?

在终端执行 npx skills add https://github.com/andrewgleave/skills --skill critical-reasoning。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

critical-reasoning 支持哪些 AI 工具?

公开资料标注支持 Codex、Claude、Cursor、Gemini CLI。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

critical-reasoning 需要什么权限?

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

critical-reasoning 是免费的吗?

公开资料没有标注明确许可证,收费和商用限制都无法确认。正式使用前请到来源仓库核对授权说明。

critical-reasoning 用的人多吗?

公开数据是累计安装 1,236 次,近一周安装 50 次,下载 388 次,GitHub 25 星。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

critical-reasoning 安全吗?

第三方扫描结果为通过,但这只覆盖已知的静态检查项,不能替代自己读一遍源码和安装命令。

值得选的地方和要先想清楚的地方

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。
  • 第三方扫描已通过,常见的高风险行为没有命中。
  • 标注为只读权限,试用阶段不容易误改本地文件。

先想清楚的地方

  • 许可证没有明确标注,能不能商用、能不能再分发都不确定。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理待分类类任务、又不想每次都手写提示词的人。
  • 只想先试试效果、不希望它改动本地文件的人。

不太适合

  • 需要明确授权才能用到公司项目里的场景。
  • 需要厂商级技术支持和 SLA 的生产系统。

待分类类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
infsh-cli

infsh CLI · Codex、Claude

4,374,576382权限未标注未明确未收录
ai-video-generation

AI 视频生成 · Codex、Claude

4,313,376382调用外部服务未明确有提醒
lark-openapi-explorer

云雀 OpenAPI 浏览器 · Codex、Claude

2,064,1209,011需要联网未明确有提醒
lark-workflow-standup-report

Lark 工作流程站立报告 · Codex、Claude

2,041,6328,978需要联网未明确通过
use-my-browser

使用我的浏览器 · Codex、Claude

1,848,49140操作浏览器未明确未通过
critical-reasoning

批判性推理 · 本页

1,23625只读未明确通过

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

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.

平台分布

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