cardiology-trial-editorial
Identify landmark cardiology trials and write evidence-based editorials in Eric Topol's authoritative Ground Truths style. Use when the user wants to: (1) Discover and evaluate recent important trials from top cardiology journals (NEJM, JACC, Lancet, EHJ, Circulation), (2) Assess trial importance using systematic scoring, (3) Write 500-word editorials on cardiology/interventional cardiology advances for physician audiences, (4) Create thought leadership content that demonstrates deep domain expertise. Supports both full-text and abstract-only scenarios with PubMed integration for references.
What this skill does
# Cardiology Trial Editorial Writer
Build thought leadership through evidence-based editorials on landmark cardiology trials, written in Eric Topol's authoritative Ground Truths style.
## Core Workflow
### Phase 1: Trial Discovery & Selection
1. **Search target journals** using PubMed:search_articles for recent publications (past 30-90 days):
- NEJM, JAMA, Lancet (tier 1 general)
- JACC, JACC: Cardiovascular Interventions, European Heart Journal (tier 1 cardiology)
- Circulation: Cardiovascular Interventions, EuroIntervention, JSCAI, CCI (interventional focus)
2. **Score each trial** using the importance scoring system (see `references/trial-scoring.md`):
- Extract metadata: design, sample size, endpoints, topic, novelty
- Calculate base score from design + sample + endpoints + topic + novelty
- Add venue bonus for top journals
- Optionally assess practice-change likelihood
- Sort by total importance_score
3. **Present top candidates** (top 3-5) to user with:
- Title, journal, publication date
- Importance score breakdown
- One-sentence summary of why it matters
- Ask user to select or request alternatives
### Phase 2: Editorial Preparation
Once user approves a trial:
1. **Determine content availability**:
- Ask: "Do you have the full PDF, or should I work from the abstract?"
- If full text available via PubMed Central (PMCID), retrieve with PubMed:get_full_text_article
- If only abstract: work from PubMed:get_article_metadata
2. **Gather contextual evidence**:
- Search PubMed for prior landmark trials in same domain
- Identify 2-4 key comparator trials for context
- Extract relevant findings to position current trial
3. **Analyze trial critically**:
- Study design, population, intervention, endpoints
- Internal validity: randomization, blinding, missing data
- External validity: generalizability, exclusions, setting
- Statistical robustness: confidence intervals, subgroups
### Phase 3: Editorial Writing
Follow the Eric Topol Ground Truths style (see `references/topol-style-guide.md`):
**Structure (500 words, ~1500-1700 characters):**
1. **Opening hook** (1-2 paragraphs):
- Start with clinical problem, not the trial
- Frame as bedside dilemma or unmet need
- Introduce trial as potential solution
2. **Trial summary** (1 tight paragraph):
- Population, intervention, comparator, design
- Primary outcome, headline effect size
- Keep numbers minimal and meaningful
3. **Evidence quality** (brief critical assessment):
- One paragraph on strengths ("why I trust this")
- One paragraph on limitations ("what makes me hesitate")
- Focus on validity and confidence, not trivia
4. **Context and comparison**:
- How this fits with prior trials
- Confirms trend, reverses evidence, or fills gap?
- Explain differences: population, endpoints, timing
5. **Clinical implications** (most important section):
- Who should change practice Monday?
- Who should wait for more data?
- Specific, actionable guidance
- Conditional but clear language
6. **Unanswered questions**:
- Important outcomes not measured
- Subgroups with unclear signals
- 1-2 concrete future research directions
7. **Closing** (one strong sentence):
- Memorable take-home message
- Balanced stance on practice change
**Topol Style Elements:**
- Authoritative but accessible voice
- Dense with scientific concepts, assume MD audience
- Evidence-grounded every claim with citations
- Balanced skepticism, never promotional
- Numbers: absolute risk differences, NNT/NNH
- Patient-centered: QOL, treatment burden, preferences
**Critical Rules:**
- ALWAYS cite using PubMed references with DOIs
- For claims about trials: cite specific PMID
- Never make unsupported assertions
- If working from abstract only, explicitly acknowledge limitations
- Use phrases like "if confirmed in full publication" when from abstract
- Maintain intellectual humility while projecting expertise
### Phase 4: Visual Infographic Creation
After writing the editorial, create an **engaging visual infographic slide** (see `references/infographic-design.md`):
**Purpose:** Increase platform dwell time by providing visual summary for those who don't read full text
**Format:** Single-page HTML slide with embedded graphics (1200x1600px optimal for mobile/desktop)
**Key Elements:**
1. **Header section** (compelling title + trial name)
2. **Visual data presentation** (key finding with icon/graphic)
3. **3-panel comparison** (who benefits, who waits, what's unknown)
4. **Clinical bottom line** (action item in highlighted box)
5. **Footer** (citation + user attribution)
**Design principles:**
- Medical professional aesthetic (clean, evidence-based, not flashy)
- Color palette: cardiology blues (#1E3A8A, #3B82F6, #60A5FA) with accent (#EF4444 for warnings)
- Typography: Clear hierarchy, readable at mobile size
- Icons: Simple, medical-appropriate (heart, stethoscope, chart symbols)
- Data visualization: Bar charts, simple comparisons, clear numbers
- White space: Professional, not cluttered
**Content structure:**
```
┌─────────────────────────────────────┐
│ TRIAL NAME: Bold Finding │ ← Header
├─────────────────────────────────────┤
│ [ICON] KEY RESULT │ ← Hero metric
│ XX% vs YY% (p=0.00X) │
│ NNT = Z │
├─────────────────────────────────────┤
│ ✓ CHANGE PRACTICE ⚠ WAIT ❓UNKNOWN│ ← 3-panel
│ [details] [details] [gaps]│
├─────────────────────────────────────┤
│ 🎯 BOTTOM LINE: [actionable] │ ← Takeaway
├─────────────────────────────────────┤
│ Source: [Journal] | Dr. [Name] │ ← Attribution
└─────────────────────────────────────┘
```
**Technical implementation:**
- Create standalone HTML file with inline CSS
- Use simple SVG icons or Unicode symbols (♥, ⚕, 📊)
- Responsive design (flexbox/grid)
- No external dependencies
- Ready to screenshot or embed
**Always deliver:**
1. Editorial text (500 words)
2. HTML infographic file
3. Brief note: "Screenshot this slide for social media posting"
### Phase 5: Quality Assurance
Before delivering:
1. Verify all citations link to actual PubMed articles
2. Check word count (target 500 ± 50 words)
3. Ensure character count fits 1500-1700 range
4. Confirm Eric Topol voice consistency
5. Validate that user appears as authoritative cardiologist
6. Test infographic renders properly in browser
7. Ensure infographic visual hierarchy is clear
## Abstract-Only Workflow
When only abstract available (common for conference presentations or embargoed trials):
1. **Set ethical boundaries upfront**:
- Frame as "commentary on emerging result, not practice verdict"
- Never recommend standard-of-care change from abstract alone
- Use "promising but provisional" tone throughout
2. **Mine abstract systematically**:
- Background: clinical problem (can write confidently)
- Methods: extract headlines only (population, intervention, design, endpoint)
- Results: direction of effect, key numbers presented
- Explicitly note missing pieces: inclusion/exclusion details, statistical plan, safety profile
3. **Structure shifts**:
- Include "honesty paragraph": "As with any report available only in abstract form, important details are not yet accessible..."
- List 3-5 specific unknowns that matter most
- Talk implications as questions, not prescriptions
- Close with "wait but pay attention" message
4. **Language safety**:
- "Based on limited information currently available"
- "If these findings are confirmed in full report"
- "Abstract suggests, but does not yet establish"
- Avoid: "game changer", "paradigm shift", "definitive"
## Alternative Paths
**If user rejects machine's trial selection:**
- Show next-ranked trials (positions 6-10)
- Ask user for specific topic preferences
- Search by user-specified criteria
- Offer manual trial entry (user provides PMRelated in Writing & Docs
jax-development
IncludedUse this skill when the user is writing, debugging, profiling, refactoring, reviewing, benchmarking, parallelising, exporting, or explaining JAX code, or when they mention JAX, jax.numpy, jit, grad, value_and_grad, vmap, scan, lax, random keys, pytrees, jax.Array, sharding, Mesh, PartitionSpec, NamedSharding, pmap, shard_map, Pallas, XLA, StableHLO, checkify, profiler, or the JAX repo. It helps turn NumPy or PyTorch-style code into pure functional JAX, fix tracer/control-flow/shape/PRNG bugs, remove recompiles and host-device syncs, choose transforms and sharding strategies, inspect jaxpr/lowering/IR, and benchmark compiled code correctly.
nature-article-writer
IncludedDrafts, rewrites, diagnostically critiques, and style-calibrates primary research manuscripts for Nature and Nature Portfolio journals. Use when the user wants a Nature-style title, summary paragraph or abstract, introduction, results, discussion, methods, figure legends, presubmission enquiry, cover letter, reviewer response, or when a scientific draft sounds generic, jargon-heavy, structurally weak, or AI-ish and needs precise, broad-reader-friendly prose without inventing data, analyses, or references. Best for primary research articles and letters rather than reviews or press releases unless explicitly adapting one.
deckrd
IncludedDocument-driven framework that derives requirements, specifications, implementation plans, and executable tasks from goals through structured AI dialogue. Use when user says "write requirements", "create spec", "plan implementation", "derive tasks", "structure this feature", "break down into tasks", or "document this module". Also use for reverse engineering existing code into docs (/deckrd rev). Do NOT use for direct code writing — use /deckrd-coder after tasks are generated. Do NOT use when the user only wants to run or fix existing code without planning.
clinical-decision-support
IncludedGenerate professional clinical decision support (CDS) documents for pharmaceutical and clinical research settings, including patient cohort analyses (biomarker-stratified with outcomes) and treatment recommendation reports (evidence-based guidelines with decision algorithms). Supports GRADE evidence grading, statistical analysis (hazard ratios, survival curves, waterfall plots), biomarker integration, and regulatory compliance. Outputs publication-ready LaTeX/PDF format optimized for drug development, clinical research, and evidence synthesis.
handling-sf-data
IncludedSalesforce data operations with 130-point scoring. Use this skill to create, update, delete, bulk import/export, generate test data, and clean up org records using sf CLI and anonymous Apex. TRIGGER when: user creates test data, performs bulk import/export, uses sf data CLI commands, needs data factory patterns for Apex tests, or needs to seed/clean records in a Salesforce org. DO NOT TRIGGER when: SOQL query writing only (use querying-soql), Apex test execution (use running-apex-tests), or metadata deployment (use deploying-metadata).
accelint-ac-to-playwright
IncludedConvert and validate acceptance criteria for Playwright test automation. Use when user asks to (1) review/evaluate/check if AC are ready for automation, (2) assess if AC can be converted as-is, (3) validate AC quality for Playwright, (4) turn AC into tests, (5) generate tests from acceptance criteria, (6) convert .md bullets or .feature Gherkin files to Playwright specs, (7) create test automation from requirements. Handles both bullet-style markdown and Gherkin syntax with JSON test plan generation and validation.