Agent skill

Scientific Writing

by Yrzsh in Yrzsh/paper-workbench

A skill your agent uses when writing or revising scientific manuscripts, abstracts, figures, or references for journal submission and you need full-paragraph prose, scientific structure…

MITAuto-check passedResearch & Science

Install Scientific Writing

skills CLI
$ npx skills add Yrzsh/paper-workbench --skill scientific-writing -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install Yrzsh/paper-workbench scientific-writing --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/Yrzsh/paper-workbench.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/scientific-writing .claude/skills/scientific-writing && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
scientific-writing
GitHub stars
112
Token cost
~7.4k tokens
SKILL.md length
3,368 words
Files
1
Skills in repo
3
Repo updated
First seen
Licence
MIT

At a glance

A skill your agent uses when writing or revising scientific manuscripts, abstracts, figures, or references for journal submission and you need full-paragraph prose, scientific structure…

  • Works in 10 steps: Manuscript Structure and Organization → Section-Specific Writing Guidance → Citation and Reference Management → …
  • Revising scientific manuscripts
  • SKILL.md covers Overview, When to Use This Skill, Visual Enhancement with… and Core Capabilities, plus 4 more sections
  • Calls python; needs OPENROUTER_API_KEY

What it does

Scientific Writing is an agent skill from Yrzsh/paper-workbench. Use when writing or revising scientific manuscripts, abstracts, figures, or references for journal submission and you need full-paragraph prose, scientific structure, citation-style guidance, or reporting-guideline support.

Its SKILL.md is about 7.4k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Research & Science, covering Scientific writing and Citation management. The repository describes itself as: Paper Workbench — 论文写作审查全流程工作台 / End-to-end academic writing & review workbench. The licence is MIT.

When your agent uses it

  • Revising scientific manuscripts
  • References for journal submission and you need full-paragraph prose
  • Scientific structure
  • Citation-style guidance

Example prompts

  • “/scientific-writing”

Requirements

  • Python 3
  • A credential in OPENROUTER_API_KEY

Workflow steps

10 steps, taken from the step headings in SKILL.md.

  1. Manuscript Structure and Organization
  2. Section-Specific Writing Guidance
  3. Citation and Reference Management
  4. Figures and Tables
  5. Reporting Guidelines by Study Type
  6. Writing Principles and Style
  7. Writing Process: From Outline to Full Paragraphs
  8. Journal-Specific Formatting
  9. Field-Specific Language and Terminology
  10. Common Pitfalls to Avoid

What it can do on your machine

Read from SKILL.md and the folder at commit 801516a. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • python

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names these keys or tokens, usually read from environment variables:

    • OPENROUTER_API_KEY

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Scientific Writing loads about 7.4k tokens when it runs. Until then it costs about 61 tokens; SKILL.md has 3,368 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~61
When it runs · the whole SKILL.md, loaded when a task matches
~7.4k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from Yrzsh/paper-workbench at commit 801516a, republished under its MIT licence (© Yrzsh). 3,368 words, ~7,443 tokens.

