scientific-writing
starsforks
How to install scientific-writing?
leonchaox/qinyan-academic-skills/scientific-writing
$npx -y skills add LeonChaoX/qinyan-academic-skills --skill scientific-writingCore 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/V
SKILL.md
| 1 | # Scientific Writing |
| 2 | |
| 3 | ## Overview |
| 4 | |
| 5 | **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. |
| 6 | |
| 7 | 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. |
| 8 | |
| 9 | **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. |
| 10 | |
| 11 | ## When to Use This Skill |
| 12 | |
| 13 | This skill should be used when: |
| 14 | - Writing or revising any section of a scientific manuscript (abstract, introduction, methods, results, discussion) |
| 15 | - Structuring a research paper using IMRAD or other standard formats |
| 16 | - Formatting citations and references in specific styles (APA, AMA, Vancouver, Chicago, IEEE) |
| 17 | - Creating, formatting, or improving figures, tables, and data visualizations |
| 18 | - Applying study-specific reporting guidelines (CONSORT for trials, STROBE for observational studies, PRISMA for reviews) |
| 19 | - Drafting abstracts that meet journal requirements (structured or unstructured) |
| 20 | - Preparing manuscripts for submission to specific journals |
| 21 | - Improving writing clarity, conciseness, and precision |
| 22 | - Ensuring proper use of field-specific terminology and nomenclature |
| 23 | - Addressing reviewer comments and revising manuscripts |
| 24 | |
| 25 | ## Visual Enhancement with Scientific Schematics |
| 26 | |
| 27 | **⚠️ MANDATORY: Every scientific paper MUST include a graphical abstract plus 1-2 additional AI-generated figures using the scientific-schematics skill.** |
| 28 | |
| 29 | This is not optional. Scientific papers without visual elements are incomplete. Before finalizing any document: |
| 30 | 1. **ALWAYS generate a graphical abstract** as the first visual element |
| 31 | 2. Generate at minimum ONE additional schematic or diagram using scientific-schematics |
| 32 | 3. Prefer 3-4 total figures for comprehensive papers (graphical abstract + methods flowchart + results visualization + conceptual diagram) |
| 33 | |
| 34 | ### Graphical Abstract (REQUIRED) |
| 35 | |
| 36 | **Every scientific writeup MUST include a graphical abstract.** This is a visual summary of your paper that: |
| 37 | - Appears before or immediately after the text abstract |
| 38 | - Captures the entire paper's key message in one image |
| 39 | - Is suitable for journal table of contents display |
| 40 | - Uses landscape orientation (typically 1200x600px) |
| 41 | |
| 42 | **Generate the graphical abstract FIRST:** |
| 43 | ```bash |
| 44 | python scripts/generate_schematic.py "Graphical abstract for [paper title]: [brief description showing workflow from input → methods → key findings → conclusions]" -o figures/graphical_abstract.png |
| 45 | ``` |
| 46 | |
| 47 | **Graphical Abstract Requirements:** |
| 48 | - **Content**: Visual summary showing workflow, key methods, main findings, and conclusions |
| 49 | - **Style**: Clean, professional, suitable for journal TOC |
| 50 | - **Elements**: Include 3-5 key steps/concepts with connecting arrows or flow |
| 51 | - **Text**: Minimal labels, large readable fonts |
| 52 | - Log: `[HH:MM:SS] GENERATED: Graphical abstract for paper summary` |
| 53 | |
| 54 | ### Additional Figures (GENERATE EXTENSIVELY) |
| 55 | |
| 56 | **⚠️ CRITICAL: Use BOTH scientific-schematics AND generate-image EXTENSIVELY throughout all documents.** |
| 57 | |
| 58 | Every document should be richly illustrated. Generate figures liberally - when in doubt, add a visual. |
| 59 | |
| 60 | **MINIMUM Figure Requirements:** |
| 61 | |
| 62 | | Document Type | Minimum | Recommended | |
| 63 | |--------------|---------|-------------| |
| 64 | | Research Papers | 5 | 6-8 | |
| 65 | | Literature Reviews | 4 | 5-7 | |
| 66 | | Market Research | 20 | 25-30 | |
| 67 | | Presentations | 1/slide | 1-2/slide | |
| 68 | | Posters | 6 | 8-10 | |
| 69 | | Grants | 4 | 5-7 | |
| 70 | | Clinical Reports | 3 | 4-6 | |
| 71 | |
| 72 | **Use scientific-schematics EXTENSIVELY for technical diagrams:** |
| 73 | ```bash |
| 74 | python scripts/generate_schematic.py "your diagram description" -o figures/output.png |
| 75 | ``` |
| 76 | |
| 77 | - Study design and methodology flowcharts (CONSORT, PRISMA, STROBE) |
| 78 | - Conceptual framework diagrams |
| 79 | - Experimental workflow illustrations |
| 80 | - Data analysis pipeline diagrams |
| 81 | - Biological pathway or mechanism diagrams |
| 82 | - System architecture visualizations |
| 83 | - Neural network architectures |
| 84 | - Decision trees, algorithm flowcharts |
| 85 | - Comparison matrices, timeline diagrams |
| 86 | - |
People who liked this also viewed
6 picksType
- find-skillsHelps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skSkillsJul 2026
- grill-meA relentless interview to sharpen a plan or design.SkillsJul 2026
- vercel-react-best-practicesVercel's official collection of agent skillsSkillsJul 2026
- improve-codebase-architectureScan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.SkillsJul 2026
- setup-matt-pocock-skillsConfigure this repo for the engineering skills — set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.SkillsJul 2026
- triageMove issues and external PRs through a state machine of triage roles — categorise, verify, grill if needed, and write agent-ready briefs.SkillsJul 2026
