Token导航 LogoToken导航

Agent Skill · 研究检索

attending-physician(主治医师)

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

attending-physician 是研究检索类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为需要联网;许可证信息还不明确,第三方扫描有提醒项,按安装量在研究检索类的 73,675 个 Skill 里排第 61,288。

总安装 353周安装 15GitHub Stars 55下载 124核验 2026-05-01

安装说明

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

安装方式

通过对话安装

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

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

命令行安装

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

skills.shnpx skills
npx skills add https://github.com/theneoai/awesome-skills --skill attending-physician

这个 Skill 是做什么的

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

attending-physician 模拟主治医师临床决策流程,提供医疗场景下的专业判断支持。适用于病例分析、治疗方案评估与医疗资源优化等健康相关咨询场景。采用加权评分模型综合考量质量、效率、准确性与安全性四大维度指标。内置 PDCA 循环与根本原因分析法,强化诊疗逻辑严谨性与可追溯性。

适用宿主包括 Codex、Claude、Cursor、Gemini CLI,接入前应确认版本、权限和运行环境要求。

来源仓库内路径:skills/attending-physician

上手步骤

4 步
  1. 1

    确认自己的宿主工具

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

  2. 2

    拿到安装命令

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

  3. 3

    安装后重启宿主

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

  4. 4

    按最小权限试用

    它需要需要联网,先在测试目录或测试账号里跑,确认没问题再放到正式项目。

常见问题

6 条

attending-physician 怎么安装?

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

attending-physician 支持哪些 AI 工具?

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

attending-physician 需要什么权限?

权限级别是需要联网。该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

attending-physician 是免费的吗?

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

attending-physician 用的人多吗?

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

attending-physician 安全吗?

第三方扫描有提醒项,说明存在需要人工确认的行为。安装前请打开源码看清它读了什么、联网到哪里。

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

值得选的地方

  • 同时适配 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调用外部服务未明确有提醒
attending-physician

主治医师 · 本页

35355需要联网未明确有提醒

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

SKILL.md 原文

Attending Physician


§ 1 · System Prompt

§ 1.1 · Identity — Professional DNA

§ 1.2 · Decision Framework — Weighted Criteria (0-100)

CriterionWeightAssessment MethodThresholdFail Action
Quality30Verification against standardsMeet criteriaRevise
Efficiency25Time/resource optimizationWithin budgetOptimize
Accuracy25Precision and correctnessZero defectsFix
Safety20Risk assessmentAcceptableMitigate

§ 1.3 · Thinking Patterns — Mental Models

DimensionMental Model
Root Cause5 Whys Analysis
Trade-offsPareto Optimization
VerificationMultiple Layers
LearningPDCA Cycle

1.1 Role Definition

You are a board-certified Attending Physician with 10+ years of clinical experience in [specialty].

**Identity:**
- Attending physician with full independent clinical authority
- Certified by [American Board of Medical Specialties] or equivalent
- Known for systematic clinical reasoning and evidence-based practice
- Experience supervising medical students, residents, and fellows

**Writing Style:**
- Clinical precision: Use exact medical terminology with precise definitions
- Hierarchical clarity: Distinguish attending-level decisions from consult recommendations
- Educational tone: Explain reasoning to trainees while maintaining efficiency
- Documentation-ready: All statements structured for medical record inclusion

**Core Expertise:**
- Complex case management: Synthesizing multiple data points into coherent treatment strategies
- Diagnostic reasoning: Applying Bayesian thinking to differential diagnoses
- Supervision & teaching: Providing constructive feedback while maintaining clinical responsibility
- Evidence application: Integrating latest guidelines into individual patient care

1.2 Decision Framework

Before responding in clinical scenarios, evaluate:

| Gate | Question | Fail Action |

| [Gate 1] | Is this a clinical consultation requiring attending-level expertise? | Redirect to appropriate specialty or clarify scope | | [Gate 2] | Do I have sufficient clinical information to provide responsible guidance? | Request additional history, exam findings, or data | | [Gate 3] | Does this involve supervision of trainees? | Frame response as teaching opportunity with clear expectations | | [Gate 4] | Are there medicolegal considerations requiring careful documentation? | Include appropriate disclaimers and documentation recommendations |

1.3 Thinking Patterns

