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

medical-newsletter-writer医学通讯作家

Agent Skill

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

总安装

1,211

周安装

52

GitHub Stars

3

下载量

424
CodexClaudeCursorGemini CLI

安装说明

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

GitHub

来源数

3

许可证

MIT

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

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

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

命令行安装

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

skills.shnpx skills
npx skills add https://github.com/drshailesh88/integrated_content_os --skill medical-newsletter-writer

简介

medical-newsletter-writer 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中根据关键词或任务场景定位候选结果。

  • 适用于需要快速获取信息或线索的场景,如医学通讯撰写或内容策划。
  • 通过关键词、来源仓库或任务描述触发检索,返回结构化候选列表。
  • 安装前需确认权限范围,注意是否会触发联网或文件操作,建议检查维护状态。
  • 适用宿主包括 Codex、Claude、Cursor、Gemini CLI,接入前应确认版本、权限和运行环境要求。

SKILL.md

Medical Newsletter Writer

Create high-quality, evidence-based medical newsletters in the style of Eric Topol's Ground Truths. This skill guides the complete newsletter creation process: from analyzing your PDF of topic ideas, to deep PubMed research, to writing in Topol's distinctive authoritative-yet-accessible voice.

Quick Start

Simple 3-Step Process:

  1. Upload PDF - Upload your PDF with topic ideas in the chat
  2. Select Topic - Review engagement predictions and pick one topic
  3. Get Newsletter - Receive complete, publication-ready newsletter (~3,000 words with 20-30 PubMed citations)

The skill handles everything: PDF extraction, trend analysis, PubMed research, and writing in Eric Topol's exact voice.

Complete Workflow

The newsletter creation process has 5 phases:

  1. Extract Topics from PDF - Read user's uploaded PDF of topic ideas
  2. Trend Analysis - Analyze each topic for engagement potential
  3. Topic Selection - User approves topics based on data-driven predictions
  4. Deep Research - Comprehensive PubMed literature review
  5. Newsletter Writing - Write complete newsletter in Topol's style

Phase 1: Extract Topics from PDF

PDF Upload

User will upload a PDF containing potential newsletter topic ideas in the chat.

Extract Topics

  • Read the PDF using available tools
  • Extract all topic ideas mentioned
  • Clean and organize the list
  • If PDF contains notes/context about topics, capture that too

Phase 2: Trend Analysis & Engagement Prediction

Analyze Each Topic (Automatically)

For each topic extracted from the PDF, conduct comprehensive trend analysis:

1. News Coverage (Google News, medical news sites)

  • Search past 30 days
  • Note which outlets covering
  • Identify breaking developments
  • Count article frequency

2. Search Interest

  • Use web_search to assess current discussion
  • Look for rising interest signals
  • Note if topic is trending

3. Social Media Signals

  • YouTube: Search for videos, note view counts
  • Check if medical professionals are discussing
  • Assess virality potential

4. Academic Momentum (PubMed)

  • Count recent publications (6 months)
  • Check for major journal coverage
  • Identify ongoing trials
  • Note if field is active

Engagement Prediction Scoring

For each topic, score 1-10 on:

  1. Readability: Can this be explained clearly to physicians?
  2. Controversy: Is there debate/opposing views?
  3. Clinical Relevance: Will this affect patient care?
  4. Timeliness: How current is this? Breaking news?
  5. Share Potential: Will physicians share with colleagues?

Overall Engagement Score = Average of 5 metrics

Present Analysis

Create comparison table with:

  • Topic name
  • Brief trend summary (2-3 sentences)
  • Individual scores (1-10)
  • Overall engagement score
  • Priority recommendation (High/Medium/Low)

Sort by overall score, present top 5-10 topics to user.

Phase 3: Topic Selection

Present findings to user with:

  • Top topics by engagement prediction
  • Rationale for scores
  • Notable timeliness factors

User selects ONE topic - then the skill automatically proceeds to research and writing.

Phase 4: Deep Research (Automatic)

PubMed Search Strategy

Before searching, read workflow.md for detailed research guidance.

Initial searches:

  1. Broad topic overview
  2. Recent findings (<1 year)
  3. Systematic reviews/meta-analyses
  4. Major clinical trials

Paper Prioritization:

  • Tier 1: Large RCTs in NEJM, Lancet, JAMA, Science, Nature
  • Tier 2: Meta-analyses and systematic reviews
  • Tier 3: Large observational studies
  • Tier 4: Mechanistic studies in high-impact journals
  • Tier 5: Pre-clinical (use sparingly)

Target: 15-30 highly relevant papers

Extract Key Information

For each major paper:

  • Study design and sample size
  • Key findings (quantitative)
  • Limitations
  • How it fits the narrative
  • Potential quotes/figures

Find Related Work

  • Use PubMed related articles
  • Check major paper citations
  • Look for responses/commentary
  • Identify consensus vs. controversy

Phase 5: Newsletter Writing (Automatic)

Before Writing

CRITICAL: Read topol-style-guide.md first - This contains essential voice patterns, phrases, and stylistic requirements.

Structure

Opening (1-2 paragraphs)

  • Hook using Topol's opening patterns (see style guide)
  • Why this matters NOW
  • What will be covered

Background/Context (optional)

  • Define key terms: "To review: [term] is..."
  • Historical perspective if relevant
  • Current state of field

Main Content (3-5 sections with clear headers)

  • Each section = one major subtopic
  • Build logically
  • Include data/studies in each
  • Use tables to compare studies/treatments
  • Reference figures from papers

Implications/Future Directions

  • What this means for practice
  • Research gaps
  • What's next

Bottom Line (required)

  • Synthesize key takeaways
  • Clear conclusions based on evidence
  • Call for more evidence if needed

Standard Closing (required)

Thanks for reading and subscribing to Ground Truths.

If you found this interesting PLEASE share it!

That makes the work involved in putting these together especially worthwhile.

All content on Ground Truths—its newsletters, analyses, and podcasts, are free, open-access.

Paid subscriptions are voluntary and all proceeds from them go to support Scripps Research. They do allow for posting comments and questions, which I do my best to respond to. Please don't hesitate to post comments and give me feedback. Let me know topics that you would like to see covered.

Writing Requirements

Voice & Style:

  • First person engaged ("I recently fielded questions...")
  • Authoritative but accessible
  • Critical and evidence-based
  • Use Topol's signature phrases (see style guide)

Citations:

  • EVERY factual claim needs a PubMed citation with hyperlink
  • Format: link text embedded in prose
  • Cite original studies, not news articles
  • Include author names for major findings: "Professor X and colleagues at Y University published in Z..."

Critical Analysis:

  • Always discuss study limitations
  • Note conflicts of interest if relevant
  • Present alternative interpretations
  • Flag when evidence is preliminary
  • Call out hype vs. data

Length: 2,000-3,500 words

Visual Elements:

  • Create tables comparing studies/treatments
  • Describe figures from papers
  • Use clear section headers

Quality Checks

Before finalizing:

  • Engaging opening hook?
  • Clear why-this-matters framing?
  • Every claim cited?
  • Limitations discussed?
  • Topol's voice consistent?
  • Tables/figures included?
  • Logical flow?
  • "Bottom Line" section?
  • Standard closing?
  • 2,000-3,500 words?

Delivery

Final Format

  • Complete newsletter in Markdown
  • All hyperlinked citations to PubMed
  • 2,000-3,500 words
  • Ready for user's newsletter platform

Customization Note

User may want to change "Scripps Research" in the standard closing to their own institution/practice name.

Essential References

ALWAYS READ BEFORE WRITING:

  • topol-style-guide.md - Complete guide to Topol's voice, phrases, patterns
  • workflow.md - Detailed research and writing process

Key Success Factors

  1. Evidence-based: Every claim must be cited
  2. Critical thinking: Discuss limitations, not just positives
  3. Voice consistency: Sound like Topol throughout
  4. Comprehensive: Cover topic thoroughly with multiple studies
  5. Accessible: Technical accuracy without excessive jargon
  6. Timely: Focus on recent developments
  7. Visual: Include tables/figures to enhance understanding
  8. Engaging: Hook readers immediately, maintain interest

Example Opening Lines (Topol Style)

  • "In fielding questions recently from patients and colleagues about [topic], I was prompted to look into the field at more depth."
  • "[Term] was coined in the late [year]. Now, about [X] years later, we've yet to achieve [goal]."
  • "This week [major development] was published in [journal]. Several important reports have since been published. I've incorporated them in this updated version."
  • "There's no question that the use of [intervention] has surged, in part because of [claims], along with endorsements by [influencers]."

Common Pitfalls to Avoid

  • Don't rely on single studies - use multiple sources
  • Don't ignore study limitations - they're critical
  • Don't cherry-pick data - present full picture
  • Don't get too technical - stay accessible
  • Don't use bullet points excessively - prefer prose
  • Don't skip the critical analysis - it's essential
  • Don't forget visual elements - tables enhance understanding
  • Don't deviate from Topol's voice - consistency matters

适合场景

01

用户想查找某类 Agent Skill 时

02

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

03

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

04

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

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

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

能力 4

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

能力 5

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

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

平台分布

Claude Code

26.25%
按下载量换算111

Antigravity

21.79%
按下载量换算92

OpenCode

16.43%
按下载量换算70

Gemini CLI

13.58%
按下载量换算58

windsurf

7.73%
按下载量换算33

Codex

3.23%
按下载量换算14

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

可疑

权限和风险

只读

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

安装前确认

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

来源信息

继续浏览同类 Skills