Ar9av/PaperOrchestra / skills/paper-orchestra
paper-orchestra
VerifiedOrchestrate 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-agent, and content-refinement-agent skills.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 13.8 KB |
| references/anti-leakage-prompt.md | markdown | 2.5 KB |
| references/host-integration.md | markdown | 7.8 KB |
| references/io-contract.md | markdown | 7.1 KB |
| references/outline-reconciliation.md | markdown | 4.7 KB |
| references/paper-summary.md | markdown | 4.1 KB |
| references/pipeline.md | markdown | 7.2 KB |
| scripts/anti_leakage_check.py | script | 3.3 KB |
| scripts/build_pdf.py | script | 28.3 KB |
| scripts/check_idea_density.py | script | 5.6 KB |
| scripts/check_tex_packages.py | script | 5.9 KB |
| scripts/claim_evidence_gate.py | script | 16.1 KB |
| scripts/diff_outlines.py | script | 3.5 KB |
| scripts/init_workspace.py | script | 4.5 KB |
| scripts/test_claim_evidence_gate.py | script | 5.1 KB |
| scripts/validate_consistency.py | script | 9.7 KB |
| scripts/validate_inputs.py | script | 4.8 KB |
scripts/diff_outlines.py
View on GitHub#!/usr/bin/env python3
"""
diff_outlines.py — Produce a human-readable summary of changes between
outline.json (Step 1) and outline_reconciled.json (Step 3.5).
Only diffs the `section_plan` array; ignores `plotting_plan` and
`intro_related_work_plan` (those are not permitted to change).
Exit codes:
0 identical section_plans (nothing was reconciled)
1 differences found (summary written to --summary)
2 input error
Usage:
python diff_outlines.py \\
--original workspace/outline.json \\
--reconciled workspace/outline_reconciled.json \\
--summary workspace/reconciliation_summary.md
"""
import argparse
import json
import os
import sys
from difflib import unified_diff
def load(path: str) -> dict:
try:
with open(path) as f:
return json.load(f)
except (FileNotFoundError, json.JSONDecodeError) as e:
print(f"ERROR: {path}: {e}", file=sys.stderr)
sys.exit(2)
def section_text(plan: list) -> str:
lines = []
for sec in plan:
lines.append(f"## {sec.get('title', '(untitled)')}")
for sub in sec.get("subsections", []):
lines.append(f" ### {sub}")
for bullet in sec.get("content_bullets", []):
lines.append(f" - {bullet}")
lines.append("")
return "\n".join(lines)
def main() -> int:
p = argparse.ArgumentParser(description=__doc__)
p.add_argument("--original", required=True)
p.add_argument("--reconciled", required=True)
p.add_argument("--summary", required=True)
args = p.parse_args()
orig = load(args.original)
recon = load(args.reconciled)
orig_text = section_text(orig.get("section_plan", []))
recon_text = section_text(recon.get("section_plan", []))
if orig_text == recon_text:
print("OK: section_plan unchanged — nothing to reconcile.")
# Write empty summary
os.makedirs(os.path.dirname(os.path.abspath(args.summary)) or ".", exist_ok=True)
with open(args.summary, "w") as f:
f.write("# Outline Reconciliation Summary\n\nNo changes — "
"section_plan is identical to original outline.\n")
return 0
diff_lines = list(unified_diff(
orig_text.splitlines(keepends=True),
recon_text.splitlines(keepends=True),
fromfile="outline.json (original)",
tofile="outline_reconciled.json",
lineterm="",
))
# Count sections that contain any changed lines
# Track current section as we walk the diff; mark it when a +/- appears
changed_sections: set[str] = set()
current_section = "(unknown)"
for line in diff_lines:
stripped = line.rstrip("\n")
# Context or changed section-header lines
if stripped.startswith((" ##", "+##", "-##", " ##")):
current_section = stripped.lstrip("+-").strip()
elif stripped.startswith(("+", "-")) and not stripped.startswith(("+++", "---")):
changed_sections.add(current_section)
summary_lines = [
"# Outline Reconciliation Summary",
"",
f"**Changed sections:** {len(changed_sections)}",
"",
"## Diff (section_plan only)",
"",
"```diff",
] + diff_lines + ["```", ""]
os.makedirs(os.path.dirname(os.path.abspath(args.summary)) or ".", exist_ok=True)
with open(args.summary, "w") as f:
f.write("\n".join(summary_lines))
print(f"Reconciliation summary written to {args.summary}")
print(f" {len(changed_sections)} section(s) changed")
return 1
if __name__ == "__main__":
sys.exit(main())
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deployment | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |