academic-figure-generation
>
pinned to #68098d5updated 3 months ago
Ask your AI client: “install skills/academic-figure-generation”.
Requires the metahub MCP server installed in your client. Set up MCP.
mh install skills/academic-figure-generationmetahub onboarded this repo on the author's behalf.
If you own github.com/jxtse/scientific-research-skills on GitHub, claim the listing to take over publishing. Your claim preserves the existing eval history and badges; only the curator label is replaced with verified-publisher on your next publish.
Stars
54
Last commit
3 months ago
Latest release
published
- #academic-research
- #agent-skill
- #claude-skill
- #literature-review
- #zotero
About this skill
Pulled from SKILL.md at publish time.
Thin CLI wrapper around PaperBanana (a.k.a. PaperVizAgent), a multi-agent figure-generation pipeline for academic papers.
Automated checks the publisher passed at publish time — structure, docs, safety, and whether the artifact behaves as claimed.68098d5· 3 months ago
Behavioral checks ran but aren't published for this artifact; the static checks above ran at publish time.
Documentation
4 passed1 warningDescription qualitywarn
21 words · 101 chars — manifest description is empty; graded the GitHub repo description instead
A skill's manifest description doubles as its trigger — add one to SKILL.md (15+ words, e.g. “use this skill when …”).
README is present and substantial
13,987 chars · 7 sections · 5 code blocks
Tags / topics declared
5 total — academic-research, agent-skill, claude-skill, literature-review, zotero
README has usage / example sections
found: Quick Start · Installation · Example
Homepage / docs URL declared
no homepage declared (registry will use the repo URL) — info-only, not blocking
Release history
1- releasecurrent68098d5warn3 months ago
Contents
Thin CLI wrapper around PaperBanana (a.k.a. PaperVizAgent), a multi-agent figure-generation pipeline for academic papers.
The skill provides exactly one script: scripts/generate.py. It feeds
your method text + caption into PaperBanana and writes N candidate PNGs.
Model selection and API keys come from PaperBanana's own
configs/model_config.yaml — the wrapper does not override them.
One-time setup
-
Clone PaperBanana somewhere convenient:
git clone https://github.com/dwzhu-pku/PaperBanana.git ~/PaperBanana cd ~/PaperBanana uv venv && uv pip install -r requirements.txt -
Configure
configs/model_config.yaml— set the image model and the matching API key. Two common setups:defaults: image_model_name: "gemini-3-pro-image-preview" # or "openai/gpt-5.4-image-2" model_name: "gemini-3.1-pro-preview" # text model for Planner/Stylist/Critic api_keys: google_api_key: "..." # required for Gemini models openrouter_api_key: "" # required for openai/gpt-5.4-image-2Use Gemini if you have a Google AI key; use GPT-Image-2 via OpenRouter if you have an OpenRouter key. Pick one — there's nothing else to wire up.
Workflow
Step 1: Gather inputs
You need:
- Method text: the relevant section of the paper describing the
approach (
./method.mdor./method.tex). - Figure caption: the target caption, e.g.
"Figure 1: Overview of our framework".
If the user only gives a vague request, ask:
- What aspect of the method should the figure focus on?
- Style? (block diagram, flowchart, pipeline, architecture, comparison)
- Venue / column width? (ACL ≤ 7.5", NeurIPS single-column 5.5")
Step 2: Generate
~/PaperBanana/.venv/bin/python scripts/generate.py \
--paperbanana-root ~/PaperBanana \
--method-file ./method.md \
--caption "Figure 1: Overview of our framework" \
--out-dir ./figures/v1 \
--candidates 3 \
--aspect-ratio 16:9
| Flag | Default | Notes |
|---|---|---|
--paperbanana-root | (required) | Path to your PaperBanana checkout |
--method-file | (required) | Method section as a text/markdown file |
--caption | (required) | Target figure caption |
--out-dir | (required) | Where PNGs land |
--candidates | 3 | Independent diagram candidates |
--max-concurrent | 2 | Cap concurrent runs (be gentle on quota) |
--exp-mode | demo_full | Full pipeline (Planner+Stylist+Visualizer+Critic). Use demo_planner_critic to skip Stylist, or vanilla for single-shot. |
--aspect-ratio | 16:9 | One of 21:9, 16:9, 3:2, 1:1 |
--max-critic-rounds | 2 | Critique → revise loops (early-exits if critic says "No changes needed") |
Step 3: Present & iterate
- Show all candidates to the user.
- Common refinements: color scheme, layout, label text, font size.
- Re-run with a tweaked caption or more candidates.
Step 4: Export
- PNGs are written as
candidate_0.png,candidate_1.png, … in--out-dir. - For camera-ready PDFs:
magick candidate_0.png candidate_0.pdf.
Style guidelines
- Color: consistent, colorblind-friendly palette
- Fonts: match the paper's body font (Times for ACL/EMNLP, Helvetica/Arial for many ML venues)
- Labels: concise; no full sentences inside the diagram
- Arrows: solid for data flow, dashed for optional / feedback loops
- Whitespace: don't overcrowd — reviewers skim figures in seconds
Common figure types
| Type | When to use | Key elements |
|---|---|---|
| Pipeline / Flowchart | Sequential processing | Boxes + arrows, L→R or T→B |
| Architecture | System overview | Nested boxes, clear module boundaries |
| Comparison | Before/after, baseline vs proposed | Side-by-side panels |
| Ablation | Component contributions | Bar charts, highlighted rows |
| Framework | High-level conceptual overview | Abstract shapes, minimal detail |
Troubleshooting
429 RESOURCE_EXHAUSTEDon Gemini: monthly Google AI Studio spending cap hit. Raise it at https://ai.studio/spend or switchimage_model_nametoopenai/gpt-5.4-image-2and setOPENROUTER_API_KEY.OpenRouter Client not initialized:OPENROUTER_API_KEYnot in env andopenrouter_api_keynot in yaml.- No PNGs in output dir: check
out_dir/results.jsonfor the raw per-candidate response and any error messages. - Long latency (>5 min): most wall time is the image model. Lower
--candidatesor use--exp-mode vanillafor faster iteration.
Links
- PaperBanana repo: https://github.com/dwzhu-pku/PaperBanana
- PaperVizAgent (Google Research version of the same project): https://github.com/google-research/papervizagent
Reviews
No reviews yet. Be the first.
Related
Verification Before Completion
Evidence before assertions, always
Writing Plans
Turn specs into phased implementation plans
Test-Driven Development
Red → green → refactor discipline for any feature or bugfix
mh install skills/academic-figure-generation