agentleFS
erafaterafat/skills/scientific-writing/SKILL.md

scientific-writing

Skill17 starsChanged 28 days agoMITView on GitHub

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 prose. IMRAD structure, citations (APA/AMA/Vancouver), figures/tables, reporting guidelines (CONSORT/STROBE/PRISMA), for research papers and journal submissions.

41 other projects use a version of this, 12 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use usfiscaldata, research-grants and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • yf8578Skill

    usfiscaldata

    Query the U.S. Treasury Fiscal Data API for federal financial data including national debt, government spending, revenue, interest rates, exchange rates, and savings bonds. Access 54 datasets and 182 data tables with no API key required. Use when working with U.S. federal fiscal data, national debt tracking (Debt to the Penny), Daily Treasury Statements, Monthly Treasury Statements, Treasury securities auctions, interest rates on Treasury securities, foreign exchange rates, savings bonds, or any U.S. government financial statistics.

    Also in 7 projects that use this

  • garri333Skill

    research-grants

    Write competitive research proposals for NSF, NIH, DOE, DARPA, and Taiwan NSTC. Agency-specific formatting, review criteria, budget preparation, broader impacts, significance statements, innovation narratives, and compliance with submission requirements.

    Also in 10 projects that use this

  • garri333Skill

    arboreto

    Infer gene regulatory networks (GRNs) from gene expression data using scalable algorithms (GRNBoost2, GENIE3). Use when analyzing transcriptomics data (bulk RNA-seq, single-cell RNA-seq) to identify transcription factor-target gene relationships and regulatory interactions. Supports distributed computation for large-scale datasets.

    Also in 9 projects that use this

  • Hongyu-yuSkill

    torch-geometric

    Graph Neural Networks (PyG). Node/graph classification, link prediction, GCN, GAT, GraphSAGE, heterogeneous graphs, molecular property prediction, for geometric deep learning.

    Also in 9 projects that use this

  • SoljournerSkill

    get-available-resources

    Enumerate installed packages, databases, and tools for engineering workflows

    Also in 9 projects that use this

  • +7 more from garri333

The file

Show its rules and text

We split this skill into the rules it gives an agent

