paper-orchestra
Orchestrate the full PaperOrchestra (Song et al., 2026, arXiv:2604.05018) five-agent pipeline to turn unstructured research materials (idea, experimental log, LaTeX template, conference guidelines, optional figures) into a submission-ready LaTeX manuscript and compiled PDF. TRIGGER when the user asks to "write a paper from my experiments", "turn this idea and these results into a paper", "generate a conference submission", "run paper-orchestra on X", or otherwise wants the end-to-end paper-writing pipeline. Coordinates the outline-agent, plotting-agent, literature-review-agent, section-writing
npx skills add Ar9av/PaperOrchestra --skill paper-orchestra --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# paper-orchestra (Orchestrator) Top-level driver for the PaperOrchestra pipeline. Read this document and follow the steps below. The detailed prompts and rules live in each sub-skill's `SKILL.md` and `references/` directories — you (the host agent) will load them as you go. > Source paper: Song et al., *PaperOrchestra: A Multi-Agent Framework for > Automated AI Research Paper Writing*, arXiv:2604.05018, 2026. > <https://arxiv.org/pdf/2604.05018> ## What this skill produces A complete submission package `P = (paper.tex, paper.pdf)` written into `workspace/final/`, plus a full audit trail under `workspace/` (outline, figures, refs, drafts, refinement worklog, provenance snapshot). ## Inputs (the (I, E, T, G, F) tuple from the paper) The workspace MUST contain: | File | Symbol | Required | Description | |---|---|---|---| | `workspace/inputs/idea.md` | `I` | yes | Idea Summary (Sparse or Dense variant — see `references/io-contract.md`) | | `workspace/inputs/experimental_log.md` | `E` | yes | Experimental Log: setup, raw numeric data, qualitative observations | | `workspace/inputs/template.tex` | `T` | yes | LaTeX template for the target conference (with `\section{...}` commands) | | `
- What this skill produces
- Inputs (the (I, E, T, G, F) tuple from the paper)
- Pipeline (read references/pipeline.md for the full diagram)
- Critical pre-instruction (read once, apply always)
- Step-by-step execution
- 0. Pre-flight Checks
- 1. Outline (Step 1 — 1 LLM call)
- 2 ∥ 3. Plotting and Literature Review (in parallel)
- 3.5. Outline Reconciliation (after Step 3 completes, before Step 4)
- 4. Section Writing (Step 4 — ONE single multimodal LLM call)
- 5. Content Refinement (Step 5 — ~3 iterations, ~5-7 calls)
- 6. Compile and finalize
- Workspace layout
- Cost budget (from paper App. B)
python skills/paper-orchestra/scripts/init_workspace.py --out workspace/ user drops their inputs into workspace/inputs/ python skills/paper-orchestra/scripts/validate_inputs.py --workspace workspace/ python skills/paper-orchestra/scripts/check_idea_density.py \ python skills/paper-orchestra/scripts/validate_consistency.py \ python skills/paper-orchestra/scripts/check_tex_packages.py \ python skills/outline-agent/scripts/validate_outline.py workspace/outline_reconciled.json python skills/paper-orchestra/scripts/diff_outlines.py \ python skills/section-writing-agent/scripts/orphan_cite_gate.py workspace/drafts/paper.tex workspace/refs.bib python skills/section-writing-agent/scripts/latex_sanity.py workspace/drafts/paper.tex
What does the paper-orchestra skill do?
Orchestrate the full PaperOrchestra (Song et al., 2026, arXiv:2604.05018) five-agent pipeline to turn unstructured research materials (idea, experimental log, LaTeX template, conference guidelines, optional figures) into a submission-ready LaTeX manuscript and compiled PDF. TRIGGER when the user asks to "write a paper from my experiments", "turn this idea and these results into a paper", "generate a conference submission", "run paper-orchestra on X", or otherwise wants the end-to-end paper-writing pipeline. Coordinates the outline-agent, plotting-agent, literature-review-agent, section-writing
How do I install it?
Run `npx skills add Ar9av/PaperOrchestra --skill paper-orchestra --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From Ar9av/PaperOrchestra, a repository with 627 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.