Draft a LaTeX research paper from all previous stage outputs
npx skills add https://github.com/OpenRaiser/NanoResearch --skill nanoresearch-writing
Take all previous outputs (ideation, planning, experiment results) and produce a complete LaTeX paper draft with figures, tables, and bibliography.
generate_latex: Generate and assemble LaTeX source files for each paper sectioncompile_pdf: Compile the LaTeX source into a PDF documentgenerate_figure: Produce publication-quality figures from experiment resultsideation_output: Path to papers/ideation_output.json from the ideation skillexperiment_blueprint: Path to papers/experiment_blueprint.json from the planning skillexperiment_results: Path to experiments/ directory containing code and results from the experiment skillgenerate_figure10. Draft the Conclusion with a summary of findings and future work directions
11. Compile the bibliography from all cited papers
12. Assemble the full LaTeX document using generate_latex
13. Compile to PDF using compile_pdf and verify the output
Produces papers/draft/ directory containing:
main.tex: Complete LaTeX source of the paperreferences.bib: Bibliography file with all citationsfigures/: Generated figures in PDF or PNG formattables/: LaTeX table source filesmain.pdf: Compiled PDF of the paper draftSystematically evaluate scholarly work using the ScholarEval framework, providing structured assessment across research quality dimensions including problem formulation, methodology, analysis, and writing with quantitative scoring and actionable feedback.
Research-before-coding workflow. Search for existing tools, libraries, and patterns before writing custom code. Invokes the researcher agent.
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.
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.
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.
Workflow 3: Full paper writing pipeline. Orchestrates paper-plan \u2192 paper-figure \u2192 paper-write \u2192 paper-compile \u2192 auto-paper-improvement-loop to go from a narrative report to a polished, submission-ready PDF. Use when user says \\\"\u5199\u8bba\u6587\u5168\u6d41\u7a0b\\\", \\\"write paper pipeline\\\", \\\"\u4ece\u62a5\u544a\u5230PDF\\\", \\\"paper writing\\\", or wants the complete paper generation workflow.
Workflow 3: Full paper writing pipeline that goes from a narrative report to a polished, submission-ready PDF. Use when user says \"写论文全流程\", \"write paper pipeline\", \"从报告到PDF\", \"paper writing\", or wants the complete paper generation workflow.
Paragraph-level structural blueprint for 10-12 page systems papers targeting OSDI, SOSP, ASPLOS, NSDI, and EuroSys. Provides page allocation, paragraph templates, and writing patterns. Use when user says \"写系统论文\", \"systems paper structure\", \"OSDI paper\", \"SOSP paper\", or wants fine-grained structural guidance for a systems conference submission.
Take openraiser/nanoresearch-writing from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.