64 rules. 0 are common, 62 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 37 edited versions we read keep these.

  • 62

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Prefer 2-3 figures for comprehensive papers (methods flowchart, results visualization, conceptual diagram)

    line 37
  2. Distinctive:

    Use the scientific-schematics skill to generate AI-powered publication-quality diagrams

    line 40
  3. Distinctive:

    Create publication-quality images with proper formatting

    line 50
  4. Distinctive:

    Ensure accessibility (colorblind-friendly, high contrast)

    line 52
  5. Distinctive:

    Methods Documentation: Ensure reproducibility through:

    line 98
  6. Distinctive:

    Verify all citations against original sources

    line 133
  7. Distinctive:

    Use reference management software (Zotero, Mendeley, EndNote)

    line 134
  8. Very specific:

    Create effective data visualizations that enhance comprehension.

    line 138
  9. Distinctive:

    Use consistent formatting and terminology across all display items

    line 146
  10. Distinctive:

    Follow the "one table/figure per 1000 words" guideline

    line 149
  11. Distinctive:

    Avoid duplicating information between text, tables, and figures

    line 150
  12. Very specific:

    Ensure completeness and transparency by following established reporting standards.

    line 161
  13. Distinctive:

    Use precise, unambiguous language

    line 182
  14. Distinctive:

    Use active voice when appropriate for clarity

    line 185
  15. Distinctive:

    Use consistent terminology throughout

    line 195
  16. Distinctive:

    Avoid overstating findings or implications

    line 201
  17. Distinctive:

    When starting a new section:

    line 213
  18. Distinctive:

    Use the research-lookup skill to gather relevant literature and data

    line 214
  19. Distinctive:

    Create a structured outline with bullet points marking:

    line 215
  20. Distinctive:

    Search for relevant papers using research-lookup

    line 297
  21. Distinctive:

    Create logical structure before writing

    line 304
  22. Distinctive:

    Follow author guidelines for structure, length, and format

    line 311
  23. Distinctive:

    Use precise anatomical and clinical terminology (e.g., "myocardial infarction" not "heart attack" in formal writing)

    line 329
  24. Distinctive:

    Follow standardized disease nomenclature (ICD, DSM, SNOMED-CT)

    line 330
  25. Distinctive:

    Use "patients" for clinical studies, "participants" for community-based research

    line 332
  26. Distinctive:

    Follow Human Genome Variation Society (HGVS) nomenclature for genetic variants

    line 333
  27. Distinctive:

    Use italics for gene symbols (e.g., *TP53*), regular font for proteins (e.g., p53)

    line 337
  28. Distinctive:

    Follow species-specific gene nomenclature (uppercase for human: *BRCA1*.

    line 338
  29. Distinctive:

    Use standard genetic notation (e.g., +/+, +/-, -/- for genotypes)

    line 340
  30. Distinctive:

    Follow IUPAC nomenclature for chemical compounds

    line 344
  31. Distinctive:

    Use systematic names for novel compounds, common names for well-known substances

    line 345
  32. Distinctive:

    Use terms like "bioavailability," "pharmacokinetics," "IC50" consistently with field definitions

    line 349
  33. Distinctive:

    Use binomial nomenclature for species (italicized: *Homo sapiens*)

    line 352
  34. Distinctive:

    Use consistent terminology for ecological metrics (e.g., "species richness," "Shannon diversity index")

    line 355
  35. Distinctive:

    Follow SI units consistently unless field conventions dictate otherwise

    line 359
  36. Distinctive:

    Use standard notation for physical quantities (scalars vs.

    line 360
  37. Distinctive:

    Use mathematical notation consistent with field standards (e.g., ℏ for reduced Planck constant)

    line 363
  38. Distinctive:

    Use standardized brain region nomenclature (e.g., refer to atlases like Allen Brain Atlas)

    line 366
  39. Distinctive:

    Follow conventions for neural terminology (e.g., "action potential" not "spike" in formal writing)

    line 368
  40. Distinctive:

    Use "neural activity," "neuronal firing," "brain activation" appropriately based on measurement method

    line 369
  41. Distinctive:

    Use person-first language when appropriate (e.g., "people with schizophrenia" not "schizophrenics")

    line 373
  42. Distinctive:

    Follow APA guidelines for reducing bias in language

    line 375
  43. Distinctive:

    Use "participants" rather than "subjects" for human research

    line 377
  44. Distinctive:

    Avoid over-defining terms well-known to the target audience (signals unfamiliarity with field)

    line 389
  45. Distinctive:

    Create a glossary if numerous specialized terms are unavoidable

    line 390
  46. Distinctive:

    Use the same term for the same concept throughout (don't alternate between "medication," "drug," and "pharmaceutical")

    line 393
  47. Distinctive:

    Follow a consistent system for abbreviations (decide on "PCR" or "polymerase chain reaction" after first definition)

    line 394
  48. Distinctive:

    Don't use clinical terminology for basic science (e.g., don't call mice "patients")

    line 398
  49. Distinctive:

    Avoid colloquialisms or overly general terms in place of precise field terminology

    line 399
  50. Distinctive:

    Don't import terminology from adjacent fields without ensuring proper usage

    line 400
  51. Distinctive:

    Check how terms are used in recent papers from the target journal

    line 404
  52. Distinctive:

    Use domain-specific databases and ontologies (e.g., Gene Ontology, MeSH terms)

    line 405
  53. Distinctive:

    When uncertain, cite a key reference that establishes terminology

    line 406
  54. Distinctive:

    Start with figures and tables (the core data story)

    line 436
  55. Distinctive:

    First: Create outline with bullet points using research-lookup

    line 438
  56. Distinctive:

    Write Methods (often easiest to draft first)

    line 440
  57. Distinctive:

    Write Introduction (setting up the research question)

    line 443
  58. Distinctive:

    Create Title (concise and descriptive)

    line 445
  59. Distinctive:

    Check logical flow and "red thread" throughout

    line 450
  60. Distinctive:

    Verify consistency in terminology and notation

    line 451
  61. Distinctive:

    Ensure figures/tables are self-explanatory

    line 452
  62. Distinctive:

    Verify all citations are accurate and properly formatted

    line 454
  63. Distinctive:

    Check word counts for each section

    line 455
  64. Distinctive:

    Write cover letter highlighting significance

    line 461

“Common” is measured: kept by at least 6 in 10 of the 37 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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:

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

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.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.