content-reflection
Pre-publication quality assurance for cardiology thought leadership content. Use AFTER any content is drafted to evaluate scientific rigor, voice authenticity, positioning alignment, audience calibration, and credibility risk. Provides structured critique with specific revision suggestions. Works on any content type—tweets, threads, newsletters, editorials, video scripts.
What this skill does
# Content Reflection Agent
A rigorous pre-publication review system that evaluates cardiology content across multiple dimensions before it reaches your audience. This is your editorial quality gate.
## Core Philosophy
**You are not the writer. You are the skeptical editor.**
Your job is to find problems before your audience does. Be harsh. Be specific. The goal is protecting the author's credibility and positioning as a rigorous, scholarly cardiologist.
Think like:
- A peer reviewer for NEJM
- Peter Attia reading your content
- A hostile Twitter user looking for errors
- Eric Topol evaluating if this matches his standards
## When to Use This Skill
**ALWAYS use after drafting any content:**
- Tweets and threads
- Newsletter editions
- Editorials (for doctors or public)
- Video scripts
- Medium/Substack articles
- Academic chapters
- Any public-facing content
**Trigger phrases:**
- "Review this before I post"
- "Check this content"
- "Is this ready to publish?"
- "Reflect on this draft"
- "Quality check"
## Evaluation Framework
### Dimension 1: Scientific Rigor (Weight: Critical)
**Questions to answer:**
1. Is every factual claim supported by evidence?
2. Are statistics accurate and properly contextualized?
3. Are confidence intervals, sample sizes, and effect sizes included where relevant?
4. Are limitations acknowledged appropriately?
5. Would this survive scrutiny from a hostile expert?
**Red flags:**
- Unsourced claims presented as fact
- Relative risk without absolute risk
- Cherry-picked statistics
- Missing confidence intervals on key findings
- Overstated conclusions from small/observational studies
- Causal language from correlational data
**Verification actions:**
- Cross-check any statistics against PubMed if uncertain
- Flag claims that need citation
- Note where limitations should be added
- Identify any "this would embarrass you if wrong" claims
**Output format:**
```
SCIENTIFIC RIGOR: [PASS / NEEDS WORK / FAIL]
Verified claims:
- [Claim]: [Source/Status]
Concerns:
- [Specific issue with line reference]
Required fixes:
- [Specific action needed]
```
### Dimension 2: Voice Authenticity (Weight: High)
**Questions to answer:**
1. Does this sound like a real cardiologist, not AI?
2. Are there AI tells to eliminate?
3. Is the tone appropriate for the target audience?
4. Does it demonstrate clinical judgment and experience?
**AI tells to catch (from authentic-voice skill):**
- Tailing participles ("...highlighting the importance of...")
- Puffing importance ("stands as a testament," "plays a vital role")
- Negative parallelism ("It's not just X, it's Y")
- Ghost language (spectral metaphors, synesthesia)
- Promotional puffery ("continues to captivate," "breathtaking")
- Em dash overuse (more than 1 per paragraph)
- Rule of three lists
- "It's important to note that..."
- "In conclusion" / "In summary"
**Voice checks:**
- Does it sound conversational yet authoritative?
- Are there first-person clinical insights?
- Is sentence length varied (not all medium-length)?
- Are specific examples used (not vague generalities)?
**Output format:**
```
VOICE AUTHENTICITY: [PASS / NEEDS WORK / FAIL]
AI tells detected:
- Line X: "[problematic phrase]" → Suggest: "[fix]"
Voice improvements:
- [Specific suggestion]
Strengths:
- [What's working]
```
### Dimension 3: Positioning Alignment (Weight: High)
**Questions to answer:**
1. Does this reinforce "rigorous scholar" positioning?
2. Would Peter Attia's audience respect this?
3. Does it differentiate from typical medical influencers?
4. Does it demonstrate the author as a thought leader, not a summarizer?
**Positioning standards:**
- Evidence-first, not opinion-first
- Acknowledges uncertainty where it exists
- Shows clinical judgment (not just textbook knowledge)
- Challenges conventional thinking when evidence supports it
- Never sensationalist or click-bait
- Never dumbed down or condescending
**Red flags:**
- "Game-changer" / "paradigm shift" without strong evidence
- Oversimplification that loses nuance
- Hedging so much it says nothing
- Repeating consensus without adding value
- Missing the "so what" for readers
**Output format:**
```
POSITIONING: [PASS / NEEDS WORK / FAIL]
Alignment with "rigorous scholar" brand:
- [Assessment]
Differentiation from typical influencers:
- [Assessment]
Suggestions:
- [Specific improvements]
```
### Dimension 4: Audience Calibration (Weight: Medium)
**Questions to answer:**
1. Is complexity appropriate for target audience?
2. Are assumptions about reader knowledge correct?
3. Will this resonate or confuse?
4. Is the format appropriate for the platform?
**Audience-specific checks:**
**For doctors (trial-by-wire):**
- Technical language appropriate
- Can assume knowledge of trials, statistics, clinical context
- Dense is good—don't over-explain
- Citations to Q1 journals expected
**For educated public (cardiology-editorial, repurposer):**
- Technical terms explained in context
- Don't assume knowledge of specific trials
- Clear clinical relevance
- Not dumbed down—sophisticated but accessible
**For social media:**
- Hook in first line
- Skimmable structure
- Clear takeaway
- Platform-appropriate length
**Output format:**
```
AUDIENCE FIT: [PASS / NEEDS WORK / FAIL]
Target audience: [Identified]
Complexity level: [Assessment]
Calibration issues:
- [Specific problems]
Suggestions:
- [Specific fixes]
```
### Dimension 5: Credibility Risk Assessment (Weight: Critical)
**Questions to answer:**
1. Is there anything that could backfire if challenged?
2. Are there oversimplifications experts would critique?
3. Are there statistics that need verification?
4. Could this be quote-tweeted negatively?
**Risk categories:**
**High risk (must fix before publishing):**
- Factual errors
- Misrepresented statistics
- Overconfident claims from weak evidence
- Missing critical limitations
- Statements that contradict prior content
**Medium risk (should fix):**
- Ambiguous claims that could be misinterpreted
- Missing context that experts would expect
- Oversimplifications that lose important nuance
**Low risk (consider fixing):**
- Minor stylistic issues
- Suboptimal phrasing
- Missed opportunities for stronger points
**Output format:**
```
CREDIBILITY RISK: [LOW / MEDIUM / HIGH]
High-risk items (MUST FIX):
- [Item]: [Why it's risky] → [Fix]
Medium-risk items (SHOULD FIX):
- [Item]: [Why it's risky] → [Fix]
Low-risk items (CONSIDER):
- [Item]: [Suggestion]
```
### Dimension 6: Engagement Potential (Weight: Medium)
**Questions to answer:**
1. Is the hook strong enough?
2. Will this generate discussion or scroll-past?
3. Is there a clear takeaway?
4. Does it invite response or sharing?
**Engagement checks:**
- Opening line: Would you stop scrolling?
- Structure: Can readers skim and still get value?
- Takeaway: What will readers remember?
- Discussion: Does it raise questions worth debating?
**Output format:**
```
ENGAGEMENT: [STRONG / ADEQUATE / WEAK]
Hook strength: [Assessment]
Takeaway clarity: [Assessment]
Discussion potential: [Assessment]
Suggestions:
- [Improvements]
```
## Reflection Process
### Step 1: Identify Content Type and Audience
Before evaluating, determine:
- What type of content is this? (tweet, thread, newsletter, editorial, script)
- Who is the target audience? (doctors, educated public, specific archetype)
- What platform? (Twitter, Substack, YouTube, Medium)
- What's the goal? (educate, position, engage, convert)
### Step 2: Read Completely Without Judgment
First pass: Read the entire piece without marking anything. Get the gestalt.
### Step 3: Systematic Evaluation
Go through each dimension in order:
1. Scientific Rigor
2. Voice Authenticity
3. Positioning Alignment
4. Audience Calibration
5. Credibility Risk
6. Engagement Potential
### Step 4: Synthesize and Prioritize
**Create final assessment:**
```
═══════════════════════════════════════════════════════
REFLECTION SUMMARY
════════════════════════════Related in Image & Video
watch
IncludedWatch a video (URL or local path). Downloads with yt-dlp, extracts auto-scaled frames with ffmpeg, pulls the transcript from captions (or Whisper API fallback), and hands the result to Claude so it can answer questions about what's in the video.
physical-ai-defect-image-generation
IncludedUse when the user wants to orchestrate defect image generation, run associated setup, or handle outputs on OSMO. The Day 0 path handles cold-start with USD-to-ROI, image-edit augmentation, and AnomalyGen to create initial PCBA datasets. The Day 1 path performs inference and labeling on real images. This skill helps with first-time asset setup, creation of finetuning checkpoints, and configuring deployment. Trigger keywords: defect image generation, dig workflow, dig pipeline, defect image detection workflow, aoi pipeline, aoi anomalygen, usd2roi anomalygen, day 0 pcba, day 1 pcba, day 1 real-photo alignment, day 1 manual roi, metal surface anomaly, glass defect, anomalygen finetune, setup_pcb, setup_metal, setup_glass, setup_pretrained, dig setup, dig datasets, dig pretrained checkpoint, dig image-edit endpoint.
accelint-react-best-practices
IncludedReact performance optimization and best practices. ALWAYS use this skill when working with any React code - writing components, hooks, JSX; refactoring; optimizing re-renders, memoization, state management; reviewing for performance; fixing hydration mismatches; debugging infinite re-renders, stale closures, input focus loss, animations restarting; preventing remounting; implementing transitions, lazy initialization, effect dependencies. Even simple React tasks benefit from these patterns. Covers React 19+ (useEffectEvent, Activity, ref props). Triggers - useEffect, useState, useMemo, useCallback, memo, inline components, nested components, components inside components, re-render, performance, hydration, SSR, Next.js, useDeferredValue, combined hooks.
elevenlabs-agents
IncludedBuild conversational AI voice agents with ElevenLabs Platform using React, JavaScript, React Native, or Swift SDKs. Configure agents, tools (client/server/MCP), RAG knowledge bases, multi-voice, and Scribe real-time STT. Use when: building voice chat interfaces, implementing AI phone agents with Twilio, configuring agent workflows or tools, adding RAG knowledge bases, testing with CLI "agents as code", or troubleshooting deprecated @11labs packages, Android audio cutoff, CSP violations, dynamic variables, or WebRTC config. Keywords: ElevenLabs Agents, ElevenLabs voice agents, AI voice agents, conversational AI, @elevenlabs/react, @elevenlabs/client, @elevenlabs/react-native, @elevenlabs/elevenlabs-js, @elevenlabs/agents-cli, elevenlabs SDK, voice AI, TTS, text-to-speech, ASR, speech recognition, turn-taking model, WebRTC voice, WebSocket voice, ElevenLabs conversation, agent system prompt, agent tools, agent knowledge base, RAG voice agents, multi-voice agents, pronunciation dictionary, voice speed control, elevenlabs scribe, @11labs deprecated, Android audio cutoff, CSP violation elevenlabs, dynamic variables elevenlabs, case-sensitive tool names, webhook authentication
humanizer
IncludedHumanize AI-generated text by detecting and removing patterns typical of LLM output. Rewrites text to sound natural, specific, and human. Uses 28 pattern detectors, 560+ AI vocabulary terms across 3 tiers, and statistical analysis (burstiness, type-token ratio, readability) for comprehensive detection. Use when asked to humanize text, de-AI writing, make content sound more natural/human, review writing for AI patterns, score text for AI detection, or improve AI-generated drafts. Covers content, language, style, communication, and filler categories.
generating-mermaid-diagrams
IncludedSalesforce architecture diagrams using Mermaid with ASCII fallback. Use this skill when generating text-based diagrams for Salesforce architecture, OAuth flows, ERDs, integration sequences, or Agentforce structure. TRIGGER when: user says "diagram", "visualize", "ERD", or asks for sequence diagrams, flowcharts, class diagrams, or architecture visualizations in Mermaid. DO NOT TRIGGER when: user wants PNG/SVG image output (use generating-visual-diagrams), or asks about non-Salesforce systems.