agentsclimarketplace

Write paper

Skill VincenzoImp/academic-research-skills/skills/write-paper

Use when starting or writing a paper for a venue — venue selection, framing, contribution selection, and the full manuscript on the venue template.From its SKILL.md

Install
npx -y skills add VincenzoImp/academic-research-skills --skill write-paper

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its file declares

Copied from the file, not written here

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

2.9 KB, 659 tokens by cl100k_base, as published. Nobody here has run it

Write Paper

Build papers/<slug>/: a venue-specific paper assembled from the survey and the contribution reports. The survey supplies related work; the reports supply technical content; the root references.bib supplies every citation.

Read First

  • papers/README.md — the paper lifecycle contract
  • survey/survey.pdf and the reports of candidate contributions
  • references/writing-rules.md, references/venue-fit.md

Procedure

  1. Venue. If not fixed, compare candidates with the user using references/venue-fit.md. Fill venue.md: venue, track, deadlines, page/format rules, anonymization policy, template source, and the venue's specific badge/artifact requirements — from the real call for papers, never from memory.
  2. Framing. Write framing.md: the story, the claims, which contributions support which claim and what each provides, and what is deliberately out of scope. Every claim must map to a contribution or to survey-grounded evidence.
  3. Template. Import the venue's official LaTeX template into manuscript/; rename the entry point to main.tex. Use the bib system the venue class dictates (bibtex/natbib or biblatex), reading the root references.bib via relative path. The base manuscript defaults to numeric (biblatex); the venue class sets the final style. The same root references.bib is shared with the survey (author-year) — bibliography style is per-document, not per-entry; contribution reports stay numeric.
  4. Write. Section by section: related work distilled from the survey (theme-first, never paper-by-paper); methods/results from the contribution reports and their figures; every \cite{} resolves in the root .bib. Follow references/writing-rules.md.
  5. Build and check. make paper P=<slug>, verify page limits and format rules from venue.md, run make check.
  6. Recommend an adversarial-review pass before any submission.

External Mode (Overleaf)

When the user asks to work on an external LaTeX project (e.g. a collaborator's Overleaf), use the overleaf MCP if configured: read or contribute to that project directly. Nothing in this scaffold depends on the external project; treat it as a foreign workspace, and apply references/writing-rules.md there too.

Rules

  • A claim enters the manuscript only with its evidence: a contribution, a survey-grounded citation, or an explicitly labeled open question.
  • Never invent or restyle bibliography entries; a missing entry means missing SOTA work — stop and report.
  • Figures come from contribution folders; copy them in, never recreate data by hand.

Done When

  • venue.md and framing.md complete, the manuscript builds clean on the venue template within its limits, make check passes

What ships with it: 2 files

1.4 KB alongside SKILL.md

references/

Gives 0 of the 12 instructions most docs writing skills give in 659 tokens

Counted across 1,637 of the 3,044 authors here whose files we hold, read 2026-08-07

  • Announce the skill at startin 54 of 1637, across 26 files
  • Convert legacy doc files before editingin 45 of 1637, across 7 files
  • Predict questions readers might askin 42 of 1637, across 4 files
  • Generate clarifying questions for initial contextin 42 of 1637, across 3 files
  • Create document scaffold with placeholder textin 42 of 1637, across 3 files
  • Brainstorm content options for each sectionin 42 of 1637, across 3 files
  • Test the document with a fresh context-less instancein 42 of 1637, across 3 files
  • Include exact file paths in every taskin 42 of 1637, across 15 files
  • Ask interview questions one at a timein 42 of 1637, across 27 files
  • Apply surgical edits during refinementin 41 of 1637, across 2 files
  • Offer structured workflow or freeformin 40 of 1637, across 1 file
  • Ask for document meta-contextin 40 of 1637, across 2 files

Said here and by no other author read

  • compare venue candidates using venue-fit references
  • fill venue details from the real call for papers
  • import the venue official LaTeX template
  • write related work theme-first
  • copy figures from contribution folders
  • run the paper build command

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 326,499. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.