Token导航 LogoToken导航TokenDH.com
研究检索只读github未标认证来源可访问clear审计提醒

cardiology-topol-writer心脏病学托波尔作家

Agent Skill

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

总安装

447

周安装

19

GitHub Stars

3

下载量

157
CodexClaudeCursorGemini CLI

安装说明

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

GitHub

来源数

3

许可证

MIT

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

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

请帮我安装这个 Agent Skill:cardiology-topol-writer(心脏病学托波尔作家)
来源仓库:https://github.com/drshailesh88/integrated_content_os
仓库路径:skills/cardiology-topol-writer
安装命令:
npx skills add https://github.com/drshailesh88/integrated_content_os --skill cardiology-topol-writer
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。不同来源提供的安装方式可能略有差异;本站展示可直接复制的安装命令,安装前请核对来源页面。

skills.shnpx skills
npx skills add https://github.com/drshailesh88/integrated_content_os --skill cardiology-topol-writer

简介

将零散的思想素材转化为风格贴近 Eric Topol 写作风格的精炼心脏病学内容。

  • 适用于处理临床观察、病例经验、研究论文或治疗争议等各类非结构化输入。
  • 输出兼具证据基础、易读性和权威性的专业内容,适合用于患者教育或专业传播。
  • 使用时需保留原始信息真实性,避免将推测当作事实陈述;对外文案应避免过度承诺效果。
  • cardiology-topol-writer 属于研究检索类 Skill,可作为该场景下的辅助能力补充。

SKILL.md

Cardiology Content Writer (Topol Voice)

Transform unstructured thought dumps into polished cardiology content that sounds like Eric Topol writing Ground Truths—evidence-based, accessible, and authoritative.

Process

1. Receive the Thought Dump

Accept whatever the user provides:

  • Clinical observations or case experiences
  • Research papers or trials to discuss
  • Treatment approaches or controversies
  • Patient education topics
  • Procedural insights (PCI, structural, imaging)
  • AI/digital cardiology developments
  • Prevention and longevity angles
  • Random thoughts from cath lab, clinic, or reading

Don't require organization. Raw clinical thinking is the input.

2. Read Voice and Tone

Load references/voice-tone.md to understand Eric Topol's writing style.

Key characteristics:

  • Evidence-first, data-driven narrative
  • Accessible without dumbing down
  • Balanced optimism with honest limitations
  • Visual data integration (figures, graphs)
  • Direct acknowledgment of uncertainty
  • Conversational authority

3. Apply Content Framework

Read references/content-framework.md to understand structure options.

Determine the best format:

  • Research Commentary: Breaking down a trial or study
  • Clinical Deep Dive: Mechanism → Evidence → Practice
  • Technology/AI Analysis: Innovation assessment
  • Patient Education: Making complex accessible
  • Controversy Analysis: Balanced evidence review
  • Video Script: Spoken-word adaptation

4. Organize Content

Structure the material using Topol's typical patterns:

For Research Commentary:

  • Hook with significance/context
  • Study design summary (1-2 sentences)
  • Key results with specific numbers
  • Visual data presentation
  • Limitations acknowledgment
  • Clinical implications
  • Forward-looking perspective

For Clinical Deep Dives:

  • Current state of knowledge
  • What the data actually shows
  • What we still don't know
  • Practical application
  • Call for better evidence if needed

For Video Scripts:

  • Strong opening hook (provocative statement or question)
  • "Here's what the data shows..."
  • Visual/demonstration moments flagged
  • Conversational transitions
  • Clear takeaways

5. Write in Topol's Voice

Apply voice characteristics:

Opening:

  • Lead with the most important finding or insight
  • Set up the significance immediately
  • Be direct—no throat clearing

Body:

  • Cite specific studies with numbers
  • Use "N=" notation naturally
  • Include confidence intervals and p-values when meaningful
  • Reference figures and graphs
  • Acknowledge limitations honestly
  • Challenge dogma when evidence supports it

Technical precision:

  • Use medical terminology accurately
  • Define jargon when writing for public
  • Include specific drug names, doses, endpoints
  • Reference trials by name (PARTNER, EVOLUT, ISCHEMIA)

Tone modulation:

  • Authoritative but never arrogant
  • Optimistic but grounded
  • Critical but fair
  • Accessible but not condescending

Ending:

  • Context: Where does this fit in the bigger picture?
  • Implications: What should clinicians/patients know?
  • Forward look: What's needed next?
  • Optional: Appropriate levity

6. Enhance with Topol Elements

Consider adding:

  • "Ground truth" framing—what do we actually know?
  • Reference to evolving science: "What's true today may change"
  • Acknowledgment of your perspective/bias if relevant
  • Call for more/better trials if appropriate
  • Humor or levity when it fits (not forced)
  • Links to primary sources

7. Review and Refine

Check the content:

  • Does it lead with evidence?
  • Are claims supported by specific data?
  • Is the tone authoritative but accessible?
  • Are limitations honestly addressed?
  • Is the clinical relevance clear?
  • Would both cardiologists and educated patients understand it?
  • Does it sound like Topol, not a corporate CME module?

Voice Guidelines

Do:

  • Lead with data and evidence
  • Cite specific trials, N, and key statistics
  • Challenge established thinking when warranted
  • Acknowledge what we don't know
  • Write for both peers and public
  • Be direct and clear
  • Use visuals and figures
  • Include your clinical perspective
  • Maintain optimism grounded in evidence
  • Reference primary sources

Don't:

  • Write pharma-speak or bland CME language
  • Hide behind hedge words when evidence is clear
  • Pretend certainty where none exists
  • Condescend to readers
  • Ignore limitations or contrary evidence
  • Use buzzwords without substance
  • Write like a textbook
  • Lose the human element

Format-Specific Notes

For Newsletter/Blog Posts:

  • 800-1500 words typical
  • 2-4 embedded figures/graphs
  • Clear section breaks
  • Links to all referenced studies
  • End with forward perspective

For Video Scripts:

  • Conversational tone throughout
  • Flag visual moments: [SHOW FIGURE], [DEMONSTRATE]
  • Include pauses for emphasis
  • Natural transitions ("Now here's where it gets interesting...")
  • Strong opening hook in first 10 seconds
  • Clear call to action or takeaway at end

For Twitter/Social Threads:

  • Lead tweet is the hook
  • One key point per tweet
  • Include one compelling figure
  • End with perspective/implication

Example Patterns

Opening hooks (Topol style):

Our gold standard of assessing efficacy in medicine is a large-scale randomized trial. Today, we finally got one that matters.
For years, we've been told that [conventional wisdom]. The data tell a different story.
In a paper published today in [Journal], [N] patients were randomly assigned to... The results are striking.

Evidence presentation:

For the overall trial there was a statistically significant 17% reduction of all-cause mortality. The high-risk group saw a 31% reduction—7 per 100 lives saved. That's remarkable and as good or better than our most effective medical treatments.

Honest limitations:

The main limitation of the trial was inability to determine the precise mechanism of benefit. We know it worked—we don't yet know exactly why.

Forward perspective:

Progress in [field] won't occur in a straight line. One big step forward, sometimes steps back. Without compelling evidence, there can't be meaningful implementation. We need a lot more trials like this one.

Bundled Resources

References

  • references/voice-tone.md - Complete Eric Topol voice and tone guide. Read this first to capture the Ground Truths style.
  • references/content-framework.md - Structure frameworks for different content types (research commentary, clinical deep dives, video scripts, patient education).

Workflow Example

User provides thought dump:

just did a complex CTO case - thinking about how AI could change this
- spent 4 hours, successful but hard
- imaging fusion really helped
- AI could probably predict which cases will be hard
- also thinking about whether we overdo CTOs
- ISCHEMIA trial implications
- patient outcomes vs procedure success
- need to write something about this

Process:

  1. Read voice-tone.md for Topol style
  2. Check content-framework.md - this is a clinical deep dive + AI angle
  3. Identify structure: Current state of CTO → Evidence (ISCHEMIA context) → AI opportunity → Practical implications
  4. Write opening hook about the tension between procedural success and outcomes
  5. Include ISCHEMIA trial data with specific numbers
  6. Discuss AI/imaging potential with honest limitations
  7. End with "what we need" perspective
  8. Review for Topol voice: evidence-based, accessible, honest about uncertainties

适合场景

01

用户想查找某类 Agent Skill 时

02

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

03

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

04

需要参考平台分布和安装热度时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

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

能力 4

补充不同宿主或平台的使用分布数据

能力 5

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

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

平台分布

Claude Code

32.25%
按下载量换算51

OpenCode

23.08%
按下载量换算36

Antigravity

18.2%
按下载量换算29

Gemini CLI

13.56%
按下载量换算21

windsurf

8.47%
按下载量换算13

Codex

3.37%
按下载量换算5

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

可疑

权限和风险

只读

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

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。来源安全扫描存在 warning/failed 结果,不能写成本站确认安全。

来源信息

继续浏览同类 Skills