Ar9av/PaperOrchestra / skills/section-writing-agent
section-writing-agent
VerifiedStep 4 of the PaperOrchestra pipeline (arXiv:2604.05018). ONE single multimodal LLM call that drafts the remaining paper sections (Abstract, Methodology, Experiments, Conclusion), extracts numeric values from experimental_log.md into LaTeX booktabs tables, splices the generated figures from Step 2, and merges everything into the template that already contains Intro + Related Work from Step 3. TRIGGER when the orchestrator delegates Step 4 or when the user asks to "write the methodology and experiments sections" or "fill in the rest of the paper".
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 12.9 KB |
| references/figure-integration.md | markdown | 3.5 KB |
| references/latex-table-patterns.md | markdown | 7.1 KB |
| references/prompt.md | markdown | 5.3 KB |
| scripts/extract_metrics.py | script | 3.8 KB |
| scripts/latex_sanity.py | script | 3.9 KB |
| scripts/orphan_cite_gate.py | script | 1.9 KB |
| scripts/table_lint.py | script | 7.2 KB |
| scripts/test_table_lint.py | script | 4.1 KB |
references/figure-integration.md
View on GitHub# Figure Integration
Conventions for including figures in the LaTeX paper, per the Section
Writing Agent prompt (App. F.1 p.48, item 5 "Figures and Visual Fidelity").
## Where the figures live
After Step 2 (Plotting Agent), figures are at:
```
workspace/figures/
├── fig_framework_overview.png
├── fig_main_results.png
├── fig_ablation_temperature.png
└── captions.json
```
The Section Writing Agent must reference them with the exact filenames,
including the `.png` extension:
```latex
\begin{figure}[t]
\centering
\includegraphics[width=0.95\linewidth]{figures/fig_framework_overview.png}
\caption{Overview of the proposed pipeline. Raw video frames flow into the
frozen SAM encoder; aligned audio cues are projected through the temporal
modality fusion layer before being injected into the mask decoder.}
\label{fig:framework_overview}
\end{figure}
```
## Single-column vs full-width
The prompt is explicit: in 2-column conference templates, prefer
`\begin{figure}` (single-column) unless the figure is very wide. Use
`\begin{figure*}` only for cross-column figures.
| Figure aspect ratio | Recommended environment |
|---|---|
| `1:1`, `2:3`, `3:2`, `3:4`, `4:3`, `4:5`, `5:4` | `figure` (single column) |
| `16:9`, `21:9`, `4:1` | `figure*` (cross column) |
| `9:16`, `1:4` | `figure` (very tall, hangs over multiple text lines) |
## Caption placement
For figures, `\caption` goes **AFTER** `\includegraphics`:
```latex
\begin{figure}[t]
\centering
\includegraphics[width=0.95\linewidth]{figures/fig_main_results.png}
\caption{Comparison of three temporal-attention variants on the Ref-AVS
Seen split. Bars show Jaccard index; error bars are 95% confidence
intervals over five seeds.}
\label{fig:main_results}
\end{figure}
```
(For tables, `\caption` goes BEFORE `\begin{tabular}`. Different
conventions; both correct in their respective contexts.)
## Caption text
- Pull from `workspace/figures/captions.json` keyed by `figure_id`.
- Do **not** include `Figure N:` in the caption text. LaTeX adds the prefix
via `\caption`.
- Plain text only. No markdown bold/italic.
- 1-3 sentences. State what the figure shows AND why (the takeaway).
## Reference in prose
Every figure must be referenced in the prose:
```latex
As shown in Figure~\ref{fig:main_results}, our method outperforms both
baselines across all five splits.
```
Use `~` (non-breaking space) before `\ref{...}`. Use `Figure` capitalized
when starting a sentence; lowercase `figure` mid-sentence.
## DO NOT merge figures
The prompt forbids combining multiple figures into one display. Each
`figure_id` from the outline corresponds to exactly one `\begin{figure}`
environment.
## All figures before Conclusion
Per the prompt: "all figures must appear before the Conclusion section,
unless they are placed in an Appendix." If you have a figure that
contextually belongs in the Appendix, move it there explicitly — do not
leave it floating after the Conclusion in the main body.
## Multi-panel figures
If a figure has multiple panels (a, b, c) — e.g., a 1×3 grid showing
ablations across three settings — the panels are part of the **same** PNG
file (rendered by Step 2). Use a single `\includegraphics` and reference
sub-panels in the caption text:
```latex
\caption{Ablation study. (a) Effect of temperature. (b) Effect of dropout.
(c) Effect of layer count. Bars show validation accuracy on the Seen split.}
```
If you really need separate sub-figure environments (`subcaption` package),
that's allowed but adds complexity — prefer single-PNG multi-panel from
Step 2.
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 |