skills/43-wentorai-research-plugins/skills/writing/composition/scientific-writing-wrapper/SKILL.md
AI-powered scientific writing workflow from outline to polished draft
npx skillsauth add brycewang-stanford/Awesome-Agent-Skills-for-Empirical-Research scientific-writing-wrapperInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Writing a scientific paper is one of the most time-consuming parts of the research process. The Scientific Writing Wrapper skill provides a structured, AI-assisted workflow that takes you from raw research notes and results to a polished manuscript draft. It is not about generating papers from nothing—it is about using AI tools strategically to accelerate each phase of the writing process while maintaining scientific rigor and your own voice.
This skill covers the complete writing lifecycle: outlining, drafting section by section, iterative revision, and final polish. At each stage, it provides specific prompting strategies and quality checkpoints that ensure the AI output meets the standards of peer-reviewed publication. The workflow is designed to keep you in control of the scientific content while delegating the mechanical aspects of prose generation.
The approach is venue-agnostic and works for journal articles, conference papers, and technical reports across all scientific disciplines.
Before generating any prose, assemble your writing inputs:
Create a structured writing folder with the following:
manuscript/
notes/
research_question.md # Your RQ, hypotheses, and scope
key_findings.md # Bullet-point list of all results
figure_descriptions.md # Description of each figure/table and what it shows
related_work_notes.md # Notes on how your work relates to prior literature
data/
results_tables.csv # Raw data for results tables
figures/ # All figure files
references/
bibliography.bib # BibTeX file with all references
drafts/ # Generated drafts will go here
Write a detailed outline before generating any prose:
This outline is your contract with yourself about what the paper will say. AI-generated prose should fill in this structure, not change it.
Draft each section independently, working from the most concrete (Methods, Results) to the most interpretive (Discussion, Introduction).
When using an LLM to draft sections, provide rich context:
I am writing the Methods section of a paper about [topic] for [venue].
Here is my outline for this section:
[paste outline]
Here are my detailed notes:
[paste relevant notes]
Please draft this section following these guidelines:
- Use passive voice sparingly; prefer active voice
- Be precise about sample sizes, parameters, and tools
- Include enough detail for reproducibility
- Target approximately [N] words
- Use past tense for describing what was done
- Do not invent any details not present in my notes
After generating a draft of any section, review it against these criteria before moving on:
Once all sections are drafted individually, assemble them into a complete manuscript and perform an integration pass:
Use targeted revision prompts for specific improvements:
Before submitting for peer review or to a journal, verify:
tools
Recommend AND run open-source AI tools, agents, Claude Code / Codex skills, and MCP servers for any stage of a literature review — searching, reading, extracting, synthesizing, screening, citation-checking, and paper writing. Use when the user asks "what tool should I use to..." OR "install/run/use <tool> to ..." for research/lit-review work: automating a survey or related-work section, PDF→Markdown extraction for LLMs (MinerU/marker/docling), PRISMA / systematic review (ASReview), citation-backed Q&A over PDFs (PaperQA2), wiring papers into Claude/Cursor via MCP (arxiv/paper-search/zotero servers), or chatting with a Zotero library. Ships a launcher (scripts/litrun.py) that installs each tool in an isolated venv and runs it. Curated catalog of 70+ vetted projects. 支持中英文(用于「文献综述工具选型」与「一键安装/运行」)。
development
Route empirical-research requests through the Auto-Empirical Research Skills catalog when this whole repository is installed as one skill in Codex, CodeBuddy, Claude Code, or another IDE. Use to choose and load the right vendored AERS skill for causal inference, econometrics, replication, data acquisition, manuscript writing, peer review and referee responses, citation checking, de-AIGC editing, or full empirical-paper workflows without reading the entire repository at once.
documentation
Use when the project collects primary data or runs a field, lab, or survey experiment, before the intervention begins — write the pre-analysis plan, size the sample from a power calculation, and register with the AEA RCT Registry. Apply after the design is chosen in aer-identification and before any outcome data are seen.
tools
Guide economists to authoritative data sources with explicit, confirmed data specifications before retrieval; interfaces with Playwright MCP to navigate portals and extract real data, not articles about data.