paper-write
Skill4 starsChanged 39 days agoMITView on GitHub
Draft or revise an academic manuscript from an approved plan and verified evidence. Use for Stage 4, translation, section drafting, or LaTeX preparation.
12 other projects use a version of this.
Adopted by
Most recently taken up by
- cabbage2000-lab/paper-tutor-skillstheir own version, first seen Nov 8, 2026
- Yulivu/debuffer-skillstheir own version, first seen Oct 13, 2026
- PUNCKe/manuscript-context-integritytheir own version, first seen Sep 19, 2026
- talhaMah56/claude_skillstheir own version, first seen Sep 12, 2026
- wanshuiyin/Auto-claude-code-research-in-sleeptheir own version, first seen Jul 15, 2026
- catalsqlb-cmd/Prism-Htheir own version, first seen May 29, 2026
Used with
Projects with it also use auto-paper-improvement-loop, deepxiv and 6 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
Yusong-EnceladusSkillauto-paper-improvement-loop
Autonomously improve a generated paper via GPT-5.4 xhigh review → implement fixes → recompile, for 2 rounds. Use when user says \"改论文\", \"improve paper\", \"论文润色循环\", \"auto improve\", or wants to iteratively polish a generated paper.
Also in 5 projects that use this
raja21068Skilldeepxiv
Search and progressively read open-access academic papers through DeepXiv. Use when the user wants layered paper access, section-level reading, trending papers, or DeepXiv-backed literature retrieval.
Also in 4 projects that use this
Yusong-EnceladusSkilldse-loop
Autonomous design space exploration loop for computer architecture and EDA. Runs a program, analyzes results, tunes parameters, and iterates until objective is met or timeout. Use when user says \"DSE\", \"design space exploration\", \"sweep parameters\", \"optimize\", \"find best config\", or wants iterative parameter tuning.
Also in 4 projects that use this
raja21068Skillexperiment-bridge
Workflow 1.5: Bridge between idea discovery and auto review. Reads EXPERIMENT_PLAN.md, implements experiment code, deploys to GPU, collects initial results. Use when user says \"实现实验\", \"implement experiments\", \"bridge\", \"从计划到跑实验\", \"deploy the plan\", or has an experiment plan ready to execute.
Also in 4 projects that use this
- +4 more from raja21068
Other versions12 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 12
- wanshuiyin/Auto-claude-code-research-in-sleep★ 19ksame name
- xstongxue/best-skills★ 2.9ksame name
- cabbage2000-lab/paper-tutor-skills★ 48same name
- Chanw-research/claude-code-paper-writing★ 42same name
- catalsqlb-cmd/Prism-H★ 16same name
- Yulivu/debuffer-skills★ 9same name
- Yusong-Enceladus/claude-skills★ 8same name
- b1mango/Agent-Skills★ 4same name
- PUNCKe/manuscript-context-integrity★ 2same name
- raja21068/AutoResearch★ 2same name
2 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository19 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- academic-humanizerSkill
- citation-verificationSkill
- claim-numerics-auditSkill
- cover-letterSkill
- experiment-planSkill
- experiment-runnerSkill
- journal-scoutSkill
- paper-auditSkill
- paper-illustrationSkill
- paper-planSkill
- research-data-auditSkill
- research-ideationSkill
- research-publicationSkill
- research-quality-gateSkill
- research-refineSkill
- result-to-claimSkill
- scientific-figure-makingSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
17 rules. 0 are common, 14 are distinctive, and 3 are very specific to this project.
0
Common
Most of the 9 edited versions we read keep these.
14
Distinctive
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 22
If a central result, figure, citation, or author decision is missing, mark the exact gap and draft only the unaffected material.
- Distinctive: line 31
Language: Use the user-approved workflow.
- Very specific: line 41
Use references/doc-to-paper-mapping.md to map each planned section to Claim IDs, Evidence IDs, result artifacts, figures/tables, citations, …
- Distinctive: line 49
write connected paragraphs that establish the supported author position.
- Distinctive: line 50
keep observation, interpretation, mechanism claim, and speculation distinct.
- Distinctive: line 51
leave an explicit unresolved marker rather than completing a sentence from memory.
- Very specific: line 53
Use the section-specific references only when that section is being drafted.
- Very specific: line 64
Use stable project filenames.
- Distinctive: line 74
Before declaring Stage 4 complete:
- Distinctive: line 76
run citation and numerical audits.
- Distinctive: line 77
check every figure/table reference and source.
- Distinctive: line 80
verify terminology, notation, abstract/conclusion claims, limitations, disclosures, and venue scope.
- Distinctive: line 86
Never strengthen a claim because the prose sounds weak.
- Distinctive: line 87
Do not weaken a supported claim merely to sound cautious.
- Distinctive: line 88
Never change a number, unit, split, significance result, citation identity, or figure content without returning to its source artifact.
- Distinctive: line 89
Do not turn a method name, module list, benchmark score, or system implementation into a contribution unless the approved evidence supports …
- Distinctive: line 91
Follow current venue guidance over generic examples, historical templates, or remembered formatting rules.
“Common” is measured: kept by at least 6 in 10 of the 9 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Paper Write
Turn approved research artifacts into a coherent manuscript without changing the evidence, results, or author decisions. The default template workflow is Chinese review followed by English LaTeX, but the user or target venue may require another language or sequence.
Readiness check
Before full drafting, read AGENTS.md and the relevant analysis, paper plan, figure report, result tables, verified citations, and current venue guidance needed to establish the manuscript's evidence and structure. The template records these in docs/08_analysis.md through docs/10_figure_report.md. For a section or local prose edit, use the corresponding material and sufficient surrounding context; reuse unchanged, already-verified evidence and check only the claims or sources affected by the revision.
Confirm:
- the central claims and their maximum permissible wording;
- the numerical truth source and experiment IDs;
- the figure/table inventory, sources, and Gate E status;
- unresolved evidence, policy, author, and disclosure decisions;
- the existing LaTeX/document structure and files that must not be overwritten.
If a central result, figure, citation, or author decision is missing, mark the exact gap and draft only the unaffected material. Do not invent a bridge, number, reference, or completed experiment.
Gate E may permit initial drafting as CONDITIONAL only when scientific validity, data provenance, reproducibility, and the required checks on the figures/tables themselves pass, and the remaining checks concern consistency with prose that does not yet exist. Record the input version, each affected item, owner, permitted drafting scope, and closure trigger in the existing figure report. Close these items in the Gate E record after drafting and before Gate F passes; Gate F references valid checks rather than repeating them. Recheck only affected items when their inputs change. A material scientific unknown or fail blocks the affected drafting scope; assigning an owner does not resolve it.
Writing decisions
- Structure: Follow the approved paper plan, study design, and venue requirements. When present, read
docs/WRITING_STANDARD.mdfor the user's project-specific section order, budgets, and editorial defaults; do not impose that preference on unrelated users or automatically restructure approved manuscripts. Record actual section word/figure/table counts and justified departures in the existing paper plan. - Voice: Match the author's established voice and the venue's accepted usage. First person, plural first person, and passive voice are all conditional choices; do not enforce a universal ban.
- Author stance: Recover the intended reader judgment from the current manuscript, evidence and accepted decisions. Draft that supported proposition directly, with its actual scope and modality. Do not create an overstrong proposition and then retract it, invent weaknesses, or carry internal audit history into the prose. Read
references/writing-principles.mdfor defensive-writing calibration when drafting or substantively revising. - Language: Use the user-approved workflow. In the research template, Chinese v1/v2 review followed by English is the default, not an irreversible rule.
- Source layout: Preserve the established single-file or multi-file structure unless a confirmed venue rule or explicit user request requires migration.
- Figures: Preserve vector/raster formats, stable filenames, and source links. Copy, convert, flatten, or rename only when the submission package requires it, and re-verify the rendered manuscript afterward.
- Citations: Draft placeholders may identify unresolved citations, but the final manuscript uses only verified records whose source supports the attached claim.
- Editorial format: Apply the project's writing standard and applicable editor requirements recorded in
docs/02_journal_scouting.md. Keep titles concise, define abbreviations, separate short captions, essential reading notes, and substantive prose, and ensure the conclusion includes evidence-supported insight, application implications, and testable future work. Preserve independent figure readability and scientific scope. Check article self-reference and tense semantically; do not globally replace every occurrence ofstudyor force one tense throughout.
Workflow
1. Build the section evidence map
Use references/doc-to-paper-mapping.md to map each planned section to Claim IDs, Evidence IDs, result artifacts, figures/tables, citations, limitations, and reader questions. Resolve contradictions before prose generation.
2. Draft from evidence modules
For each section:
- identify the reader question and section claim internally;
- assemble the evidence, method details, figure/table role, and any material limitation relevant to the claim;
- write connected paragraphs that establish the supported author position; keep necessary inferential links visible without forcing each paragraph to announce its purpose or end in a caveat;
- keep observation, interpretation, mechanism claim, and speculation distinct;
- leave an explicit unresolved marker rather than completing a sentence from memory.
Use the section-specific references only when that section is being drafted. Read references/paragraph-flow.md for structural repair, references/related-work.md for positioning, and references/discussion-conclusion.md for interpretation. Examples are optional reasoning patterns; their facts, counts and suggested phrasing are not requirements for this manuscript.
3. Chinese review rounds when applicable
For the template's default workflow:
- v1: produce a complete Chinese draft for structure, argument, contribution, and evidence review.
- Round 1: incorporate the user's decisions on large issues and record unresolved evidence.
- v2: revise for terminology, paragraph logic, figure/table consistency, limitations, and venue fit.
- Round 2: incorporate detailed user review and freeze the approved content before English drafting.
Use stable project filenames; the conventional names paper/draft_cn_v1.* and paper/draft_cn_v2.* are defaults only when they do not conflict with an existing source tree.
4. English manuscript and LaTeX
Translate or draft from the approved content rather than independently rewriting the scientific story. Obtain the current official template only after the venue and version are confirmed. Preserve terminology, notation, citations, values, figures, and claim scope across languages.
Compile the actual submission source and visually inspect affected pages. A successful compiler exit does not prove that equations, tables, figures, references, or page layout are correct.
5. Integrity and handoff
Before declaring Stage 4 complete:
- run citation and numerical audits;
- check every figure/table reference and source;
- reverse-outline the manuscript to confirm each paragraph advances the approved narrative;
- reconcile the title, abstract, introduction, decisive displays and conclusion against the same Claim state; verify methods as performed, comparison classes, analysis units and uncertainty definitions;
- verify terminology, notation, abstract/conclusion claims, limitations, disclosures, and venue scope;
- record remaining
pass/warn/fail/unknownitems indocs/11_pre_submission_audit.md; - route the manuscript to
research-quality-gateGate F andpaper-audit, rather than self-certifying it inside the writing pass.
Rules
- Never strengthen a claim because the prose sounds weak.
- Do not weaken a supported claim merely to sound cautious. Preserve a possible explanation instead of rewriting it as necessary proof followed by a warning. State a given uncertainty once unless distinct conditions require separate treatment.
- Never change a number, unit, split, significance result, citation identity, or figure content without returning to its source artifact.
- Do not turn a method name, module list, benchmark score, or system implementation into a contribution unless the approved evidence supports that framing.
- Preserve real limitations where they affect interpretation; do not mechanically append limitations to every paragraph. Remove only unsupported self-defeat, repetition, or generic filler.
- Follow current venue guidance over generic examples, historical templates, or remembered formatting rules.
References
| File | Open when |
references/writing-principles.md | Framing contribution, evidence-led paragraphs, related work, limitations, and conclusion. |
references/writing-prep-checklist.md | Confirming claim, number, figure, citation, source-layout, and policy readiness before drafting. |
references/doc-to-paper-mapping.md | Mapping numbered project artifacts into the approved paper plan. |
references/abstract.md | Drafting or revising the abstract. |
references/introduction.md | Drafting or revising the introduction. |
references/method.md | Drafting or revising methods. |
references/experiments.md | Drafting setup, results, and analyses. |
references/paragraph-flow.md | Repairing paragraph function, inferential links, information order and section handoffs. |
references/related-work.md | Synthesizing closest work by scientific question and verified comparison dimensions. |
references/discussion-conclusion.md | Interpreting mixed evidence, scope, implications and the final research answer. |
references/examples/ | A concrete pattern is needed after the paper type and section purpose are known. |
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

