Menu

Individual skill

ape-write-paper

0upvotes

Writes a polished, standard two-column research paper (LaTeX to PDF) from any source material -- code, docs, experiment logs, benchmark files, notes -- optimising for correctness, readability, structure, figures, tables and references. Supports both standalone papers and conference templates (ACM SIGMOD/VLDB, IEEE, NeurIPS). Audits every claim against evidence before writing, reports losses honestly, and renders pages to check them. Trigger on "ape write paper", "write a paper from this", "turn these experiments into a paper", or "draft the paper for this project".

ape-write-paper/SKILL.md

Read pinned source

Source commit db7ad939cc944eb71f61790a72b9a0d79008d226

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
No
Observed behavior
Not checked yet
Last checked
Nov 11, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
57
Repository last updated
Oct 24, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Write Paper Skill

Turns a pile of source material (repo, docs, experiment logs, result JSONs, notes) into a conference-style paper and a compiled PDF. The goal is a paper a skeptical reviewer can follow in one pass and check number by number.

Priorities, in order: **correct, then clear, then polished.** A beautiful paper with one invented number is worse than a plain one with none.

## Workflow

Run these phases in order. Do not start writing prose before phase 2 is done.

### 1. Gather and obey constraints

- Read every project instruction file first (`AGENTS.md`, `CLAUDE.md`, venue notes). Typical rules: target conference, approved title, author identity, layout, forbidden claims, which results may appear. They override this skill.
- **Venue template check**: If a specific conference or journal is targeted (e.g., ACM SIGMOD/VLDB requires `acmart`; IEEE requires `IEEEtran`; NeurIPS/ICML/ACL require their `.sty` packages), use the official conference documentclass and native metadata commands (`\begin{CCSXML}`, `\keywords`, `\author{...}\affiliation{...}`) rather than the standalone title block from `reference/preamble.tex`. See `reference/snippets.md` for the ACM `acmart` skeleton.
Back to top