scientific-writing
Core skill for the deep research and writing tool. Write scientific manuscripts in full paragraphs (never bullet points). Use two-stage process with (1) section outlines with key points using research-lookup then (2) convert to flowing prose. IMRAD structure, citations (APA/AMA/Vancouver), figures/tables, reporting guidelines (CONSORT/STROBE/PRISMA), for research papers and journal submissions.
npx skills add LeonChaoX/qinyan-academic-skills --skill scientific-writing --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
What it does
Directs the agent to produce scientific manuscripts in full, flowing paragraphs (no bullet points), following IMRAD structure and incorporating citations (APA/AMA/Vancouver), figures/tables, and reporting guidelines (CONSORT/STROBE/PRISMA). Implements a two-stage process: first create section outlines with key points via a research-lookup step, then convert those outlines into complete paragraphs.
How it works
The skill enforces a full-paragraph manuscript workflow, requiring a two-stage approach: Stage 1 uses research-lookup to gather literature and generate section outlines with key points; Stage 2 converts those bullet-point outlines into flowing prose, integrating citations within sentences and ensuring logical progression. It specifies IMRAD structure and consideration of figures/tables, and references to reporting guidelines (CONSORT/STROBE/PRISMA) as applicable. The writing should be in complete sentences and paragraphs, not bullet lists, to produce publication-ready text. It also mandates inclusion of graphical abstract and additional figures via dedicated visualization tools described in the content.
When to use it
Use when writing or revising any section of a scientific manuscript (abstract, introduction, methods, results, discussion), structuring a paper in IMRAD or similar formats, formatting citations in APA/AMA/Vancouver/Chicago/IEEE styles, creating or improving figures/tables, applying reporting guidelines (CONSORT for trials, STROBE for observational studies, PRISMA for reviews), drafting abstracts for journal requirements, preparing manuscripts for submission, improving clarity and precision, and addressing reviewer comments.
What it can touch
The skill declares tool usage including Read, Write, Edit, Bash and specifies the need to perform research-lookup and produce sections with citations, figures, and potentially graphical abstracts and additional figures using related visualization scripts. It requires interactions with external literature sources and visualization tooling to generate figures and schematics.
Caveats
The skill imposes a strict prohibition against bullet-point final manuscripts; final text must be in full paragraphs. It mandates inclusion of a graphical abstract and additional figures generated through provided visualization workflows. The approach relies on two-stage outlines and conversion to prose, with citations integrated into prose and adherence to specific reporting guidelines where applicable.
# 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) - C
- Overview
- When to Use This Skill
- Visual Enhancement with Scientific Schematics
- Graphical Abstract (REQUIRED)
- Additional Figures (GENERATE EXTENSIVELY)
- Core Capabilities
- 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. Professional Report Formatting (Non-Journal Documents)
python scripts/generate_schematic.py "your diagram description" -o figures/output.png python scripts/generate_image.py "your image description" -o figures/output.png xelatex report.tex
What does the scientific-writing skill do?
Core skill for the deep research and writing tool. Write scientific manuscripts in full paragraphs (never bullet points). Use two-stage process with (1) section outlines with key points using research-lookup then (2) convert to flowing prose. IMRAD structure, citations (APA/AMA/Vancouver), figures/tables, reporting guidelines (CONSORT/STROBE/PRISMA), for research papers and journal submissions.
How do I install it?
Run `npx skills add LeonChaoX/qinyan-academic-skills --skill scientific-writing --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From LeonChaoX/qinyan-academic-skills, a repository with 759 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.