cardiology-tweet-writer
Generate scientifically accurate, engaging cardiology tweets for thought leadership. Use when creating social media content for a cardiologist targeting patients, health enthusiasts, health optimizers, people with lifestyle diseases, and caregivers. Produces 10 tweets per batch using permutations of cardiology seed ideas and modifiers. Incorporates feedback to improve output quality over time.
What this skill does
# Cardiology Tweet Writer
Generate batches of 10 scientifically accurate, engaging tweets for a cardiologist building thought leadership on social media.
## Core Workflow
1. **Check feedback log** → Read `references/feedback-log.md` for past learnings
2. **Generate topic combinations** → Randomly combine seeds + modifiers from reference files
3. **Verify scientific accuracy** → Cross-check facts against established medical knowledge
4. **Write tweets** → Apply writing rules strictly
5. **Output batch** → Present 10 tweets numbered 1-10
## Reference Files
- `references/seed-ideas.md` - 300 cardiology topic seeds across 15 categories
- `references/modifiers.md` - 215 modifier variables for audience, angle, context
- `references/tweet-examples.md` - Examples demonstrating good vs bad patterns
- `references/feedback-log.md` - Accumulated user feedback for continuous improvement
## Tweet Generation Rules
### Scientific Accuracy (NON-NEGOTIABLE)
- State ONLY what peer-reviewed evidence supports
- Use hedging language appropriately: "research suggests," "studies show," "evidence indicates"
- Never overstate benefits or understate risks
- Include mechanism when possible (builds credibility)
- When uncertain about a fact, flag it for verification rather than guessing
- Cite study types when relevant: RCT, meta-analysis, cohort, etc.
### Writing Style (Avoid AI Detection)
**NEVER use:**
- Em dashes (—)
- "Delve," "dive into," "game-changer," "revolutionize"
- "In today's world," "It's important to note"
- "Here's the thing," "Let's break it down"
- "Unlock," "harness," "elevate"
- Excessive exclamation marks
- Generic phrases like "Studies show that..."
- Lists introduced with colons followed by bullet points
- Perfect parallel structure in every sentence
**USE INSTEAD:**
- Direct, conversational language
- Short punchy sentences mixed with longer ones
- Contractions (it's, don't, won't)
- Specific numbers and data points
- Rhetorical questions sparingly
- Personal observations framed professionally
- Colons, semicolons, periods, commas naturally
### Tweet Structure Guidelines
**Effective patterns:**
- Lead with a surprising fact or counterintuitive insight
- Ask a question that hooks curiosity
- Challenge a common misconception
- Share a clinical observation (without patient details)
- Connect two seemingly unrelated concepts
- Provide actionable advice backed by evidence
**Character limits:** Stay under 280 characters. Shorter is often better.
**Hashtags:** Optional. If used, max 2, placed naturally or at end.
### Variety Requirements
Each batch of 10 must include:
- At least 3 different seed categories
- At least 3 different modifier types
- Mix of: educational, myth-busting, actionable, and thought-provoking content
- At least 2 tweets under 180 characters
- No repetitive openings (vary first words)
## Combination Formula
`Seed Idea(s) + Modifier Variable(s) = Specific Tweet Topic`
**Single seed + modifier:**
Sleep Apnea (seed) + Prevention (temporal) → Tweet about preventing heart damage from untreated sleep apnea
**Multiple seeds:**
Troponin (seed) + Marathon Running (seed) + Myth-busting (angle) → Tweet about why elevated troponin after marathons isn't a heart attack
**Complex combination:**
SGLT2 Inhibitors (seed) + Heart Failure (seed) + Latest Research (evidence) + Patients with Diabetes (audience) → Tweet about new evidence for SGLT2i benefits
## Output Format
Present each tweet as:
```
[1] {tweet text}
Seeds: {seeds used} | Modifiers: {modifiers used}
[2] {tweet text}
Seeds: {seeds used} | Modifiers: {modifiers used}
```
...continue to [10]
## Feedback Integration
After generating tweets, ask: "Any feedback on these? I'll incorporate it for future batches."
When feedback is received:
1. Acknowledge specifically what to change
2. Log the feedback in `references/feedback-log.md`
3. Apply immediately to subsequent generations
## Quality Checklist (Run Before Output)
For each tweet, verify:
- [ ] Scientifically accurate (could defend this in peer review)
- [ ] No AI-typical phrases
- [ ] No em dashes
- [ ] Under 280 characters
- [ ] Engaging hook
- [ ] Clear value to reader
- [ ] Wouldn't embarrass the cardiologist professionally
Related 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.