Agent skill

Scientific Writing

by LigphiDonk in LigphiDonk/Oh-my--paper

Core skill for the deep research and writing tool. An agent skill from LigphiDonk/Oh-my--paper.

MITAuto-check passedResearch & Science

Install Scientific Writing

skills CLI
$ npx skills add LigphiDonk/Oh-my--paper --skill scientific-writing -a claude-code

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

GitHub CLI
$ gh skill install LigphiDonk/Oh-my--paper 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/LigphiDonk/Oh-my--paper.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
739
Token cost
~6.5k tokens
SKILL.md length
2,775 words
Files
6 (incl. references)
Skills in repo
27
Repo updated
First seen
Licence
MIT

At a glance

Core skill for the deep research and writing tool. An agent skill from LigphiDonk/Oh-my--paper.

  • Works in 10 steps: Manuscript Structure and Organization → Section-Specific Writing Guidance → Citation and Reference Management → …
  • Tasks that involve Scientific writing
  • SKILL.md covers Canonical Summary, Trigger Rules, Resource Use Rules and Execution Contract, plus 8 more sections
  • Calls python

What it does

Scientific Writing is an agent skill from LigphiDonk/Oh-my--paper. Core skill for the deep research and writing tool.

Its SKILL.md is about 6.5k tokens, which your agent loads only when the skill is triggered. The skill folder holds 6 other files, including reference files (for example `references/citation_styles.md`, `references/figures_tables.md` and `references/imrad_structure.md`).

It sits in Research & Science, covering Scientific writing and Deep research. The repository describes itself as: A Claude Code plugin that turns your terminal into an autonomous research lab — literature survey, experiment execution, paper writing, all in one pipeline. The licence is MIT.

When your agent uses it

  • Tasks that involve Scientific writing
  • Tasks that involve Deep research

Example prompts

  • “/scientific-writing”

Requirements

  • Python 3

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 6baece9. 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 no API keys, tokens, secrets or passwords.

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

Context cost

Scientific Writing loads about 6.5k tokens when it runs, and up to ~39k if it reads all its reference files. Until then it costs about 17 tokens; SKILL.md has 2,775 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~17
When it runs · the whole SKILL.md, loaded when a task matches
~6.5k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~39k

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 LigphiDonk/Oh-my--paper at commit 6baece9, republished under its MIT licence (© LigphiDonk). 2,775 words, ~6,492 tokens.

