Ar9av/PaperOrchestra / skills/plotting-agent
plotting-agent
VerifiedStep 2 of the PaperOrchestra pipeline (arXiv:2604.05018). Execute the visualization plan from outline.json — render plots and conceptual diagrams from experimental_log.md and idea.md, optionally refine via VLM critique loop, and produce context-aware captions. Runs in parallel with the literature-review-agent. TRIGGER when the orchestrator delegates Step 2 or when the user asks to "generate the figures for my paper" or "render the plots from this experiment log".
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 9.2 KB |
| references/aspect-ratios.md | markdown | 2.0 KB |
| references/caption-prompt.md | markdown | 2.7 KB |
| references/chart-patterns.md | markdown | 6.6 KB |
| references/diagram-patterns.md | markdown | 3.9 KB |
| references/paperbanana-cookbook.md | markdown | 6.0 KB |
| references/plotting-pipeline.md | markdown | 5.8 KB |
| scripts/figure_lint.py | script | 8.1 KB |
| scripts/paperbanana_render.py | script | 12.7 KB |
| scripts/render_diagram.py | script | 4.1 KB |
| scripts/render_matplotlib.py | script | 7.1 KB |
| scripts/test_figure_lint.py | script | 6.5 KB |
references/diagram-patterns.md
View on GitHub# Conceptual Diagram Patterns
For `plot_type == "diagram"` figures: framework overviews, system pipelines,
algorithmic flows, architectural block diagrams.
The paper's Fig. 1 (PaperOrchestra overview) is a canonical example: boxes
representing agents, arrows showing data flow, grouped sub-systems with
labeled inputs and outputs.
## Tools
- **matplotlib patches** — best for hand-controlled layouts (boxes-and-arrows
with exact positioning, labels, and group rectangles). No external deps.
- **graphviz** — best for DAGs where layout doesn't matter; requires the
`graphviz` Python binding and the `dot` system binary. Use only if the
diagram is purely topological.
This skill defaults to matplotlib because it ships in `requirements.txt` and
needs no system binary.
## Block diagram pattern (boxes + arrows)
```python
import matplotlib.pyplot as plt
from matplotlib.patches import FancyBboxPatch, FancyArrowPatch
from matplotlib.lines import Line2D
# 16:9 frame
fig, ax = plt.subplots(figsize=(7.0, 3.94))
ax.set_xlim(0, 10); ax.set_ylim(0, 6)
ax.axis('off')
PALETTE = {
'input': '#cfe2f3',
'agent': '#9fc5e8',
'output': '#b6d7a8',
'control': '#ead1dc',
'border': '#2060cc',
}
def box(x, y, w, h, text, color):
bb = FancyBboxPatch((x, y), w, h, boxstyle="round,pad=0.06,rounding_size=0.15",
ec=PALETTE['border'], fc=color, lw=0.8)
ax.add_patch(bb)
ax.text(x + w/2, y + h/2, text, ha='center', va='center',
fontsize=8, fontweight='bold')
def arrow(x1, y1, x2, y2):
a = FancyArrowPatch((x1, y1), (x2, y2),
arrowstyle='->', mutation_scale=10,
color=PALETTE['border'], lw=0.9)
ax.add_patch(a)
# Inputs (left column)
box(0.2, 4.8, 1.6, 0.7, "Idea (I)", PALETTE['input'])
box(0.2, 3.6, 1.6, 0.7, "Exp Log (E)", PALETTE['input'])
box(0.2, 2.4, 1.6, 0.7, "Template (T)", PALETTE['input'])
box(0.2, 1.2, 1.6, 0.7, "Guidelines (G)", PALETTE['input'])
# Agents (middle)
box(2.6, 3.6, 1.8, 1.0, "Outline\nAgent", PALETTE['agent'])
box(5.0, 4.8, 1.8, 0.9, "Plotting\nAgent", PALETTE['agent'])
box(5.0, 3.0, 1.8, 0.9, "Lit Review\nAgent", PALETTE['agent'])
box(5.0, 1.2, 1.8, 0.9, "Section\nWriter", PALETTE['agent'])
box(7.5, 2.4, 2.0, 1.6, "Refinement\nAgent", PALETTE['control'])
# Output
box(7.5, 0.4, 2.0, 0.9, "paper.tex\n+ paper.pdf", PALETTE['output'])
# Arrows
for y_in in (5.15, 3.95, 2.75, 1.55):
arrow(1.8, y_in, 2.6, 4.1)
arrow(4.4, 4.1, 5.0, 5.25)
arrow(4.4, 4.1, 5.0, 3.45)
arrow(4.4, 4.1, 5.0, 1.65)
for y in (5.25, 3.45, 1.65):
arrow(6.8, y, 7.5, 3.2)
arrow(8.5, 2.4, 8.5, 1.3)
fig.savefig(out_path, dpi=300, bbox_inches='tight', pad_inches=0.05)
plt.close()
```
## Pipeline / flowchart pattern (linear with branches)
Same primitives, just arranged left-to-right with `arrow(x1, y1, x2, y2)`
between successive boxes. For parallel branches (Steps 2 ∥ 3 in
PaperOrchestra), draw two parallel rows with a fork-and-join.
## Algorithm-as-graph pattern
For diagrams that are *just* a topological graph (no labels of importance,
just nodes-and-edges), use graphviz:
```python
import graphviz
g = graphviz.Digraph(format='png')
g.attr(dpi='300', rankdir='LR', fontname='Times-Roman', fontsize='8')
g.attr('node', shape='box', style='rounded,filled',
fillcolor='#cfe2f3', color='#2060cc', fontname='Times-Roman', fontsize='8')
g.attr('edge', color='#2060cc', fontname='Times-Roman', fontsize='7')
g.edge('Input', 'Encoder')
g.edge('Encoder', 'Decoder')
g.edge('Decoder', 'Output')
g.render(out_path.replace('.png', ''), cleanup=True)
```
## Anti-patterns
- Never use clip-art icons or emoji.
- Never use color as the *only* signal (always pair with shape or label).
- Never let arrows cross labels — re-route around.
- Never use a bitmap background.
- Always `axis('off')` for diagrams; no spines, no ticks, no grid.
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 |