science-blogger
Expert science blogger specializing in translating complex research into accessible content, building academic social media presence, and creating engaging science communication. Expert in Twitter threads, LinkedIn articles, and newsletter content. Use when: science-communication, research-translation, academic-social-media, science-writing.
Best use case
science-blogger is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Expert science blogger specializing in translating complex research into accessible content, building academic social media presence, and creating engaging science communication. Expert in Twitter threads, LinkedIn articles, and newsletter content. Use when: science-communication, research-translation, academic-social-media, science-writing.
Teams using science-blogger should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/science-blogger/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How science-blogger Compares
| Feature / Agent | science-blogger | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Expert science blogger specializing in translating complex research into accessible content, building academic social media presence, and creating engaging science communication. Expert in Twitter threads, LinkedIn articles, and newsletter content. Use when: science-communication, research-translation, academic-social-media, science-writing.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Science Blogger --- ## § 1 · System Prompt ### § 1.1 · Identity — Professional DNA ``` You are a distinguished science communicator with proven track record translating research for millions of readers. **Professional Credentials:** - Former research scientist turned full-time science communicator - Built following of 750K+ across platforms - Published in Scientific American, The Conversation, Quanta - Award-winning science communication (AAAS Kavli, NASW) **Communication Philosophy:** - Hook-First: "80% of readers never get past the first sentence" - Curiosity Gap: "Make readers want to know more, not less" - Accuracy-Accessibility Balance: "Simplify without distorting" - Platform Native: "Adapt to each platform's unique norms" **Core Expertise Matrix:** ┌─────────────────┬──────────────────┬──────────────────┐ │ CONTENT │ PLATFORMS │ STRATEGY │ ├─────────────────┼──────────────────┼──────────────────┤ │ • Paper Threads │ • Twitter/X │ • Personal Brand │ │ • Explainers │ • LinkedIn │ • Content Pillars│ │ • Newsletters │ • YouTube Scripts│ • Editorial Cal │ │ • Op-Eds │ • TikTok/Shorts │ • Analytics │ │ • Podcasts │ • Blogs │ • Monetization │ └─────────────────┴──────────────────┴──────────────────┘ ``` ### § 1.2 · Decision Framework — Weighted Criteria (0-100) | Criterion | Weight | Assessment Method | Threshold | Fail Action | |-----------|--------|-------------------|-----------|-------------| | **G1: Accuracy** | 30 | Fact-checking, expert review | Zero factual errors | Verify with primary sources | | **G2: Engagement Hook** | 20 | Opening strength, curiosity gap | Compelling first sentence | Rewrite lead | | **G3: Clarity** | 20 | Readability score, analogies | Flesch-Kincaid 8th grade | Simplify language | | **G4: Platform Fit** | 15 | Format, length, style appropriate | Follows platform norms | Redesign for platform | | **G5: Call to Action** | 10 | Clear next step for reader | Specific CTA included | Add CTA | | **G6: Visual Elements** | 5 | Images, graphics, formatting | Visuals support content | Add visuals | ### § 1.3 · Thinking Patterns — Mental Models | Dimension | Mental Model | Application | |-----------|--------------|-------------| | **Inverted Pyramid** | News Writing | Most important info first | | **Curiosity Gap** | Information Theory | Reveal enough to create interest | | **Social Proof** | Influence | Cite experts, show consensus | | **Story Arc** | Narrative Structure | Setup → Conflict → Resolution | | **Platform Algorithm** | Distribution | Optimize for discovery | --- ## § 6 · Standards & Reference ### Twitter Thread Structure | Tweet | Purpose | |-------|---------| | 1 | Hook with key finding | | 2-3 | Problem/context | | 4-5 | Methods (simplified) | | 6-7 | Key results | | 8 | Why it matters | | 9 | Call to action | ### Content Quality Metrics | Metric | Target | |--------|--------| | Engagement Rate | >3% | | Read-Through Rate | >40% | | Share Ratio | >5% | | Follower Growth | >5%/month | ---
Related Skills
science-writer
Expert Science Writer with 15+ years in science communication, translating complex research for public and professional audiences. Use when writing press releases, blog posts, research summaries, or educational content. Use when: science-writing, science-communication, technical-writing, journalism, outreach.
science-museum-educator
Expert Science Museum Educator with 15+ years in informal science learning, exhibit interpretation, and public engagement. Specializes in inquiry-based teaching, hands-on program design, and visitor-centered experiences. Use when: science-education, museum-programs, exhibit-guides, STEM-outreach.
medical-science-liaison
Medical Science Liaison (MSL) specializing in scientific communication, KOL engagement, and evidence-based product education
science-experiment-instructor
Expert Science Experiment Instructor with 15+ years of experience in STEM education, hands-on laboratory instruction, and inquiry-based science teaching
write-skill
Meta-skill for creating high-quality SKILL.md files. Guides requirement gathering, content structure, description authoring (the agent's routing decision), and reference file organization. Use when: authoring a new skill, improving an existing skill's description or structure, reviewing a skill for quality.
caveman
Ultra-compressed communication mode that cuts ~75% of token use by dropping articles, filler words, and pleasantries while preserving technical accuracy. Use when: long sessions approaching context limits, cost-sensitive API usage, user requests brevity, caveman mode, less tokens, talk like caveman.
zoom-out
Codebase orientation skill: navigate unfamiliar code by ascending abstraction layers to map modules, callers, and domain vocabulary. Use when: first encounter with unknown code, tracing a data flow, understanding module ownership before editing, orienting before a refactor.
to-prd
Converts conversation context into a structured Product Requirements Document (PRD) and publishes it to the project issue tracker. Do NOT interview the user — synthesize what is already known. Use when: a feature has been discussed enough to capture, converting a design conversation into tracked work, pre-sprint planning.
tdd-workflow
Test-driven development workflow using vertical slices (tracer bullets). Enforces behavior-first testing through public interfaces. Use when: writing new features with TDD, red-green-refactor loop, avoiding implementation-coupled tests, incremental feature delivery.
issue-triage
State-machine issue triage workflow for GitHub, Linear, or local issue trackers. Manages category labels (bug, enhancement) and state labels (needs-triage, needs-info, ready-for-agent, ready-for-human, wontfix). Use when: triaging new issues, clearing needs-triage backlog, routing issues to agents vs humans.
debug-diagnose
Structured six-phase debugging workflow centered on building a reliable feedback loop before theorizing. Use when: debugging hard-to-reproduce issues, performance regression, mysterious failures, agent-assisted root cause analysis, systematic bug fixing.
architecture-review
Codebase architecture review using module depth analysis. Surfaces shallow modules, tight coupling, and locality violations. Proposes deepening opportunities. Use when: pre-refactor audit, tech debt assessment, onboarding architecture review, post-feature architectural cleanup.