Token导航 LogoToken导航

Agent Skill · 研究检索

clinical-diagnostic-reasoning(临床诊断推理)

clinical-diagnostic-reasoning 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

clinical-diagnostic-reasoning 是研究检索类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为只读;许可证信息还不明确,第三方扫描已通过,按安装量在研究检索类的 73,675 个 Skill 里排第 37,089。

总安装 1,805周安装 73GitHub Stars 98下载 566核验 2026-05-01

安装说明

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

安装方式

通过对话安装

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

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

命令行安装

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

skills.shnpx skills
npx skills add https://github.com/erichowens/some_claude_skills --skill clinical-diagnostic-reasoning

这个 Skill 是做什么的

研究检索类 Skill 主要解决「找资料、核对事实、把来源整理清楚」的问题,通常会让助手先检索再总结。

clinical-diagnostic-reasoning 提升诊断准确率,识别并纠正临床思维中的系统性认知偏差。适合在 Codex、Claude、Cursor、Gemini CLI 中辅助诊断决策与治疗规划。应用于病例复盘、医学教育与质量安全改进等非技术性临床支持场景。

不提供基础病理知识或操作技能,聚焦高阶推理过程优化。适用宿主包括 Codex、Claude、Cursor、Gemini CLI,接入前应确认版本、权限和运行环境要求。

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

上手步骤

4 步
  1. 1

    确认自己的宿主工具

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

  2. 2

    拿到安装命令

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

  3. 3

    安装后重启宿主

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

  4. 4

    按最小权限试用

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

常见问题

6 条

clinical-diagnostic-reasoning 怎么安装?

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

clinical-diagnostic-reasoning 支持哪些 AI 工具?

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

clinical-diagnostic-reasoning 需要什么权限?

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

clinical-diagnostic-reasoning 是免费的吗?

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

clinical-diagnostic-reasoning 用的人多吗?

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

clinical-diagnostic-reasoning 安全吗?

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

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

值得选的地方

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

先想清楚的地方

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

适不适合你

更适合

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

不太适合

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

研究检索类 Skill 对比

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

寻找技能 · Codex、Claude

31,199,81316,486操作浏览器MIT有提醒
self-improving-agent

自我改进 Agent · OpenClaw

16,464,0023,396接触敏感数据MIT-0通过
soultrace

灵魂追踪 · Codex、Claude

7,588,94412需要联网未明确有提醒
self-improving

自我完善 · OpenClaw

6,829,2841,046需要联网MIT-0通过
microsoft-foundry

微软代工厂 · Codex、Claude

6,614,144764调用外部服务未明确有提醒
clinical-diagnostic-reasoning

临床诊断推理 · 本页

1,80598只读未明确通过

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

SKILL.md 原文

Clinical Diagnostic Reasoning

Improve diagnostic accuracy and treatment decisions by recognizing and overcoming systematic cognitive errors in clinical thinking.

When to Use

✅ Use for:

  • Diagnostic decision-making in clinical practice
  • Treatment planning and therapeutic choices
  • Case review and error analysis
  • Medical education on clinical reasoning
  • Patient communication and shared decision-making
  • Quality improvement and patient safety initiatives

❌ NOT for:

  • Learning basic medical facts or pathophysiology
  • Technical procedures or surgical skills
  • Healthcare administration or policy
  • Non-physician clinical roles without diagnostic responsibility
  • Population health management without individual patient focus

Core Process

Diagnostic Reasoning Flow

New patient presentation
    ↓
