How do I install the Scientist Writeup skill?

Run npx skillmds@latest add ldm2060/scientist-writeup in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Scientist Writeup safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Scientist Writeup?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Scientist Writeup free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Scientist Writeup?

ldm2060 (@ldm2060) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Scientist Writeup by ldm2060 — Agent Skill

Name: Scientist Writeup
Author: ldm2060

Scientist Writeup

Use when the user asks to '开始写论文', '生成 PDF', '整理成论文', or wants LaTeX / Markdown drafted directly in Copilot from experiment artifacts. Triggers on: 'write the paper', 'generate PDF', 'compile to paper'. Copilot-native — no workspace writeup script call. Do NOT use for review (scientist-review) or plotting (scientist-plotting).

ldm2060 b5f7488 2 files · 2.9 KB Updated Sep 17, 2026

File contents

scientist-writeup

Generate or edit LaTeX / Markdown paper content directly from an existing experiment directory. Model output is produced by Copilot in-session; NEVER call workspace-custom model scripts.

Execution model

This is a Copilot-native model task. Copilot reads results, writes content, and edits LaTeX files; the terminal handles non-model commands like pdflatex.

Workflow

Read the experiment directory, summary files, figures, and logs.
Identify the user-supplied latex/template.tex or the existing draft.
Write or edit paper content directly in the editor.
On user request, run pdflatex / bibtex for a compilation check.
Report the produced manuscript path, compilation result, and remaining gaps.

Verification before declaring completion

Before claiming the paper is drafted, you MUST produce one of:

the file path + a short verbatim quote of new content,
a Read confirmation that the new content is in the file,
a successful pdflatex exit and the produced PDF path,
or an explicit "drafted but could not verify — here is what I have so far."

A turn that ends with "the paper is drafted" without one of the above is a failure mode.

Input

folder: experiment directory
folder/latex/template.tex: user-provided template entry
Figures, summarized results, citation info, and target-layout requirements

Output

Edited LaTeX / Markdown files
Compiled PDF path (if compilation was run)
List of unmet prerequisites

Operating principles

Confirm the template and dependency files exist before writing.
Write from real experimental results; NEVER fabricate conclusions or citations.
When the user only wants a text draft, do not force a PDF compile.

Forbidden

NEVER call any workspace-custom writeup model pipeline.
NEVER use custom model calls in workspace code to generate paper text.

Deliverable requirements

Name which paper files were edited.
If compilation fails, return the real LaTeX error summary.
If conclusions still lack experimental support, name the missing results explicitly.

---name: scientist-writeupdescription: Use when the user asks to '开始写论文', '生成 PDF', '整理成论文', or wants LaTeX / Markdown drafted directly in Copilot from experiment artifacts. Triggers on: 'write the paper', 'generate PDF', 'compile to paper'. Copilot-native — no workspace writeup script call. Do NOT use for review (scientist-review) or plotting (scientist-plotting).---# scientist-writeupGenerate or edit LaTeX / Markdown paper content directly from an existing experiment directory. Model output is produced by Copilot in-session; NEVER call workspace-custom model scripts.## Execution modelThis is a **Copilot-native model task**. Copilot reads results, writes content, and edits LaTeX files; the terminal handles non-model commands like `pdflatex`.## Workflow1. Read the experiment directory, summary files, figures, and logs.2. Identify the user-supplied `latex/template.tex` or the existing draft.3. Write or edit paper content directly in the editor.4. On user request, run `pdflatex` / `bibtex` for a compilation check.5. Report the produced manuscript path, compilation result, and remaining gaps.## Verification before declaring completion**Before claiming the paper is drafted, you MUST produce one of:**- the file path + a short verbatim quote of new content,- a `Read` confirmation that the new content is in the file,- a successful `pdflatex` exit and the produced PDF path,- or an explicit "drafted but could not verify — here is what I have so far."A turn that ends with "the paper is drafted" without one of the above is a failure mode.## Input- `folder`: experiment directory- `folder/latex/template.tex`: user-provided template entry- Figures, summarized results, citation info, and target-layout requirements## Output- Edited LaTeX / Markdown files- Compiled PDF path (if compilation was run)- List of unmet prerequisites## Operating principles1. Confirm the template and dependency files exist before writing.2. Write from real experimental results; NEVER fabricate conclusions or citations.3. When the user only wants a text draft, do not force a PDF compile.## Forbidden- NEVER call any workspace-custom writeup model pipeline.- NEVER use custom model calls in workspace code to generate paper text.## Deliverable requirements- Name which paper files were edited.- If compilation fails, return the real LaTeX error summary.- If conclusions still lack experimental support, name the missing results explicitly.

Frequently asked questions