Claude-skill-registry academic-research-writing
Use when writing CS research papers (conference, journal, thesis), reviewing scientific manuscripts, improving academic writing clarity, or preparing IEEE/ACM submissions. Invoke when user mentions paper, manuscript, research writing, journal submission, or needs help with academic structure, formatting, or revision.
install
source · Clone the upstream repo
git clone https://github.com/majiayu000/claude-skill-registry
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/majiayu000/claude-skill-registry "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/data/academic-research-writing" ~/.claude/skills/majiayu000-claude-skill-registry-academic-research-writing && rm -rf "$T"
manifest:
skills/data/academic-research-writing/SKILL.mdsource content
Academic Research Writing
Overview
Comprehensive toolkit for writing and reviewing computer science research papers. Combines paper writing workflows, manuscript review processes, clarity principles, and formatting standards.
When to Use
Writing Mode:
- Writing new research papers (conference, journal, thesis)
- Creating survey/review papers
- Structuring technical contributions
Review Mode:
- Reviewing/editing existing manuscripts
- Pre-submission polish
- Addressing reviewer comments
- Collaborative editing
Both Modes:
- Improving academic writing clarity
- Preparing IEEE/ACM submissions
- Learning academic writing conventions
Mode Selection
User request received | v Is this about WRITING new content or REVIEWING existing content? | +---> Writing new paper -----> Use Writing Workflow | (references/writing-workflow.md) | +---> Reviewing/editing -----> Use Review Workflow | existing manuscript (references/review-workflow.md) | +---> Both/unclear ----------> Start with Review Workflow to assess, then write
Quick Reference
Writing a Paper
- Clarify scope - topic, venue, format (IEEE/ACM)
- Create outline - section-by-section plan
- Draft core sections - methodology first, then results
- Write supporting sections - intro, related work, discussion
- Add citations - 15-20+ references
- Review & polish - use checklists
See:
references/writing-workflow.md
Reviewing a Manuscript
- Extract core message - one sentence summary
- Structural pass - overall organization
- Section reviews - intro, results, discussion
- Scientific clarity - claims, evidence, hedging
- Language polish - terminology, voice
- Formatting check - journal compliance
See:
references/review-workflow.md
Core Resources
| Resource | Purpose |
|---|---|
| 6-step paper writing process |
| 8-step manuscript review process |
| Section-by-section narrative structure (Problem->Solution->Evidence) |
| Gopen & Swan sentence-level clarity |
| Common academic phrases by section |
| CS-specific writing conventions |
| Combined quality checklists |
| IEEE formatting specifications |
| ACM formatting specifications |
Templates
| Template | Purpose |
|---|---|
| Introduction arc, results paragraph, discussion templates |
| Core message extraction, structural assessment, language guidelines |
Evaluation
Use
evaluators/rubric.json for quality scoring:
- Structure and Organization (weight: 1.0)
- Scientific Rigor (weight: 1.2)
- Language and Clarity (weight: 1.0)
- Section-Specific Quality (weight: 1.0)
- Formatting Compliance (weight: 0.8)
- Citation Quality (weight: 0.8)
Minimum threshold: Average score >= 3.5
Seven Core Principles
- Clarity over cleverness - Scientific clarity beats stylistic elegance
- Narrative shapes comprehension - Structure determines understanding
- Audience dictates tone - Expert vs. general requires different framing
- Format signals credibility - Professional formatting reflects rigor
- Claims require evidence - Strong assertions need strong data
- Each section has a job - Intro sells, Results show, Discussion interprets
- Constraints shape structure - Word limits determine emphasis
Guardrails
Critical requirements:
- Preserve author voice - edit for clarity, don't rewrite
- Claims match data - flag overclaiming immediately
- Quantitative rigor - statistics for all comparisons
- Logical flow - clear transitions between sections
- Appropriate hedging - match evidence strength
- Consistent terminology - same term for same concept
Common pitfalls to avoid:
- Overclaiming ("proves" when data only suggests)
- Missing context (results without interpretation)
- Buried lede (important findings hidden)
- Inconsistent terms (alternating synonyms)
- Vague descriptions ("some increase" vs "3-fold increase")
External Guides
| Guide | Purpose |
|---|---|
| Practical conference paper structuring guidelines (Introduction paragraphs, experiments, tables/figures) |
PDF Templates
- IEEE templateassets/full_paper_template.pdf
- ACM templateassets/interim-layout.pdf