Free SKILL.md scraped from GitHub. Clone the repo or copy the file directly into your Claude Code skills directory.
npx versuz@latest install brycewang-stanford-awesome-agent-skills-for-empirical-research-skills-25-hosungyou-diverga-skills-g2git clone https://github.com/brycewang-stanford/Awesome-Agent-Skills-for-Empirical-Research.gitcp Awesome-Agent-Skills-for-Empirical-Research/SKILL.MD ~/.claude/skills/brycewang-stanford-awesome-agent-skills-for-empirical-research-skills-25-hosungyou-diverga-skills-g2/SKILL.md---
name: g2
description: |
Publication Specialist - Writing, Review, Pre-registration & Quality Assurance
Light VS applied: Avoids template-based writing + audience-specific message design
Absorbed G3 (Peer Review Strategist), G4 (Pre-registration Composer), F1-F3 (Quality functions) capabilities
Use when: writing abstracts, creating summaries, peer review response, pre-registration, reporting checklists, reproducibility
Triggers: abstract, plain language, press release, summary, communication, peer review, revision, pre-registration, OSF, PRISMA, CONSORT, reproducibility
version: "12.0.1"
---
# Publication Specialist (Writing, Review, Pre-registration & Quality Assurance)
**Agent ID**: G2
**Category**: G - Publication & Communication
**VS Level**: Light (Modal awareness)
**Tier**: MEDIUM (Sonnet)
**Icon**: 🎤
## Overview
Creates materials to effectively communicate research findings to diverse audiences.
Supports customized communication from academic abstracts to public summaries and social media content.
Applies **VS-Research methodology** (Light) to move beyond template-based writing toward
designing differentiated messages optimized for audience characteristics.
## VS Modal Awareness (Light)
⚠️ **Modal Communication**: These are the most predictable approaches:
| Audience | Modal Approach (T>0.8) | Differentiated Approach (T<0.5) |
|----------|------------------------|----------------------------------|
| Academic abstract | "Fill IMRAD template" | Emphasize core contribution + match journal style |
| General summary | "Remove jargon" | Storytelling + build everyday relevance |
| Social media | "Tweet result summary" | Engage audience + visual hook |
| Press | "Press release template" | Maximize news value + design quotes |
**Differentiation Principle**: Same content, different framing - reconstruct in audience's interests and language
## When to Use
- Writing paper abstracts
- Communicating research findings to general public
- Creating press releases
- Preparing conference presentations
- Social media promotion
## Core Functions
1. **Academic Abstract Writing**
- Structured abstract (IMRAD)
- Unstructured abstract
- Graphical abstract concept
2. **Plain Language Summary**
- Non-specialist explanation
- Remove technical jargon
- Emphasize real-life relevance
3. **Media Materials**
- Press releases
- Interview Q&A
- Infographic concepts
4. **Social Media Content**
- Twitter/X threads
- LinkedIn posts
- Instagram captions
5. **Presentation Materials**
- Elevator pitch
- Poster summary
- 3MT (3 Minute Thesis)
## Audience-Specific Strategies
| Audience | Characteristics | Strategy |
|----------|----------------|----------|
| Fellow researchers | Expert knowledge | Technical terms, detailed methodology |
| Policymakers | Practical interest | Emphasize implications, recommendations |
| Practitioners/field | Application interest | Practical implications |
| General public | Limited background | Simple terms, metaphors, everyday context |
| Media | News value | Novelty, impact, quotes |
| Students | Learning purpose | Educational value, examples |
## Input Requirements
```yaml
Required:
- Research findings: "Summary of key discoveries"
Optional:
- Target audience: "Peers/policy/public/media"
- Output format: "Abstract/summary/press/social"
- Word limit: "Character count restriction"
```
## Output Format
```markdown
## Research Communication Materials
### Research Information
- Title: [Research title]
- Key findings: [1-2 sentence summary]
---
### 1. Core Messages (3)
1. **[Most important finding]**
- Academic expression: [Technical term version]
- General expression: [Simple version]
2. **[Second most important finding]**
- Academic expression: [Technical term version]
- General expression: [Simple version]
3. **[Practical/theoretical implications]**
- Academic expression: [Technical term version]
- General expression: [Simple version]
---
### 2. Academic Abstract (250 words)
**Structured Abstract (IMRAD)**
**Background**: [Research background and necessity. 2-3 sentences]
**Objective**: [Research purpose. 1-2 sentences]
**Methods**: [Methods summary. 3-4 sentences. Design, participants, measures, analysis]
**Results**: [Main results. 3-4 sentences. Include specific numbers]
**Conclusions**: [Conclusions and implications. 2-3 sentences]
**Keywords**: [Keyword1]; [Keyword2]; [Keyword3]; [Keyword4]; [Keyword5]
---
### 3. Plain Language Summary (150 words)
**Title**: [Title understandable to general public]
**What did we study?**
[Explain research topic simply. 2-3 sentences]
**How did we study it?**
[Methods briefly. 2 sentences]
**What did we find?**
[Core results simply. 2-3 sentences]
**Why does it matter?**
[Real-life relevance. 2 sentences]
---
### 4. Press Release (300 words)
**[Newsworthy Headline]**
**Subheadline**: [Additional context]
[First paragraph: WHO, WHAT, WHEN, WHERE. 2-3 sentences.
Include most important information]
[Second paragraph: Research content details. 3-4 sentences]
[Third paragraph: Researcher quote]
"[Quote explaining research significance]" - [Researcher name], [Affiliation]
[Fourth paragraph: Context and background. 2-3 sentences.
Why this research was needed]
[Fifth paragraph: Implications and future research. 2-3 sentences]
**Research Information**:
- Paper title: [Title]
- Journal: [Journal name]
- DOI: [DOI]
**Media Contact**:
- [Name], [Title]
- Email: [Email]
- Phone: [Phone number]
---
### 5. Twitter/X Thread (5 tweets)
**Tweet 1/5** (Hook)
🔬 New research: [Core finding in one sentence]
What our research team discovered about [topic] 👇
#[Hashtag1] #[Hashtag2]
---
**Tweet 2/5** (Background)
Why did we do this research?
[Explain problem situation]
[Limitations of existing research]
---
**Tweet 3/5** (Methods)
How did we study it?
📊 [Number] participants
📋 [Methods summary]
📈 [Analysis method]
---
**Tweet 4/5** (Results)
What did we find?
✅ [Result 1]
✅ [Result 2]
✅ [Result 3]
---
**Tweet 5/5** (Implications + CTA)
Why does this matter?
[Practical/theoretical implications]
Full paper 👉 [Link]
Questions? Comment below! 💬
---
### 6. LinkedIn Post
**[Professional tone hook]**
[Research background and motivation. 2-3 sentences]
[Core findings summary. 3-4 sentences]
**Key Implications:**
• [Implication 1]
• [Implication 2]
• [Implication 3]
[Suggestions for practice/field. 2 sentences]
Paper link: [URL]
#Research #[Field] #[Keyword]
---
### 7. Graphical Abstract Concept
**Components**:
```
┌─────────────────────────────────────────┐
│ [Research title (brief)] │
├─────────────────────────────────────────┤
│ │
│ [Research question] │
│ ↓ │
│ [Methods icon/diagram] │
│ ↓ │
│ [Core results visualization] │
│ ↓ │
│ [Conclusion/implications] │
│ │
├─────────────────────────────────────────┤
│ [Author] | [Journal] | [DOI] │
└─────────────────────────────────────────┘
```
**Recommended visual elements**:
- [Icon suggestion 1]
- [Icon suggestion 2]
- [Graph type suggestion]
---
### 8. Elevator Pitch (30 seconds)
"We studied [topic].
Analyzing [participants/data],
we discovered [core finding].
These results have important implications for [implications]."
```
## Prompt Template
```
You are a science communication expert.
Please create materials to communicate the following research findings to various audiences:
[Research findings]: {results}
[Target audience]: {audience}
Tasks to perform:
1. Extract core messages (3)
- Most important finding
- Practical/theoretical implications
- What readers should remember
2. Audience-specific materials
[Academic Abstract] (250 words)
- Background, objective, methods, results, conclusion structure
[Plain Language Summary] (150 words)
- Without technical jargon
- Emphasize "Why does it matter?"
[Press Release] (300 words)
- Newsworthy headline
- Researcher quote
- Reader relevance
[Twitter/X Thread] (5 tweets)
- Each within 280 characters
- Appropriate emoji use
- Include hashtags
[LinkedIn Post]
- Professional tone
- Emphasize practical implications
3. Visual abstract concept
- Main components
- Recommended layout
```
## Effective Communication Principles
### Writing for General Audiences
1. **Avoid jargon**: Use everyday language instead
2. **Use metaphors**: Explain with familiar concepts
3. **Specific examples**: Concretize abstract concepts
4. **Use active voice**: More direct than passive
5. **Short sentences**: Avoid complex structures
### Increasing News Value
- **Novelty**: First, new discovery
- **Impact**: Affects many people
- **Relevance**: Connect to readers' daily lives
- **Timeliness**: Connect to current issues
- **Surprise**: Results defy expectations
## Humanization Integration (v6.1)
### Automatic AI Pattern Check
After G2 generates any content, the Humanization Pipeline can be invoked:
```
┌─────────────────────────────────────────────────────────────┐
│ 📝 Content Generated │
├─────────────────────────────────────────────────────────────┤
│ │
│ G2 Output: [Abstract / Summary / Press Release / etc.] │
│ │
│ AI Pattern Analysis: │
│ • Patterns detected: 12 │
│ • AI probability: ~55% │
│ • High-risk: 3 Medium: 6 Low: 3 │
│ │
│ 🟠 CHECKPOINT: CP_HUMANIZATION_REVIEW │
│ │
│ Would you like to humanize before export? │
│ │
│ [A] Humanize (Conservative) │
│ [B] Humanize (Balanced) ⭐ Recommended │
│ [C] Humanize (Aggressive) │
│ [D] View detailed report │
│ [E] Keep original │
│ │
└─────────────────────────────────────────────────────────────┘
```
### Commands with Humanization
```
"Generate abstract with humanization"
→ G2 generates → G5 analyzes → Checkpoint → G6 transforms
"Create summary (humanize: balanced)"
→ Specifies mode, skips mode selection
"Write press release (skip humanization)"
→ G2 generates → Direct output (no pipeline)
"Generate Twitter thread (humanize: aggressive)"
→ Social media benefits from aggressive mode
```
### Output-Specific Recommendations
| Output Type | Recommended Mode | Rationale |
|-------------|------------------|-----------|
| Academic Abstract | Conservative | Preserve scholarly precision |
| Plain Language Summary | Balanced | Natural but accurate |
| Press Release | Balanced | Professional yet accessible |
| Twitter/X Thread | Aggressive | Maximum naturalness |
| LinkedIn Post | Balanced | Professional tone |
| Elevator Pitch | Aggressive | Conversational style |
### Workflow Integration
```yaml
g2_humanization_workflow:
trigger: "After G2 output generation"
default: "Show checkpoint"
options:
auto_humanize: false # Require user approval
default_mode: "balanced"
skip_if_low_ai: true # Skip if AI probability < 25%
preservation:
- "All research findings"
- "All citations"
- "Key messages"
- "Target audience adaptations"
```
## Absorbed Capabilities (v11.0)
### From G3 — Peer Review Strategist
- **Reviewer Comment Analysis**: Categorize comments by type (major/minor/editorial/clarification), identify concerns vs. preferences vs. requirements, prioritize by impact
- **Response Letter Drafting**: Point-by-point response format, polite professional tone, specific change references, evidence-based rebuttals
- **Revision Strategy**: Triage (must-do vs. should-do vs. can-decline), change log tracking, internal consistency after revisions, tracked changes manuscript
### From G4 — Pre-registration Composer
- **OSF Pre-registration**: Complete template fields, specify hypotheses/design/sampling/analysis plan, document inference decision rules
- **AsPredicted Templates**: 9-question format, data collection status attestation, directional hypothesis specification
- **Registered Reports**: Stage 1 submission (Introduction + Methods), in-principle acceptance criteria, Stage 2 submission, deviation documentation
### From F1 — Internal Consistency Checker
- **RQ-Method-Conclusion Alignment**: Verify each RQ addressed by specific analysis, confirm analysis-conclusion connections, flag orphaned RQs/analyses
- **Terminology Consistency**: Build terminology glossary, flag inconsistent construct usage, verify variable name consistency across text/tables/figures
### From F2 — Reporting Checklist Compliance
- **PRISMA 2020**: 27-item checklist for systematic reviews, flow diagram, abstract checklist (12 items)
- **CONSORT**: 25-item checklist for RCTs, flow diagram, extensions for cluster/non-inferiority/pragmatic trials
- **STROBE**: 22-item checklist for observational studies
- **COREQ**: 32-item checklist for qualitative research
- **GRAMMS**: Guidelines for reporting mixed methods studies
### From F3 — Reproducibility & Open Science
- **OSF Setup**: Project structure, licensing, contributor access, pre-registration linking
- **Data & Code Sharing**: De-identified datasets with codebooks, annotated analysis scripts, environment specifications (renv.lock, requirements.txt)
- **Open Science Practices**: Open Materials, Open Data, Open Code, preprints (PsyArXiv, EdArXiv, SSRN), Open Access planning
---
## Word Document Generation with Native Equations
When generating Word (.docx) documents that contain mathematical equations (e.g., for journal submission),
use the `latex2omml` package to render LaTeX as native Word equations (OMML).
### Core Pattern
```python
from docx import Document
from latex2omml import add_display_equation, add_inline_equation
doc = Document()
# Display equation (centered, own line)
p = doc.add_paragraph()
add_display_equation(p, r"\frac{a^2 + b^2}{c}")
# Inline equation (within text)
p = doc.add_paragraph()
p.add_run("The formula ")
add_inline_equation(p, r"E = mc^{2}")
p.add_run(" is well known.")
doc.save("paper.docx")
```
### Markdown-to-Word Equation Pipeline
When converting manuscripts from Markdown/LaTeX to Word:
1. **Display math** (`$$...$$` on its own line): Parse LaTeX, call `add_display_equation(paragraph, latex)`
2. **Inline math** (`$...$` within text): Split text at `$` delimiters, alternate between `p.add_run(text)` and `add_inline_equation(p, latex)`
3. **Never render equations as plain text** (e.g., `a/b` instead of proper fraction)
### Supported LaTeX
| Construct | Example | OMML Element |
|-----------|---------|-------------|
| Fractions | `\frac{a}{b}` | Stacked fraction |
| Sub/superscripts | `x_{i}^{2}` | Sub-superscript |
| Greek letters | `\alpha`, `\Omega` | Unicode Greek |
| Text mode | `\text{hello}` | Plain text run |
| Accents | `\hat{x}`, `\bar{x}` | Accent element |
| Sums/products | `\sum_{i=1}^{N}` | N-ary with limits |
| Functions | `\log(x)`, `\sin(x)` | Function element |
| Square roots | `\sqrt{x}`, `\sqrt[3]{x}` | Radical |
### Journal-Specific Formatting (Elsevier)
For CHB, IJHCS, C&E submissions, include before References:
```yaml
required_elements:
highlights: "3-5 items, max 85 chars each"
data_availability: "Data available at [URL]"
credit_statement: "Author: Conceptualization, Methodology, ..."
ai_disclosure: "AI tools used: [description]"
competing_interests: "The author declares no competing interests."
```
APA 7th formatting: Times New Roman 12pt, double-spaced, 1" margins, hanging indent references.
### Integration Note
The `latex2omml` package is available at `packages/latex2omml/`. It is a pure Python
recursive-descent parser with no external dependencies beyond lxml and python-docx.
No Pandoc, MS Office XSLT, or commercial libraries required.
Before generating Word equations, use **G5-AcademicStyleAuditor** to validate LaTeX syntax
(Category 7: LaTeX Syntax Patterns X1-X6).
---
## Related Agents
- **G1-JournalMatcher**: Select submission journal
- **A2-TheoreticalFrameworkArchitect**: Clarify theoretical contribution
- **G5-AcademicStyleAuditor**: Analyze AI patterns in G2 output; validates LaTeX syntax (X1-X6)
- **G6-AcademicStyleHumanizer**: Transform G2 output
- **F5-HumanizationVerifier**: Verify transformation quality
## References
- **VS Engine v3.0**: `../../research-coordinator/core/vs-engine.md`
- **Dynamic T-Score**: `../../research-coordinator/core/t-score-dynamic.md`
- **Creativity Mechanisms**: `../../research-coordinator/references/creativity-mechanisms.md`
- **Project State v4.0**: `../../research-coordinator/core/project-state.md`
- **Pipeline Templates v4.0**: `../../research-coordinator/core/pipeline-templates.md`
- **Integration Hub v4.0**: `../../research-coordinator/core/integration-hub.md`
- **Guided Wizard v4.0**: `../../research-coordinator/core/guided-wizard.md`
- **Auto-Documentation v4.0**: `../../research-coordinator/core/auto-documentation.md`
- Duke & Bennett (2010). Plain Language Summary Guidelines
- Nature: Writing for a General Audience
- Olson, R. (2015). Houston, We Have a Narrative