┌───[Gather information through language/history]
│   ↓
│   Does presentation suggest standard algorithm?
│   ├─ NO → Continue hypothesis generation
│   │         ↓
│   │         Develop differential diagnosis
│   │         ↓
│   │         [Proceed to bias check]
│   │
│   └─ YES → Does patient context match algorithm assumptions?
│             ├─ YES → Apply algorithm
│             │         ↓
│             │         Monitor outcomes
│             │         ↓
│             │         [Proceed to bias check]
│             │
│             └─ NO → What patient-specific factors differ?
│                     ↓
│                     Does evidence justify deviation?
│                     ├─ YES → Document rationale and modify
│                     └─ NO → Apply algorithm; reconsider if new data
│
└─── [BIAS CHECK - Always perform]
     ↓
     Am I anchored to initial impression?
     ├─ POSSIBLY → Reassess case without initial anchor
     │
     Have I found one explanation and stopped searching?
     ├─ YES → Continue search: "What else could this be?"
     │         "Does this explain ALL findings?"
     │
     Am I pattern-matching from recent/memorable case?
     ├─ YES → List specific differences between cases
     │
     Am I stereotyping this patient?
     ├─ POSSIBLY → Reset: Evaluate symptoms independently
     │
     Do I feel compelled to "do something"?
     ├─ YES → Is action justified by evidence or anxiety?
     │         Is watchful waiting appropriate?
     │
     Have I sought disconfirming evidence?
     └─ NO → Actively look for data that contradicts working diagnosis

Case-Based Error Analysis Flow

Clinical error occurred
    ↓
What was the error?
    ├─ Wrong diagnosis
    ├─ Inappropriate treatment
    └─ Missed diagnosis
    ↓
Was this a knowledge gap or thinking error?
    ├─ KNOWLEDGE GAP → Address through study
    │                   (Not the focus of this skill)
    │
    └─ THINKING ERROR → Which cognitive bias operated?
                        ↓
                        ┌─ Anchoring? (stuck on initial impression)
                        ├─ Satisfaction of search? (stopped too early)
                        ├─ Availability? (recent case pattern-match)
                        ├─ Attribution? (stereotyped patient)
                        └─ Commission? (unnecessary action)
                        ↓
                        Was error preventable with current knowledge?
                        ├─ YES → How could bias have been recognized?
                        │         ↓
                        │         Extract generalizable lesson
                        │         ↓
                        │         Apply to future similar situations
                        │
                        └─ NO → Document for learning, not applicable

Patient Communication Flow

Need to present medical information
    ↓
What decision does patient need to make?
    ↓
Identify equivalent framings:
    - Positive frame (% success/survival)
    - Negative frame (% failure/mortality)
    - Absolute numbers
    - Relative risk
    ↓
Which framing facilitates genuine understanding?
    ↓
Is my framing choice unintentionally biasing decision?
    ├─ YES → Present multiple equivalent framings
    │         Allow patient to process from different angles
    │
    └─ UNCERTAIN → Present both positive and negative frames
                    Verify patient comprehension
                    ↓
                    "What is your understanding of the risks/benefits?"

Anti-Patterns

Satisfaction of Search

Novice approach: Finds one clinically interesting explanation and stops diagnostic inquiry. "The patient has pneumonia, that explains the fever and cough."

Expert approach: After finding initial explanation, explicitly asks: "What else could be present? Does this explain ALL findings? Could there be a coexisting condition?"

Timeline: Develops over years of clinical experience through cases where initial findings were incomplete or coincidental. Critical moment comes when missing a second diagnosis causes patient harm—realization that "not finding everything is suboptimal."

Anchoring Error

Novice approach: Initial symptoms or emergency department triage note establishes diagnosis that persists despite contradictory information. "ED said anxiety attack, so I'm treating anxiety."

Expert approach: Periodically resets evaluation without reference to initial impressions. "If I saw this patient fresh right now, what would I think?" Actively seeks information contradicting initial hypothesis.

Timeline: Requires recognizing pattern across multiple cases where initial impression proved misleading. Breakthrough occurs when physician catches themselves defending an anchor despite mounting contrary evidence.

Commission Bias

Novice approach: Feels compelled to take action because "doing something" feels better than watchful waiting, even without clear indication. Treats borderline abnormal labs, adjusts medications unnecessarily.

