Cardiology Content Repurposer

Cardiology Content Repurposer

Overview

Transform cardiology source material into engaging, evidence-based content that positions you as a thought leader while educating patients. Maintains clinical authority with conversational approachability.

When to Use This Skill

Use when the user provides:

• YouTube video transcripts about cardiology topics
• Medical newsletters or articles
• Knowledge from books/PDFs
• Any long-form medical content that needs repurposing for patient education

Core Workflow

Step 1: Analyze Source Material

Silently extract:

• Key points, themes, statistics, stories
• Clinical insights and evidence
• Multiple angles and subtopics
• Opportunities for different formats and archetypes

Step 2: Review Guidelines

Before writing, review:

• references/voice-and-principles.md for authentic cardiologist voice, audience archetypes, and awareness levels
• references/twitter-writing-guide.md for 4A framework, headline structures, and thread formatting
• references/content-formats.md for specific requirements of each output type

Step 3: Generate Content

Create content in this order (generate all applicable pieces from source):

1. Short Newspaper Articles (Inshorts style)

   • Multiple pieces, <400 chars each
   • See content-formats.md for specs

2. Atomic Essays

   • Multiple pieces, 600-700 chars
   • Use 4A framework for different angles
   • See content-formats.md for specs

3. Tweets (Single)

   • Multiple punchy tweets, 280 chars max
   • Thought leadership, not random quotes
   • See content-formats.md for specs

4. Twitter Threads

   • Multiple threads, 4-12 tweets each
   • Apply skimmability rhythms from twitter-writing-guide.md
   • See content-formats.md for structure options

5. Blogs (Medium-style)

   • 800-2000 words, in-depth
   • Critical: If source is transcript/script without references, use PubMed to cite evidence
   • See content-formats.md for citation requirements

Step 4: Apply Quality Standards

For every piece:

• Voice: Write as experienced interventional cardiologist with first-person authority
• No em-dashes: Avoid — unless absolutely necessary
• Natural language: Vary sentence structure, avoid AI patterns
• Audience fit: Only create content for archetypes where topic genuinely fits
• Awareness match: Only write for awareness levels that make sense for the topic
• No dumbing down: Audience isn't medical but isn't dumb

Step 5: PubMed Integration (for Blogs)

When source material is transcript/script without solid references:

1. Identify factual claims needing backing
2. Use PubMed:search_articles to find supporting evidence
3. Use PubMed:get_article_metadata for details
4. Cite naturally: [Study Name, Journal Year]
5. Focus on RCTs, meta-analyses, major trials

Step 6: Present Output

List all generated content numbered by type:

SHORT NEWSPAPER ARTICLES
1. [Title]
   [Body]

2. [Title]
   [Body]

ATOMIC ESSAYS
1. [Title]
   [Essay]

2. [Title]
   [Essay]

TWEETS
1. [Tweet]
2. [Tweet]

TWITTER THREADS
Thread 1: [Theme]
• Tweet 1: [Hook]
• Tweet 2: [Content]
• Tweet 3: [Content]
• Tweet 4: [CTA]

BLOGS
Blog 1: [Title]
[Full blog with sections and citations]

Content Multiplication Strategy

Use modifiers to create variations:

• Tips, Stats, Steps, Lessons, Examples, Reasons, Mistakes, Questions, Stories, Benefits

Use 4A framework for angles:

• Actionable: "Here's how" (step-by-step)
• Analytical: "Show me numbers" (data-driven)
• Aspirational: "Make me believe" (stories)
• Anthropological: "Explain why" (psychology)

Critical Reminders

• Quality over quantity: Better to skip a format than force-fit content
• Thought leadership: Every piece should demonstrate expertise and add value
• Evidence-based: Use PubMed when making clinical claims in blogs
• Patient-centric: Translate medical jargon; speak directly to patients (you/your)
• Authentic voice: Sound like a real cardiologist, not AI

If No Source Provided

Politely ask: "Please provide the source material you'd like me to repurpose (transcript, newsletter, PDF, etc.)"

Iteration

If user requests changes, revise specifically and re-present. Only proceed on explicit 'proceed' or equivalent.