Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →catlog22/scholar-writing
End-to-end academic paper writing workflow. Takes a research repository and produces a publication-ready LaTeX manuscript for top ML/AI conferences (NeurIPS, ICML, ICLR, ACL, AAAI, COLM). Covers repo understanding, structure planning, section drafting, citation management, anti-AI polishing, and conference formatting.
Passed 10 of 15 test cases with the skill, and 6 of 15 without it.
and 8 more in the full report
9 fixed5 passed either way4 still failing4 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 8 test cases the skill fixed. Same model, same prompt, with and without the skill.
After aggressive context compression on a sentinel-marked phase, only the compact sentinel marker remains in memory. What immediate step must be taken before continuing execution?
| Checked | Without skill | With skill |
|---|---|---|
| Instructs calling `Read()` on the phase document immediately to recover context before proceeding. | Missed | Passed |
The instructions your model reads when the skill loads.
<required_reading> @~/.maestro/workflows/run-mode.md </required_reading>
End-to-end workflow for writing publication-ready ML/AI papers from research repositories. Integrates paper writing craft, citation verification, and anti-AI polishing into a structured 6-phase pipeline.
Follow ~/.maestro/workflows/run-mode.md. If an orchestrator injected run_id / run_dir in the birth packet, use them and do NOT call maestro run create. Otherwise self-start before Phase 1:
maestro run create scholar-writing --session <YYYYMMDD-scholar-writing-{topic}> --intent "<short phrase>"
Session slug is ASCII-only, ≤64 chars. The paper itself lives in the user's outputDir (a working area in the user's repo, like source code — not the Run truth source). Write the workflow synthesis and the delivery manifest (paths to paper.tex / paper.pdf / references.bib, verification status, remaining action items) to {run_dir}/report.md, and the machine-readable delivery-paths list to {run_dir}/outputs/delivery.json — the contract registers it as the primary artifact latest-paper-delivery, and the runtime only scans {run_dir}/outputs/, so a manifest written anywhere else is invisible. Close per the Final Checklist.
{ "paper_tex": "", "paper_pdf": "", "references_bib": "", "sections": [], "verified": false, "open_items": [] }
.workflow/codebase/ARCHITECTURE.md exists, read for project contextmaestro load --type spec --category coding — load coding conventionsmaestro search "academic writing research paper" --json — top 5 entries as prior contextUser: "Write a paper from this repo"
|
v
┌──────────────────────────────────────────────────────────────────────┐
│ SKILL.md (Orchestrator) │
│ Collect preferences → Dispatch phases → Track progress │
└──────────┬───────────────────────────────────────────────────────────┘
|
test cases passed, vs 6 / 15 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.