
Paper Writing Section
Refine individual LaTeX paper sections with a two-pass agent workflow that fixes syntax errors before compressing and polishing prose.
Overview
Paper Writing Section is an agent skill most often used in Build (also Validate scope, Ship review) that runs two-pass LaTeX section refinement with a fixed scientific-writing error checklist.
Install
npx skills add https://github.com/lingzhi227/agent-research-skills --skill paper-writing-sectionWhat is this skill?
- Pass 1 error-correction prompt with a fixed checklist (math, figures, citations, environments)
- Pass 2 compression and polish pass tied to section-specific tips
- Explicit ban on adding new citations beyond the existing .bib
- Requires closing figure/table environments and deduplicating section headers
- Syncs narrative with notes.txt, logs, and figures already in the project directory
- Fixed multi-item error checklist spanning math, figures, citations, and environments
- Two explicit refinement passes: error correction then compression and polish
Adoption & trust: 713 installs on skills.sh; 114 GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
You have draft LaTeX and experiment logs but each section still hides citation, figure, and environment errors that break compilation or peer review.
Who is it for?
Indie researchers and solo builders automating AI-Scientist-style paper writeups section-by-section inside an agent workflow.
Skip if: Builders who are not writing LaTeX research papers or who already have a final, human-edited camera-ready manuscript.
When should I use this skill?
You are refining a single LaTeX section from an AI-Scientist-style writeup and need checklist-driven error correction plus a second polish pass.
What do I get? / Deliverables
After both passes, the target section is complete without placeholders and aligned with notes, figures, and verified numerical results from your logs.
- Revised LaTeX section text for the named section
- Checklist-compliant section without placeholders
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Scientific writeups land in the build phase when turning experiments and notes into publication-ready LaTeX. The skill is procedural documentation for drafting and refining manuscript sections, not running experiments or shipping infra.
Where it fits
Tighten the methods section against notes.txt before committing to a full build sprint on remaining chapters.
Run pass one on the results section right after experiments finish logging metrics to the paper directory.
Run pass two on the introduction using section-specific tips once related sections are drafted.
Re-run the error checklist on abstract and conclusion before submitting to arXiv or a venue template.
How it compares
Use instead of one-shot “fix my paper” chat when you need repeatable, checklist-driven section refinement tied to on-disk artifacts.
Common Questions / FAQ
Who is paper-writing-section for?
Solo builders and small research teams using coding agents to polish academic LaTeX sections after experiments and figures are in the repo.
When should I use paper-writing-section?
During build/docs when drafting or revising a section; during validate/scope when tightening a methods or results slice for a preprint; and during ship/review when doing a final consistency pass before submission.
Is paper-writing-section safe to install?
It is prompt-only procedural knowledge with no bundled network or shell tools; review the Security Audits panel on this Prism page before installing any skill from the catalog.
SKILL.md
READMESKILL.md - Paper Writing Section
# Two-Pass Refinement Prompts > Extracted verbatim from AI-Scientist `perform_writeup.py`. ## Error Checklist When refining any section, check for these specific errors: - Unenclosed math symbols - Only reference figures that exist in our directory - LaTeX syntax errors - Numerical results that do not come from explicit experiments and logs - Repeatedly defined figure labels - References to papers that are not in the .bib file, DO NOT ADD ANY NEW CITATIONS! - Unnecessary verbosity or repetition, unclear text - Results or insights in the `notes.txt` that have not yet been included - Any relevant figures that have not yet been included in the text - Closing any `\begin{figure}` with a `\end{figure}` and `\begin{table}` with a `\end{table}`, etc. - Duplicate headers, e.g. duplicated `\section{Introduction}` or `\end{document}` - Unescaped symbols, e.g. `shakespeare_char` should be `shakespeare\_char` in text - Incorrect closing of environments, e.g. `</end{figure}>` instead of `\end{figure}` ## Pass 1: Error Correction ``` Great job! Now criticize and refine only the {section} that you just wrote. Make this complete in this pass, do not leave any placeholders. Pay particular attention to fixing any errors such as: [error checklist above] ``` ## Pass 2: Compression and Polish ``` Criticize and refine the {section} only. Recall the advice: {tips for this section} Make this complete in this pass, do not leave any placeholders. Pay attention to how it fits in with the rest of the paper. Identify any redundancies (e.g. repeated figures or repeated text), if there are any, decide where in the paper things should be cut. Identify where we can save space, and be more concise without weakening the message of the text. Fix any remaining errors as before: [error checklist above] ``` ## Section Generation Prompt Template For each section, use this pattern: ``` Please fill in the {section} of the writeup. Some tips are provided below: {per_section_tips[section]} Be sure to use \cite or \citet where relevant, referring to the works provided in the file. Do not cite anything that is not already in references.bib. Do not add any new entries to this. Keep the experimental results (figures and tables) only in the Results section, and make sure that any captions are filled in. In this pass, do not reference anything in later sections of the paper. Before every paragraph, please include a brief description of what you plan to write in that paragraph in a comment. ``` ## Related Work Sketch (before citation harvesting) ``` Please fill in the Related Work of the writeup. Some tips are provided below: {per_section_tips["Related Work"]} For this section, very briefly sketch out the structure of the section, and clearly indicate what papers you intend to include. Do this all in LaTeX comments using %. The related work should be concise, only plan to discuss the most relevant work. Do not modify references.bib to add any new citations, this will be filled in at a later stage. ``` # Per-Section Writing Tips > Extracted verbatim from AI-Scientist (`perform_writeup.py`) and AgentLaboratory (`papersolver.py`). ## Abstract - TL;DR of the paper - What are we trying to do and why is it relevant? - Why is this hard? - How do we solve it (i.e. our contribution!) - How do we verify that we solved it (e.g. Experiments and results) - This must only be a single paragraph, not more. - Please make sure the abstract reads smoothly and is well-motivated. This should be one continuous paragraph with no breaks between the lines. ## Introduction - Longer version of the Abstract, i.e. of the entire paper - What are we trying to do and why is it relevant? - Why is this hard? - How do we solve it (i.e. our contribution!) - How do we verify that we solved it (e.g. Experiments and results) - New trend: specifically list your contributions as bullet points - Extra space? Future work! ## Related Work - Academic siblings of our work, i.e. alternative attempt