paper-authoring

Draft LaTeX papers from Chronicle experiment records and attach compiled snapshots.

1|1|Updated May 9, 2026
One-click install
npx skills add https://github.com/methodic-research/skills --skill paper-authoring-methodic-research
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: paper-authoring
Source: https://github.com/methodic-research/skills/tree/main/research-plugin/skills/paper-authoring
Command: npx skills add https://github.com/methodic-research/skills --skill paper-authoring-methodic-research

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a finished experiment into a publication-ready paper usually means manually reassembling results, figures, citations, and negative findings scattered across reports — and then losing track of which paper version corresponds to which experimental record. This Skill authors the LaTeX paper directly from the approved Chronicle experiment record and attaches each revision as a compiled, recorded snapshot on the experiment. ## Core Features & Use Cases - Record-grounded drafting: Gathers approved takeaways and variation reports, figure assets (PDF/SVG renditions), lessons, and registered citations via the chronicle MCP tools so every number and \cite in the paper traces to the record. - Local LaTeX authoring: Writes the paper in the researcher's own working tree and template, with figure asset IDs annotated in comments for provenance and negative results stated plainly. - Snapshot attach and compile: Uploads the source as a latex_source asset and calls POST /v1/experiments/{id}/papers so Chronicle compiles it into an imported_report; re-attaching on meaningful revisions keeps a versioned record. - Use Case: After approving a takeaways report, ask the agent to draft the paper — it pulls the approved reports and figures, writes main.tex with a bibliography mapped to registered publications, attaches the source for server-side compilation, and reports the citation ledger. ## Quick Start Draft a LaTeX paper from experiment <id> using my current directory as the working tree and attach it to the experiment record.

Frequently Asked Questions about paper-authoring

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I turn a Chronicle experiment into a LaTeX paper?▼

Invoke the skill with the experiment ID; it gathers the approved takeaways and variation reports, figure assets, lessons, and registered citations, then writes the LaTeX locally in your working tree. With your approval it attaches the source via POST /v1/experiments/{id}/papers for server-side compilation.

How do I attach a paper draft to a Chronicle experiment?▼

Zip the paper directory, upload it with chronicle.upload_asset as asset_type latex_source, then call POST /v1/experiments/{id}/papers with the source_asset_id and main_file. Chronicle compiles it asynchronously into an imported_report linked to the experiment.

Can I publish the paper to Overleaf or arXiv?▼

Yes, but publishing happens outside Chronicle. Overleaf is treated as a git remote you own — push your working tree with plain git using your own credentials. Chronicle only holds the compiled record of each attached snapshot.

What happens if the takeaways report is still pending review?▼

The skill warns that the paper would lean on an unapproved draft and suggests running evaluate-results or chronicle-distill first. You can still choose to draft from the raw record, and the warning is repeated after completion.

Why did my paper attach fail to compile?▼

A compile failure leaves the asset abandoned with a compile_error. Surface the log tail, fix the LaTeX source, and re-attach — each retry is a fresh recorded snapshot rather than a mutation of the failed one.

Do I need a local LaTeX installation to use this skill?▼

No, a local LaTeX toolchain is optional because Chronicle compiles the attached source server-side via chronicle-tex. A local install is only handy for preview iterations while drafting.