Download SKILL.mdSave it as .claude/skills/scientific-writing/SKILL.md (or your agent's skills folder). This skill also uses 5 other files; get the full folder from GitHub.
name
scientific-writing
description
Core skill for the deep research and writing tool.
id
scientific-writing
version
1.0.0
stages
publication
tools
read_file, search_project, write_file
summary
Core skill for the deep research and writing tool. Write scientific manuscripts in full paragraphs (never bullet points). Use two-stage process: (1) create…
primaryIntent
writing
intents
writing, research
capabilities
visualization-reporting
domains
general
keywords
scientific-writing, paper writing, visualization-reporting, scientific, writing, core, deep, research, tool, write, manuscripts, full

scientific-writing

Canonical Summary

Core skill for the deep research and writing tool. Write scientific manuscripts in full paragraphs (never bullet points). Use two-stage process: (1) create section outlines with key points using research-lookup, (2) convert to flowing pros...

Trigger Rules

Use this skill when the user request matches its research workflow scope. Prefer the bundled resources instead of recreating templates or reference material. Keep outputs traceable to project files, citations, scripts, or upstream evidence.

Resource Use Rules

  • Read from references/ only when the current task needs the extra detail.

Execution Contract

  • Resolve every relative path from this skill directory first.
  • Prefer inspection before mutation when invoking bundled scripts.
  • If a required runtime, CLI, credential, or API is unavailable, explain the blocker and continue with the best manual fallback instead of silently skipping the step.
  • Do not write generated artifacts back into the skill directory; save them inside the active project workspace.

Upstream Instructions

Scientific Writing

Overview

This is the core skill for the deep research and writing tool—combining AI-driven deep research with well-formatted written outputs. Every document produced is backed by comprehensive literature search and verified citations through the research-lookup skill.

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 using research-lookup, then convert those outlines into complete 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

Visual Enhancement with Scientific Schematics

⚠️ MANDATORY: Every scientific paper MUST include at least 1-2 AI-generated figures using the scientific-schematics skill.

This is not optional. Scientific papers without visual elements are incomplete. Before finalizing any document:

  1. Generate at minimum ONE schematic or diagram using scientific-schematics
  2. Prefer 2-3 figures for comprehensive papers (methods flowchart, results visualization, conceptual diagram)

How to generate figures:

  • Use the scientific-schematics skill to generate AI-powered publication-quality diagrams
  • Simply describe your desired diagram in natural language
  • Nano Banana Pro will automatically generate, review, and refine the schematic

How to generate schematics:

bash
python scripts/generate_schematic.py "your diagram description" -o figures/output.png

The AI will automatically:

  • Create publication-quality images with proper formatting
  • Review and refine through multiple iterations
  • Ensure accessibility (colorblind-friendly, high contrast)
  • Save outputs in the figures/ directory

When to add schematics:

  • 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 schematics, refer to the scientific-schematics skill documentation.


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

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.

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. Use the research-lookup skill to gather relevant literature and data
  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 Research Lookup:

The research-lookup skill is essential for Stage 1 (creating outlines):

  1. Search for relevant papers using research-lookup
  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
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,126 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 using research-lookup
    • 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

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

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

Files

SKILL.md and 5 other files (references) in skills/scientific-writing of LigphiDonk/Oh-my--paper.

  • SKILL.md
  • references/citation_styles.md
  • references/figures_tables.md
  • references/imrad_structure.md
  • references/reporting_guidelines.md
  • references/writing_principles.md

Open the folder on GitHubat commit 6baece9

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 skillLigphiDonk/Oh-my--paper739—~6.5kAutomated safety check: PassMIT
Academic Research PipelineImbad0202/academic-research-skills51k—~15kAutomated safety check: PassCustom licence
Academic Research Suite for CodexImbad0202/academic-research-skills-codex12k—~12kAutomated safety check: PassCustom licence
Scientific Writingneflibata-feng/MyArxiv-Agent12618 repos~8.4kAutomated safety check: NotesMIT
Research ClawAlphaLab-USTC/ResearchClaw134—~578Automated safety check: PassMIT
Journal Submission Researchhuangwb8/ChineseResearchLaTeX2.9k—~1.2kAutomated safety check: PassMIT

Similar skills

  • Academic Research Pipeline

    Imbad0202/academic-research-skills

    Orchestrates a ten-stage academic workflow from research to finished manuscript, including integrity checks, two rounds of peer review and revision.

    51k GitHub stars~15k tokensUpdated 2 days ago
    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
  • Scientific Writing

    neflibata-feng/MyArxiv-Agent

    Core skill for the deep research and writing tool. An agent skill from neflibata-feng/MyArxiv-Agent.

    126 GitHub starsUsed in 18 repos~8.4k tokens
    Research & ScienceAuto-check: notes
  • Research Claw

    AlphaLab-USTC/ResearchClaw

    Complete AI research assistant with 6 core capabilities: paper discovery, deep reading notes, reading list management, research taste learning, idea generation, and paper writing.

    134 GitHub stars~578 tokensUpdated 6 mo ago
    Research & ScienceAuto-check passed
  • Journal Submission Research

    huangwb8/ChineseResearchLaTeX

    Researches a named academic journal's submission requirements, formatting rules, fees, review speed and community feedback, and writes one Chinese markdown report.

    2.9k GitHub stars~1.2k tokensUpdated 6 days ago
    Research & ScienceAuto-check passed
  • ResearchClaw Research Pipeline

    aiming-lab/AutoResearchClaw

    Runs the ResearchClaw 23-stage autonomous pipeline from a topic, config file and output directory, from literature review through experiments to a written and reviewed paper.

    15k GitHub stars~1k tokensUpdated 1 mo ago
    Research & ScienceAuto-check passed

More from LigphiDonk/Oh-my--paper

All 27 skills in this repo
  • Preprint Search on bioRxiv

    LigphiDonk/Oh-my--paper

    Searches bioRxiv life sciences preprints by keyword, author, date range or category with a Python script, returning JSON metadata and optional PDF downloads.

    739 GitHub starsUsed in 12 repos~3.7k tokens
    Auto-check passed
  • Literature PDF OCR Library Builder

    LigphiDonk/Oh-my--paper

    Searches and downloads legally accessible academic PDFs, OCRs them to Markdown, and organizes the results into a traceable, AI-readable literature library.

    739 GitHub stars~1.1k tokensUpdated 5 mo ago
    Auto-check passed
  • Inno Code Survey

    LigphiDonk/Oh-my--paper

    Finds and clones missing code repositories for a chosen research idea, then writes a survey that maps academic concepts to their implementations.

    739 GitHub stars~3.6k tokensUpdated 5 mo ago
    Auto-check passed
  • Turns experimental data such as CSV, JSON or TensorBoard logs into statistical significance tests, visualizations and a drafted Results section.

    739 GitHub stars~3k tokensUpdated 5 mo ago
    Auto-check passed
  • Citation Verification Guide

    LigphiDonk/Oh-my--paper

    Lays out principles for catching fake, mismatched, or inconsistently formatted citations in academic writing, checked through live web search.

    739 GitHub stars~2.2k tokensUpdated 5 mo ago
    Auto-check passed
  • Single-Cell Initial Analysis

    LigphiDonk/Oh-my--paper

    Runs a seven-step quality-control and exploration pipeline on scRNA-seq, CyTOF or flow cytometry data and writes a plain-language report of what it found.

    739 GitHub starsUsed in 1 repo~1.4k tokens
    Auto-check passed

Questions about Scientific Writing

What does Scientific Writing do?

Core skill for the deep research and writing tool. An agent skill from LigphiDonk/Oh-my--paper. Scientific Writing is an agent skill from LigphiDonk/Oh-my--paper. Core skill for the deep research and writing tool.

When should I use Scientific Writing?

Scientific Writing fits situations like: tasks that involve Scientific writing; tasks that involve Deep research.

How do I install Scientific Writing in Claude Code?

Run `npx skills add LigphiDonk/Oh-my--paper --skill scientific-writing -a claude-code`. Or copy the skill folder (skills/scientific-writing in LigphiDonk/Oh-my--paper) 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 LigphiDonk/Oh-my--paper --skill scientific-writing -a codex`. Or copy the skill folder (skills/scientific-writing in LigphiDonk/Oh-my--paper) 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 LigphiDonk/Oh-my--paper --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). Our summary lists: Python 3.

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 6.5k tokens (SKILL.md is roughly 26k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 32k tokens, read only when the agent opens those files.

What are the alternatives to Scientific Writing?

Skills that share tags, products or a category with Scientific Writing: Academic Research Pipeline (Imbad0202/academic-research-skills, 51k stars), Academic Research Suite for Codex (Imbad0202/academic-research-skills-codex, 12k stars), Scientific Writing (neflibata-feng/MyArxiv-Agent, 126 stars) and Research Claw (AlphaLab-USTC/ResearchClaw, 134 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Scientific Writing?

LigphiDonk (a GitHub user) maintains it in LigphiDonk/Oh-my--paper, which has 739 GitHub stars. The repository holds 27 skills in this directory. The repository was last updated on April 15, 2026.

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