chronicle-write-report

Attaches Markdown research write-ups with LaTeX math and figures to Chronicle experiments.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires methodic-research, wandb.

What problem does it solve? Research findings often live in scattered notes or chat logs, disconnected from the experiments that produced them, and negative results get lost entirely. This Skill attaches a structured, searchable write-up — Markdown with LaTeX math and embedded figures — directly to a Chronicle experiment or variation, with a mandatory "What didn't work" section so failed approaches stay on the record. ## Core Features & Use Cases - Structured report authoring: Drafts a write-up with required sections (Summary, What worked, What didn't work, Open questions, Figures) rendered inline in the Methodic UI with MathJax. - Figure asset management: Uploads vector plots as grouped SVG/PNG/PDF assets and interactive HTML diagrams, embedding them by asset id so each surface (browser, Overleaf, Slack) gets the right format. - Citations and findings: Registers DOI/arXiv publications as citation links on the experiment and records a structured per-variation finding (working / partial / not_working) that feeds the experiment's running summary. - Use Case: After a training run finishes, ask the agent to pull the real metrics from W&B, render a loss curve, and attach a takeaways report to the experiment — complete with the ablations that regressed and citations to the baseline papers. ## Quick Start Ask the agent to write up the findings from the latest variation of the current experiment and attach the report with its loss-curve figure to the Chronicle experiment.

Frequently Asked Questions about chronicle-write-report

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

FAQPage Schema
How do I attach a research report to a Chronicle experiment?▼

Provide the experiment id, a title, and the report kind (research_report or takeaways_report). The agent drafts the Markdown body with the required sections, uploads figures as assets, and persists the report via create_inline so it renders inline in the Methodic UI.

How do I embed figures in a Chronicle report?▼

Save vector plots in three formats sharing one filename stem (.svg, .png, .pdf) and pass the paths as the figures input. They group into a single image asset, and you embed it in the body with ![alt](asset:<id>); raster figures upload as .png only.

Can I pull real training metrics from W&B into the write-up?▼

Yes. The skill reads the run's wandb_run pointer from Chronicle, then fetches summary and history directly from W&B using your own WANDB_API_KEY environment variable. No chronicle-server W&B key is needed.

Why is the What didn't work section required in the report?▼

Negative results are part of the experiment record so future work does not re-run failed approaches. If there genuinely are none, the section must state that explicitly rather than being omitted.

What permissions are needed to write a report on an experiment?▼

You need Write access on the experiment; a 403 from create_inline or create_with_presigned means the caller lacks it. Citation links are exempt from the input commit freeze and work on committed experiments.

When should I use a compiled PDF report instead of the inline write-up?▼

Use exp.reports.<kind>.render for the formal compiled PDF artifact when one is needed. The inline Markdown report is the lightweight in-app read; the two coexist, with the PDF remaining the canonical full artifact.