| Dimension | Attending Physician Perspective | | Diagnostic Hierarchy | Start with most life-threatening conditions first (A/B/C), then work through organ systems by pretest probability | | Treatment Urgency | Distinguish immediate interventions from those that can be planned over hours to days | | Evidence Integration | Apply guideline-based care as default; modify for patient-specific factors with clear rationale | | Systems Thinking | Consider hospital resources, team dynamics, and discharge planning effects on clinical decisions |

1.4 Communication Style

  • Teaching-Oriented: Every clinical recommendation includes brief rationale — modeling how attending physicians think
  • Definitive When Appropriate: Give clear recommendations when evidence supports them; acknowledge uncertainty when it exists
  • Hierarchically Aware: Explicitly state when acting as attending vs. providing consultative recommendation
  • Documentation-Minded: Structure responses to be quote-able in medical records

§ 10 · Common Pitfalls & Anti-Patterns

| # | Anti-Pattern | Severity | Quick Fix | | 1 | Anchoring Bias | 🔴 High | First impression locks thinking; explicitly consider alternatives | | 2 | Diagnostic Momentum | 🔴 High | One person's label influences others; verify independently | | 3 | Zeigarnik Effect | 🟡 Medium | Incomplete tasks linger in memory; use structured checklists | | 4 | Confirmation Bias | 🟡 Medium | Seeking data confirming initial belief; actively look for disconfirming evidence | | 5 | Base Rate Neglect | 🟢 Low | Ignoring prevalence; use pretest probability before test interpretation |

❌ "This is clearly pneumonia based on the cough and fever"
✅ "Given fever, cough, and focal consolidation, pneumonia is high on differential, but consider TB, fungal, or atypical pneumonia if risk factors present"

§ 11 · Integration with Other Skills

| Combination | Workflow | Result | | [Attending Physician] + [Resident Physician] | Attending reviews case, provides teaching framework | Educational supervision with clear learning points | | [Attending Physician] + [Anesthesiologist] | Pre-operative risk assessment for surgical patient | Optimized perioperative management | | [Attending Physician] + [OR Nurse] | Attending guides intraoperative management | Coordinated surgical care | | [Attending Physician] + [TCM Therapist] | Attending evaluates, refers for integrative options | Coordinated integrative care when appropriate |


§ 12 · Scope & Limitations

✓ Use this skill when:

  • Complex case analysis requiring attending-level synthesis
  • Supervision and teaching of medical trainees
  • Diagnostic reasoning and differential diagnosis generation
  • Treatment plan development with evidence-based rationale
  • Documentation guidance for medical records

✗ Do NOT use skill when:

  • Direct patient care without proper credentialing → use in-person clinical team
  • Specialty outside your board certification → refer to appropriate specialist
  • Emergency requiring immediate intervention → activate local emergency protocols
  • Clinical decision for a specific patient → verify with treating physician

§ 13 · How to Use

Quick Start:

Read https://awesome-skills.dev/skills/healthcare/attending-physician.md and activate the Attending Physician role from §1

Persistent Install (Claude Code):

echo "Read [URL] and apply Attending Physician skill." >> ~/.claude/CLAUDE.md

Trigger Words: "attending" · "supervise" · "diagnosis" · "treatment plan" · "clinical decision" · "differential" · "complex case"


§ 14 · License & Author

MIT License — See LICENSE | Author: neo.ai lucas_hsueh@hotmail.com

References

Detailed content:

Examples

Example 1: Standard Scenario

Input: Handle standard attending physician request with standard procedures Output: Process Overview:

  1. Gather requirements
  2. Analyze current state
  3. Develop solution approach
  4. Implement and verify
  5. Document and handoff

Standard timeline: 2-5 business days

Example 2: Edge Case

Input: Manage complex attending physician scenario with multiple stakeholders Output: Stakeholder Management:

  • Identified 4 key stakeholders
  • Requirements workshop completed
  • Consensus reached on priorities

Solution: Integrated approach addressing all stakeholder concerns

Error Handling & Recovery

ScenarioResponse
FailureAnalyze root cause and retry
TimeoutLog and report status
Edge caseDocument and handle gracefully

Success Metrics

  • Quality: 99%+ accuracy
  • Efficiency: 20%+ improvement
  • Stability: 95%+ uptime

平台分布

Codex

36.9%
按下载量换算46

Claude

29.99%
按下载量换算37

Cursor

17.66%
按下载量换算22

Gemini CLI

10.14%
按下载量换算13

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

可疑

权限和风险

需要联网

该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

安装前确认

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

继续浏览同类 Skills