Expert approach: Explicitly evaluates whether action is justified by evidence or driven by psychological need to intervene. Comfortable with watchful waiting when appropriate. Asks: "Will treatment help more than harm?"

Timeline: Often develops after causing harm through unnecessary intervention. Turning point is recognizing that action carries its own risks and that inaction is sometimes the most appropriate decision.

Availability Error

Novice approach: "I just saw three patients with Lyme disease, so this patient's fatigue must be Lyme too." Pattern-matches based on superficial similarities without considering differences.

Expert approach: When noticing similarity to recent case, explicitly lists differences: "How is this patient NOT like that case?" Questions whether similarities are clinically meaningful or coincidental.

Timeline: Accumulates through experience with similar-seeming cases that proved different. Key insight comes when a "just like the last patient" case turns out completely different upon deeper investigation.

Attribution Error

Novice approach: Accepts colleague's characterization that patient is "drug-seeking" or "anxious" and dismisses symptoms without independent evaluation. Stereotypes based on demographics.

Expert approach: Approaches each patient as individual regardless of others' characterizations. "What does THIS patient's presentation tell me?" Separates objective findings from attributed motivations.

Timeline: Often requires personal experience of misjudging a patient or discovering that a dismissed patient had serious pathology. Recognition that stereotypes prevented seeing actual clinical presentation.

Algorithm Rigidity

Novice approach: Either follows algorithms without contextual consideration ("The guideline says X, so I must do X") OR abandons them based on gut feeling without justification.

Expert approach: Recognizes algorithms as population-based tools requiring interpretation. Can articulate why specific patient context justifies deviation when it does. Documents reasoning.

Timeline: Develops through repeated experience applying guidelines to diverse patients. Critical learning occurs when rigid application causes harm OR when appropriate deviation leads to better outcome—recognizing that expertise lies in knowing which mode applies when.

Mental Models & Shibboleths

Core Shibboleths

  • "Not finding everything is suboptimal" — Expert recognition that diagnostic search shouldn't stop at first finding
  • "Understanding why we get things wrong is essential to understanding how to get things right" — Expert frame that errors reveal cognitive patterns, not just knowledge gaps
  • Semantic equivalence awareness — Expert automatically recognizes that "30% chance of improvement" and "70% chance of failure" are clinically identical but psychologically different

Expert vs Novice Markers

Novice says: "The patient has [single diagnosis]" Expert says: "The primary issue is [diagnosis], but I'm also considering [alternatives] and haven't ruled out [other possibilities]"

Novice says: "We need to do something" Expert says: "The question is whether intervention offers more benefit than harm compared to watchful waiting"

Novice says: "The protocol says..." Expert says: "The protocol applies when [conditions], but this patient differs in [specific ways]"

Navigation Metaphor

Clinical reasoning requires navigating between two extremes:

  • Rigid shore: Algorithmic medicine without contextual adaptation
  • Chaos shore: Intuition-based medicine without evidence grounding
  • Expert navigation: Knowing when to sail closer to structure (standard presentations) versus when context requires deviation (atypical patients)

Trap Metaphor

Cognitive biases are predictable traps on the diagnostic path:

  • Recognizable once you know what to look for
  • Avoidable with deliberate countermeasures
  • Universal (even experts fall in, but recognize and escape faster)
  • The map of traps can be taught and learned

References

  • Source: "How Doctors Think" by Jerome Groopman
  • Domain: Clinical decision-making, diagnostic reasoning, medical cognitive science
  • Key insight: Medical errors stem primarily from systematic thinking patterns (cognitive biases) rather than knowledge deficits, and these patterns can be identified, taught, and corrected

平台分布

Codex

33.68%
按下载量换算191

Claude

33.25%
按下载量换算188

Cursor

17.86%
按下载量换算101

Gemini CLI

10.28%
按下载量换算58

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

只读

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

安装前确认

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

继续浏览同类 Skills