Download SKILL.mdSave it as .claude/skills/scientific-writing/SKILL.md (or your agent's skills folder).
name
scientific-writing
description
Use when writing or revising scientific manuscripts, abstracts, figures, or references for journal submission and you need full-paragraph prose, scientific structure, citation-style guidance, or reporting-guideline support.

Scientific Writing

Overview

This is the core journal-writing skill in this repository. Use it to turn a stable scientific story into clear, well-structured manuscript prose while keeping citations, figures, and reporting standards aligned.

Scientific writing is a process for communicating research with precision and clarity. Write manuscripts using IMRAD structure, citations (APA/AMA/Vancouver), figures/tables, and reporting guidelines (CONSORT/STROBE/PRISMA). Apply this skill for research papers and journal submissions.

Critical Principle: Always write in full paragraphs with flowing prose. Never submit bullet points in the final manuscript. Use a two-stage process: first create section outlines with key points from verified notes, literature, and results, then convert those outlines into complete paragraphs.

For revision-heavy journal manuscripts, do not jump from stale prose directly to polishing. First stabilize the section with a reverse outline and a claim-evidence map, then rewrite the paragraphs.

When to Use This Skill

This skill should be used when:

  • Writing or revising any section of a scientific manuscript (abstract, introduction, methods, results, discussion)
  • Structuring a research paper using IMRAD or other standard formats
  • Formatting citations and references in specific styles (APA, AMA, Vancouver, Chicago, IEEE)
  • Creating, formatting, or improving figures, tables, and data visualizations
  • Applying study-specific reporting guidelines (CONSORT for trials, STROBE for observational studies, PRISMA for reviews)
  • Drafting abstracts that meet journal requirements (structured or unstructured)
  • Preparing manuscripts for submission to specific journals
  • Improving writing clarity, conciseness, and precision
  • Ensuring proper use of field-specific terminology and nomenclature
  • Addressing reviewer comments and revising manuscripts

For title, abstract, cover-letter, or top-level logic decisions, read references/editor-first-impression.md.

Visual Enhancement with Scientific Figures

When a manuscript would benefit from a schematic, workflow diagram, or conceptual figure, use this repository's nature-figure skill, which ships an OpenRouter AI-schematic route. It is not in the default recommended set because it needs a plotting backend or an OPENROUTER_API_KEY; install it from the Figure Stack (see the installation docs).

Before finalizing any document:

  1. Add at least one figure when it materially improves comprehension.
  2. Prefer 2-3 figures for longer papers (methods flowchart, results visualization, conceptual diagram).

How to generate figures:

  • Use the nature-figure skill's OpenRouter route to generate publication-style schematics.
  • Write prompts that specify academic style, white background, clean labels, colorblind-friendly colors, and high contrast.
  • Save outputs under a local figures/ directory in the current project.

Example command (via the nature-figure skill, once installed):

bash
export OPENROUTER_API_KEY="sk-or-..."
python ~/.codex/skills/nature-figure/scripts/generate_openrouter_schematic.py \
  --title "Your method" \
  --panel-map "left: problem; center: proposed mechanism; right: validated outcome" \
  --outdir figures --basename schematic --resolution 2K
# Claude Code (global install): replace ~/.codex/skills with ~/.claude/skills
# Claude Code (project-local install): replace ~/.codex/skills with .claude/skills

Requires OPENROUTER_API_KEY. Iterate on the panel map and title until the figure is publication-ready. See nature-figure's references/openrouter-image-generation.md for full options.

When to add figures:

  • Study design and methodology flowcharts (CONSORT, PRISMA, STROBE)
  • Conceptual framework diagrams
  • Experimental workflow illustrations
  • Data analysis pipeline diagrams
  • Biological pathway or mechanism diagrams
  • System architecture visualizations
  • Any complex concept that benefits from visualization

For detailed guidance on creating figures, refer to the nature-figure skill.


Core Capabilities

1. Manuscript Structure and Organization

IMRAD Format: Guide papers through the standard Introduction, Methods, Results, And Discussion structure used across most scientific disciplines. This includes:

  • Introduction: Establish research context, identify gaps, state objectives
  • Methods: Detail study design, populations, procedures, and analysis approaches
  • Results: Present findings objectively without interpretation
  • Discussion: Interpret results, acknowledge limitations, propose future directions

For detailed guidance on IMRAD structure, refer to references/imrad_structure.md.

Alternative Structures: Support discipline-specific formats including:

  • Review articles (narrative, systematic, scoping)
  • Case reports and case series
  • Meta-analyses and pooled analyses
  • Theoretical/modeling papers
  • Methods papers and protocols
2. Section-Specific Writing Guidance

Editor-First Front Door: Make the title, abstract, introduction, Results, discussion, and cover letter answer the same four questions in the same order:

  • why did the study need to be done
  • what did you do
  • what did you find
  • how does the study advance the field

If these sections answer different versions of the story, the manuscript will feel fragmented even when the prose is locally strong.

Abstract Composition: Craft concise, standalone summaries (100-250 words) that capture the paper's purpose, methods, results, and conclusions. Support both structured abstracts (with labeled sections) and unstructured single-paragraph formats. Make the abstract state the problem, the aim/method, the key result, and the implication. Do not spend most of the space on generic background or report only that results were significant.

Title and Cover Letter: Make the title a concise summary of the main contribution, ideally about 20 words or fewer. Prefer concrete keywords, avoid question-form titles, avoid unnecessary abbreviations, and avoid making the method the title unless the method itself is the main contribution. Make the cover letter about one page, state significance, journal fit, readership fit, and one or two key findings, and do not turn it into a second abstract or a full result list.

Top-Level Logic: Keep one visible chain across the manuscript:

  • topic
  • published work
  • unresolved problem
  • objective
  • methodology
  • results and figures
  • summary of findings
  • interpretation
  • implication for the field

Introduction Development: Build compelling introductions that:

  • Establish the research problem's importance
  • Review relevant literature systematically
  • Identify knowledge gaps or controversies
  • State clear research questions or hypotheses
  • Explain the study's novelty and significance

Methods Documentation: Ensure reproducibility through:

  • Detailed participant/sample descriptions
  • Clear procedural documentation
  • Statistical methods with justification
  • Equipment and materials specifications
  • Ethical approval and consent statements

Results Presentation: Present findings with:

  • Logical flow from primary to secondary outcomes
  • Integration with figures and tables
  • Statistical significance with effect sizes
  • Objective reporting without interpretation

Discussion Construction: Synthesize findings by:

  • Relating results to research questions
  • Comparing with existing literature
  • Acknowledging limitations honestly
  • Proposing mechanistic explanations
  • Suggesting practical implications and future research
3. Citation and Reference Management

Apply citation styles correctly across disciplines. For comprehensive style guides, refer to references/citation_styles.md.

Major Citation Styles:

  • AMA (American Medical Association): Numbered superscript citations, common in medicine
  • Vancouver: Numbered citations in square brackets, biomedical standard
  • APA (American Psychological Association): Author-date in-text citations, common in social sciences
  • Chicago: Notes-bibliography or author-date, humanities and sciences
  • IEEE: Numbered square brackets, engineering and computer science

Best Practices:

  • Cite primary sources when possible
  • Include recent literature (last 5-10 years for active fields)
  • Balance citation distribution across introduction and discussion
  • Verify all citations against original sources
  • Use reference management software (Zotero, Mendeley, EndNote)
4. Figures and Tables

Create effective data visualizations that enhance comprehension. For detailed best practices, refer to references/figures_tables.md.

When to Use Tables vs. Figures:

  • Tables: Precise numerical data, complex datasets, multiple variables requiring exact values
  • Figures: Trends, patterns, relationships, comparisons best understood visually

Design Principles:

  • Make each table/figure self-explanatory with complete captions
  • Use consistent formatting and terminology across all display items
  • Label all axes, columns, and rows with units
  • Include sample sizes (n) and statistical annotations
  • Follow the "one table/figure per 1000 words" guideline
  • Avoid duplicating information between text, tables, and figures

Common Figure Types:

  • Bar graphs: Comparing discrete categories
  • Line graphs: Showing trends over time
  • Scatterplots: Displaying correlations
  • Box plots: Showing distributions and outliers
  • Heatmaps: Visualizing matrices and patterns
5. Reporting Guidelines by Study Type

Ensure completeness and transparency by following established reporting standards. For comprehensive guideline details, refer to references/reporting_guidelines.md.

Key Guidelines:

  • CONSORT: Randomized controlled trials
  • STROBE: Observational studies (cohort, case-control, cross-sectional)
  • PRISMA: Systematic reviews and meta-analyses
  • STARD: Diagnostic accuracy studies
  • TRIPOD: Prediction model studies
  • ARRIVE: Animal research
  • CARE: Case reports
  • SQUIRE: Quality improvement studies
  • SPIRIT: Study protocols for clinical trials
  • CHEERS: Economic evaluations

Each guideline provides checklists ensuring all critical methodological elements are reported.

6. Writing Principles and Style

Apply fundamental scientific writing principles. For detailed guidance, refer to references/writing_principles.md.

Clarity:

  • Use precise, unambiguous language
  • Define technical terms and abbreviations at first use
  • Maintain logical flow within and between paragraphs
  • Use active voice when appropriate for clarity

Conciseness:

  • Eliminate redundant words and phrases
  • Favor shorter sentences (15-20 words average)
  • Remove unnecessary qualifiers
  • Respect word limits strictly

Accuracy:

  • Report exact values with appropriate precision
  • Use consistent terminology throughout
  • Distinguish between observations and interpretations
  • Acknowledge uncertainty appropriately

Objectivity:

  • Present results without bias
  • Avoid overstating findings or implications
  • Acknowledge conflicting evidence
  • Maintain professional, neutral tone
7. Writing Process: From Outline to Full Paragraphs

CRITICAL: Always write in full paragraphs, never submit bullet points in scientific papers.

Scientific papers must be written in complete, flowing prose. Use this two-stage approach for effective writing:

Stage 1: Create Section Outlines with Key Points

When starting a new section:

  1. Gather the relevant literature and data from verified local notes, trusted web sources, or an installed literature-search skill
  2. Create a structured outline with bullet points marking:
    • Main arguments or findings to present
    • Key studies to cite
    • Data points and statistics to include
    • Logical flow and organization
  3. These bullet points serve as scaffolding—they are NOT the final manuscript

Example outline (Introduction section):

- Background: AI in drug discovery gaining traction
  * Cite recent reviews (Smith 2023, Jones 2024)
  * Traditional methods are slow and expensive
- Gap: Limited application to rare diseases
  * Only 2 prior studies (Lee 2022, Chen 2023)
  * Small datasets remain a challenge
- Our approach: Transfer learning from common diseases
  * Novel architecture combining X and Y
- Study objectives: Validate on 3 rare disease datasets

Stage 2: Convert Key Points to Full Paragraphs

Once the outline is complete, expand each bullet point into proper prose:

  1. Transform bullet points into complete sentences with subjects, verbs, and objects
  2. Add transitions between sentences and ideas (however, moreover, in contrast, subsequently)
  3. Integrate citations naturally within sentences, not as lists
  4. Expand with context and explanation that bullet points omit
  5. Ensure logical flow from one sentence to the next within each paragraph
  6. Vary sentence structure to maintain reader engagement

Example conversion to prose:

Artificial intelligence approaches have gained significant traction in drug discovery 
pipelines over the past decade (Smith, 2023; Jones, 2024). While these computational 
methods show promise for accelerating the identification of therapeutic candidates, 
traditional experimental approaches remain slow and resource-intensive, often requiring 
years of laboratory work and substantial financial investment. However, the application 
of AI to rare diseases has been limited, with only two prior studies demonstrating 
proof-of-concept results (Lee, 2022; Chen, 2023). The primary obstacle has been the 
scarcity of training data for conditions affecting small patient populations. 

To address this challenge, we developed a transfer learning approach that leverages 
knowledge from well-characterized common diseases to predict therapeutic targets for 
rare conditions. Our novel neural architecture combines convolutional layers for 
molecular feature extraction with attention mechanisms for protein-ligand interaction 
modeling. The objective of this study was to validate our approach across three 
independent rare disease datasets, assessing both predictive accuracy and biological 
interpretability of the results.

Key Differences Between Outlines and Final Text:

Outline (Planning Stage)Final Manuscript
Bullet points and fragmentsComplete sentences and paragraphs
Telegraphic notesFull explanations with context
List of citationsCitations integrated into prose
Abbreviated ideasDeveloped arguments with transitions
For your eyes onlyFor publication and peer review

Common Mistakes to Avoid:

  • ❌ Never leave bullet points in the final manuscript
  • ❌ Never submit lists where paragraphs should be
  • ❌ Don't use numbered or bulleted lists in Results or Discussion sections (except for specific cases like study hypotheses or inclusion criteria)
  • ❌ Don't write sentence fragments or incomplete thoughts
  • ✅ Do use occasional lists only in Methods (e.g., inclusion/exclusion criteria, materials lists)
  • ✅ Do ensure every section flows as connected prose
  • ✅ Do read paragraphs aloud to check for natural flow

When Lists ARE Acceptable (Limited Cases):

Lists may appear in scientific papers only in specific contexts:

  • Methods: Inclusion/exclusion criteria, materials and reagents, participant characteristics
  • Supplementary Materials: Extended protocols, equipment lists, detailed parameters
  • Never in: Abstract, Introduction, Results, Discussion, Conclusions

Integration with Literature Search:

Verified literature gathering is essential for Stage 1 (creating outlines):

  1. Search for relevant papers using trusted sources or an installed literature-search skill
  2. Extract key findings, methods, and data
  3. Organize findings as bullet points in your outline
  4. Then convert the outline to full paragraphs in Stage 2

This two-stage process ensures you:

  • Gather and organize information systematically
  • Create logical structure before writing
  • Produce polished, publication-ready prose
  • Maintain focus on the narrative flow
7A. Reverse Outline And Claim-Evidence Pass For Revisions

When revising an existing manuscript section rather than drafting from scratch:

  1. Reverse-outline the current text:
    • section thesis
    • one-line message for each paragraph
    • the evidence, citation, or reasoning each paragraph carries
  2. For all major claims in the Abstract, Introduction, Results topic sentences, and Discussion, write:
    • Claim: ... | Evidence: ... | Status: supported / partial / missing
  3. If a claim is marked partial or missing, do one of three things only:
    • weaken it
    • add the missing evidence
    • move it into motivation, interpretation, or future work
  4. Only after this pass, rewrite into full journal prose.

Use this especially when:

  • the section has been revised many times
  • the front half may now be stronger than the Results
  • paragraph flow feels smooth but the logic still feels unstable
7B. Skeptical Self-Review Before Finalizing

Before treating a section as finished, ask:

  • Is the contribution actually clear?
  • Is every major claim readable and self-contained?
  • Does the empirical evidence directly support the claim I am making?
  • Is an important baseline, ablation, or caveat missing?
  • Would a skeptical reviewer call the method, framework, or resource insufficiently justified?

If the answer is not clearly defensible from the manuscript itself, revise the section before polishing style.

8. Journal-Specific Formatting

Adapt manuscripts to journal requirements:

  • Follow author guidelines for structure, length, and format
  • Apply journal-specific citation styles
  • Meet figure/table specifications (resolution, file formats, dimensions)
  • Include required statements (funding, conflicts of interest, data availability, ethical approval)
  • Adhere to word limits for each section
  • Format according to template requirements when provided
Show full SKILL.md (1,387 more words)Show less
9. Field-Specific Language and Terminology

Adapt language, terminology, and conventions to match the specific scientific discipline. Each field has established vocabulary, preferred phrasings, and domain-specific conventions that signal expertise and ensure clarity for the target audience.

Identify Field-Specific Linguistic Conventions:

  • Review terminology used in recent high-impact papers in the target journal
  • Note field-specific abbreviations, units, and notation systems
  • Identify preferred terms (e.g., "participants" vs. "subjects," "compound" vs. "drug," "specimens" vs. "samples")
  • Observe how methods, organisms, or techniques are typically described

Biomedical and Clinical Sciences:

  • Use precise anatomical and clinical terminology (e.g., "myocardial infarction" not "heart attack" in formal writing)
  • Follow standardized disease nomenclature (ICD, DSM, SNOMED-CT)
  • Specify drug names using generic names first, brand names in parentheses if needed
  • Use "patients" for clinical studies, "participants" for community-based research
  • Follow Human Genome Variation Society (HGVS) nomenclature for genetic variants
  • Report lab values with standard units (SI units in most international journals)

Molecular Biology and Genetics:

  • Use italics for gene symbols (e.g., TP53), regular font for proteins (e.g., p53)
  • Follow species-specific gene nomenclature (uppercase for human: BRCA1; sentence case for mouse: Brca1)
  • Specify organism names in full at first mention, then use accepted abbreviations (e.g., Escherichia coli, then E. coli)
  • Use standard genetic notation (e.g., +/+, +/-, -/- for genotypes)
  • Employ established terminology for molecular techniques (e.g., "quantitative PCR" or "qPCR," not "real-time PCR")

Chemistry and Pharmaceutical Sciences:

  • Follow IUPAC nomenclature for chemical compounds
  • Use systematic names for novel compounds, common names for well-known substances
  • Specify chemical structures using standard notation (e.g., SMILES, InChI for databases)
  • Report concentrations with appropriate units (mM, μM, nM, or % w/v, v/v)
  • Describe synthesis routes using accepted reaction nomenclature
  • Use terms like "bioavailability," "pharmacokinetics," "IC50" consistently with field definitions

Ecology and Environmental Sciences:

  • Use binomial nomenclature for species (italicized: Homo sapiens)
  • Specify taxonomic authorities at first species mention when relevant
  • Employ standardized habitat and ecosystem classifications
  • Use consistent terminology for ecological metrics (e.g., "species richness," "Shannon diversity index")
  • Describe sampling methods with field-standard terms (e.g., "transect," "quadrat," "mark-recapture")

Physics and Engineering:

  • Follow SI units consistently unless field conventions dictate otherwise
  • Use standard notation for physical quantities (scalars vs. vectors, tensors)
  • Employ established terminology for phenomena (e.g., "quantum entanglement," "laminar flow")
  • Specify equipment with model numbers and manufacturers when relevant
  • Use mathematical notation consistent with field standards (e.g., ℏ for reduced Planck constant)

Neuroscience:

  • Use standardized brain region nomenclature (e.g., refer to atlases like Allen Brain Atlas)
  • Specify coordinates for brain regions using established stereotaxic systems
  • Follow conventions for neural terminology (e.g., "action potential" not "spike" in formal writing)
  • Use "neural activity," "neuronal firing," "brain activation" appropriately based on measurement method
  • Describe recording techniques with proper specificity (e.g., "whole-cell patch clamp," "extracellular recording")

Social and Behavioral Sciences:

  • Use person-first language when appropriate (e.g., "people with schizophrenia" not "schizophrenics")
  • Employ standardized psychological constructs and validated assessment names
  • Follow APA guidelines for reducing bias in language
  • Specify theoretical frameworks using established terminology
  • Use "participants" rather than "subjects" for human research

General Principles:

Match Audience Expertise:

  • For specialized journals: Use field-specific terminology freely, define only highly specialized or novel terms
  • For broad-impact journals (e.g., Nature, Science): Define more technical terms, provide context for specialized concepts
  • For interdisciplinary audiences: Balance precision with accessibility, define terms at first use

Define Technical Terms Strategically:

  • Define abbreviations at first use: "messenger RNA (mRNA)"
  • Provide brief explanations for specialized techniques when writing for broader audiences
  • Avoid over-defining terms well-known to the target audience (signals unfamiliarity with field)
  • Create a glossary if numerous specialized terms are unavoidable

Maintain Consistency:

  • Use the same term for the same concept throughout (don't alternate between "medication," "drug," and "pharmaceutical")
  • Follow a consistent system for abbreviations (decide on "PCR" or "polymerase chain reaction" after first definition)
  • Apply the same nomenclature system throughout (especially for genes, species, chemicals)

Avoid Field Mixing Errors:

  • Don't use clinical terminology for basic science (e.g., don't call mice "patients")
  • Avoid colloquialisms or overly general terms in place of precise field terminology
  • Don't import terminology from adjacent fields without ensuring proper usage

Verify Terminology Usage:

  • Consult field-specific style guides and nomenclature resources
  • Check how terms are used in recent papers from the target journal
  • Use domain-specific databases and ontologies (e.g., Gene Ontology, MeSH terms)
  • When uncertain, cite a key reference that establishes terminology
10. Common Pitfalls to Avoid

Top Rejection Reasons:

  1. Inappropriate, incomplete, or insufficiently described statistics
  2. Over-interpretation of results or unsupported conclusions
  3. Poorly described methods affecting reproducibility
  4. Small, biased, or inappropriate samples
  5. Poor writing quality or difficult-to-follow text
  6. Inadequate literature review or context
  7. Figures and tables that are unclear or poorly designed
  8. Failure to follow reporting guidelines

Writing Quality Issues:

  • Mixing tenses inappropriately (use past tense for methods/results, present for established facts)
  • Excessive jargon or undefined acronyms
  • Paragraph breaks that disrupt logical flow
  • Missing transitions between sections
  • Inconsistent notation or terminology

Workflow for Manuscript Development

Stage 1: Planning

  1. Identify target journal and review author guidelines
  2. Determine applicable reporting guideline (CONSORT, STROBE, etc.)
  3. Outline manuscript structure (usually IMRAD)
  4. Plan figures and tables as the backbone of the paper

Stage 2: Drafting (Use two-stage writing process for each section)

  1. Start with figures and tables (the core data story)
  2. For each section below, follow the two-stage process:
    • First: Create outline with bullet points from verified literature, notes, and results
    • Second: Convert bullet points to full paragraphs with flowing prose
  3. Write Methods (often easiest to draft first)
  4. Draft Results (describing figures/tables objectively)
  5. Compose Discussion (interpreting findings)
  6. Write Introduction (setting up the research question)
  7. Craft Abstract (synthesizing the complete story)
  8. Create Title (concise and descriptive)

Remember: Bullet points are for planning only—the final manuscript must be in complete paragraphs.

Stage 3: Revision

  1. Check logical flow and "red thread" throughout
  2. Verify consistency in terminology and notation
  3. Ensure figures/tables are self-explanatory
  4. Confirm adherence to reporting guidelines
  5. Verify all citations are accurate and properly formatted
  6. Check word counts for each section
  7. Proofread for grammar, spelling, and clarity

Stage 4: Final Preparation

  1. Format according to journal requirements
  2. Prepare supplementary materials
  3. Write cover letter highlighting significance
  4. Complete submission checklists
  5. Gather all required statements and forms

Integration with Other Scientific Skills

This skill works effectively with:

  • Data analysis skills: For generating results to report
  • Statistical analysis: For determining appropriate statistical presentations
  • Literature review skills: For contextualizing research
  • Figure creation tools: For developing publication-quality visualizations

References

This skill includes comprehensive reference files covering specific aspects of scientific writing:

  • references/imrad_structure.md: Detailed guide to IMRAD format and section-specific content
  • references/citation_styles.md: Complete citation style guides (APA, AMA, Vancouver, Chicago, IEEE)
  • references/figures_tables.md: Best practices for creating effective data visualizations
  • references/reporting_guidelines.md: Study-specific reporting standards and checklists
  • references/writing_principles.md: Core principles of effective scientific communication
  • references/latex-layout.md: LaTeX float placement and typesetting fixes (loose pages, stranded headings, figures that do not fill the page, "Float too large")

Load these references as needed when working on specific aspects of scientific writing.

Nature-Style Academic Polishing

Sentence Length Control

Rule: Every sentence in the polished output must be ≤30 words and span no more than 2 lines at standard formatting.

Cohesion strategies:

StrategyExample
Restate the subject"The resulting serial sections exhibit inherent spatial asymmetry. Such asymmetry makes pixel-level alignment unattainable."
Adverbial connective"PAS captures only one dimension of the pathology. Therefore, special stains are essential."
Pronoun reference"Pathologists employ a panel of histochemical stains. Each targets a distinct feature."
Definite article + noun"The renal biopsy specimen is small. The limited tissue complicates multi-modal analysis."
Demonstrative + noun"This heterogeneity makes IgAN an ideal test case."
Practical Heuristics
  • Each English sentence should carry ONE subject + ONE verb as its core.
  • Avoid overloading sentences with participial phrases, lists, or multiple propositions.
  • Split long sentences to improve clarity and flow.
Example

Before: To characterise phenotypic evolution and spatial reorganisation within this microenvironment during kidney injury, pathologists employ a panel of histochemical stains. PAS, Masson's trichrome, PAM and H&E each interrogate distinct pathological dimensions, including basement membrane lesions, collagen deposition and cellular infiltration, enabling a composite assessment of tissue damage. (38 words)

After: To characterise phenotypic evolution and spatial reorganisation within this microenvironment during kidney injury, pathologists employ a panel of histochemical stains. PAS, Masson's trichrome, PAM and H&E each interrogate distinct pathological dimensions. These include basement membrane lesions, collagen deposition and cellular infiltration. Together, they enable a composite assessment of tissue damage.

© Yrzsh, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/scientific-writing of Yrzsh/paper-workbench.

Open the folder on GitHubat commit 801516a

Compare with similar skills

Scientific Writing next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Scientific Writing compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Scientific Writing this skillYrzsh/paper-workbench112—~7.4kAutomated safety check: PassMIT
Citation Verification GuideGalaxy-Dawn/claude-scholar5.7k2 repos~1.9kAutomated safety check: PassMIT
Citation ManagementK-Dense-AI/claude-scientific-writer2.4k2 repos~3.9kAutomated safety check: NotesMIT
Academic Paper Writing PipelineImbad0202/academic-research-skills51k—~16kAutomated safety check: PassCustom licence
Academic HumanizerAIScientists-Dev/academic-humanizer1.9k1 repos~4.2kAutomated safety check: PassMIT
Academic Research Suite for CodexImbad0202/academic-research-skills-codex12k—~12kAutomated safety check: PassCustom licence

Similar skills

  • Citation Verification Guide

    Galaxy-Dawn/claude-scholar

    Reference guidance for checking every citation in academic writing against canonical sources such as DOI, arXiv, CrossRef and Semantic Scholar, to catch fake or wrong references.

    5.7k GitHub starsUsed in 2 repos~1.9k tokens
    Research & ScienceAuto-check passed
  • Citation Management

    K-Dense-AI/claude-scientific-writer

    Finds papers in OpenAlex, PubMed and Google Scholar, turns DOIs, PMIDs and arXiv IDs into clean BibTeX, and validates citations for a manuscript or thesis.

    2.4k GitHub starsUsed in 2 repos~3.9k tokens
    Research & ScienceAuto-check: notes
  • Academic Paper Writing Pipeline

    Imbad0202/academic-research-skills

    Runs a 12-agent pipeline that plans, drafts, cites, reviews and formats academic papers, with modes for revision, rebuttals, abstracts and citation checks.

    51k GitHub stars~16k tokensUpdated yesterday
    Research & ScienceAuto-check passed
  • Academic Humanizer

    AIScientists-Dev/academic-humanizer

    Improve the clarity and voice of AI-assisted academic writing (papers, theses, rebuttals) and funding proposals (NSF Project Summary/Description, NIH Specific Aims): preserve scholarly conventions…

    1.9k GitHub starsUsed in 1 repo~4.2k tokens
    Research & ScienceAuto-check passed
  • Academic Research Suite for Codex

    Imbad0202/academic-research-skills-codex

    A router skill that sends academic work such as literature reviews, drafting, citation checks, peer review and revision to the right workflow in the ARS suite.

    12k GitHub stars~12k tokensUpdated 7 days ago
    Research & ScienceAuto-check passed
  • Autonomous Research

    federicodeponte/opendraft

    An 18-agent pipeline that turns one topic line into a drafted research paper, literature review, or thesis chapter.

    507 GitHub stars~8.2k tokensUpdated 9 days ago
    Research & ScienceAuto-check passed

More from Yrzsh/paper-workbench

  • Paper Staged Gen

    Yrzsh/paper-workbench

    A skill your agent uses when generating or regenerating a full manuscript with the DSH Paper Workbench staged pipeline — contract-first, per-section generation with citation-pool gates, programmatic…

    112 GitHub stars~524 tokensUpdated 1 mo ago
    Auto-check passed
  • Write Scientific Manuscript

    Yrzsh/paper-workbench

    Diagnose and repair the clarity and logic of manuscript prose, journal-agnostic.

    112 GitHub stars~2.7k tokensUpdated 1 mo ago
    Auto-check passed

Questions about Scientific Writing

What does Scientific Writing do?

A skill your agent uses when writing or revising scientific manuscripts, abstracts, figures, or references for journal submission and you need full-paragraph prose, scientific structure…. Scientific Writing is an agent skill from Yrzsh/paper-workbench. Use when writing or revising scientific manuscripts, abstracts, figures, or references for journal submission and you need full-paragraph prose, scientific structure, citation-style guidance, or reporting-guideline support.

When should I use Scientific Writing?

Scientific Writing fits situations like: revising scientific manuscripts; references for journal submission and you need full-paragraph prose; scientific structure; citation-style guidance.

How do I install Scientific Writing in Claude Code?

Run `npx skills add Yrzsh/paper-workbench --skill scientific-writing -a claude-code`. Or copy the skill folder (skills/scientific-writing in Yrzsh/paper-workbench) into .claude/skills/scientific-writing in your project. Claude Code loads it when a task matches its description.

How do I install Scientific Writing in Codex?

Run `npx skills add Yrzsh/paper-workbench --skill scientific-writing -a codex`. Or copy the skill folder (skills/scientific-writing in Yrzsh/paper-workbench) into .agents/skills/scientific-writing in your project. Codex loads it when a task matches its description.

Can I use Scientific Writing in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Yrzsh/paper-workbench --skill scientific-writing -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/scientific-writing, .gemini/skills/scientific-writing, .github/skills/scientific-writing and .opencode/skills/scientific-writing in your project.

What does Scientific Writing need to run?

Going by SKILL.md and its folder, Scientific Writing needs the command-line tools its instructions call (python) and credentials named OPENROUTER_API_KEY. Our summary lists: Python 3; A credential in OPENROUTER_API_KEY.

Does Scientific Writing access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Scientific Writing safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Scientific Writing use?

Scientific Writing is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Scientific Writing use?

About 7.4k tokens (SKILL.md is roughly 30k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Scientific Writing?

Skills that share tags, products or a category with Scientific Writing: Citation Verification Guide (Galaxy-Dawn/claude-scholar, 5.7k stars), Citation Management (K-Dense-AI/claude-scientific-writer, 2.4k stars), Academic Paper Writing Pipeline (Imbad0202/academic-research-skills, 51k stars) and Academic Humanizer (AIScientists-Dev/academic-humanizer, 1.9k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Scientific Writing?

Yrzsh (a GitHub user) maintains it in Yrzsh/paper-workbench, which has 112 GitHub stars. The repository holds 3 skills in this directory. The repository was last updated on September 7, 2026.

Source: Yrzsh/paper-workbench on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.