publication-chart-skill
Skill0 starsChanged 27 days agoMITView on GitHub
This skill should be used when the user asks for a publication-quality scientific figure or table, wants help choosing the right chart for results, needs a paper-ready pubfig or pubtab workflow, wants a figure + companion table for a results section, wants an Excel sheet turned into publication-ready LaTeX, or wants an existing scientific figure/table reviewed and upgraded.
- Installs packages
1 other project uses a version of this, 1 of them edited.
Adopted by
Most recently taken up by
- Galaxy-Dawn/claude-scholaredited, first seen Apr 15, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 1
- Galaxy-Dawn/claude-scholar★ 5.9k99% same
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository15 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- academic-humanizerSkill
- drawio-skillSkill
- innovation-exploreSkill
- paper-framingSkill
- paper-readingSkill
- paper-reviewSkill
- paper-storytellingSkill
- paper-style-profilerSkill
- paper-writing-orchestratorSkill
- research-pipelineSkill
- scientific-visualizationSkill
- session-handoff-promptSkill
- task-forestSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
40 rules. About 0 are common, 33 are distinctive, and 7 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈33
Distinctive · estimate
This author's own choices. Worth a look.
7
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 12
Use this skill to turn research results into publication-grade figures and tables with an end-to-end workflow.
- Distinctive: line 46
Do not use this skill when the task is mainly:
- Distinctive: line 83
Before generating anything, identify:
- Distinctive: line 90
Prefer the smallest environment check that helps execution.
- Distinctive: line 103
If a dependency is missing and the task requires runnable execution:
- Distinctive: line 106
prefer the user’s active environment instead of guessing a random global interpreter,
- Very specific: line 107
use python3 scripts/ensure_publication_tooling.py --require ...
- Distinctive: line 121
If auto-install fails, report the exact failure and then degrade gracefully.
- Distinctive: line 123
Do not block on a full environment audit.
- Distinctive: line 134
Do not jump into plotting code before the communication target is clear.
- Distinctive: line 136
Before plotting research results, lock the evidence contract:
- Distinctive: line 146
If these are unclear, ask or produce an audit recommendation instead of a polished figure.
- Distinctive: line 165
avoid pie/donut when exact comparison matters and a bar/table is clearer,
- Distinctive: line 166
avoid radar unless the comparison is genuinely profile-like and low-cardinality,
- Distinctive: line 167
avoid 3D, decorative gradients, and dense legends used only for style,
- Distinctive: line 168
avoid forcing every result into a figure when a publication table communicates the evidence better.
- Distinctive: line 170
If the request is ambiguous, explicitly state what scientific claim the artifact is supposed to support.
- Very specific: line 195
prefer Python for pubfig figure generation,
- Very specific: line 196
prefer CLI for pubtab when the task is file-driven,
- Very specific: line 197
prefer Python for pubtab when the task is already inside a notebook or scripted pipeline,
- Distinctive: line 198
keep the figure and table responsibilities separate in mixed requests.
- Distinctive: line 202
Prefer the smallest production-ready artifact first:
- Distinctive: line 211
Keep filenames and suffixes explicit.
- Distinctive: line 249
If the result is weak, revise with specific changes such as:
- Distinctive: line 256
add or simplify the caption,
- Very specific: line 262
If pubfig or pubtab is not available:
- Distinctive: line 264
do not fail immediately,
- Very specific: line 266
prefer python3 scripts/ensure_publication_tooling.py --require ...
- Distinctive: line 270
if installation succeeds, continue with the runnable workflow,
- Distinctive: line 271
if installation fails, degrade to a design/specification workflow,
- Distinctive: line 278
Treat composite or Figma assembly as secondary:
- Distinctive: line 280
use it when the user explicitly wants a multi-panel paper figure,
- Distinctive: line 283
Do not escalate simple figure tasks into composite/Figma workflows by default.
- Distinctive: line 287
Prefer direct, implementation-usable outputs.
- Very specific: line 289
When execution matters, include a short environment status block such as pubfig: available/missing, pubtab: available/missing.
- Distinctive: line 290
If a dependency is missing, state the exact helper command or install command, perform the installation, and report the post-install status.
- Distinctive: line 291
When a table is stronger than a figure, say so explicitly.
- Distinctive: line 292
When a figure is stronger than a table, say so explicitly.
- Distinctive: line 293
When both are needed, assign them different communication roles.
- Distinctive: line 294
Keep revision guidance actionable and falsifiable.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Publication Chart Skill
Goal
Use this skill to turn research results into publication-grade figures and tables with an end-to-end workflow.
Primary production stack:
pubfigfor figurespubtabfor publication tables
This skill covers the full delivery chain:
- understand the scientific communication goal,
- choose the right artifact type,
- map the task to
pubfig,pubtab, or both, - generate concrete runnable instructions,
- export paper-ready assets,
- run publication QA,
- propose targeted revisions.
Use this skill when
Trigger this skill for requests like:
- “make a publication-quality figure”
- “choose the right chart for these results”
- “turn these results into a paper-ready figure”
- “make a benchmark / ablation / calibration / forest / heatmap / scatter / line / bar figure”
- “make a benchmark / appendix / ablation table from Excel”
- “convert this Excel table into publication-ready LaTeX”
- “prepare one summary figure plus one companion table for the results section”
- “review and improve this scientific figure/table”
- “I already have a weak chart / screenshot / draft plot — make it publication-ready”
- “export panels for a paper figure”
Do not use this skill for
Do not use this skill when the task is mainly:
- manuscript prose writing,
- statistical testing without artifact design,
- raw exploratory analysis with no publication deliverable,
- Figma-first layout work before the figure/table content is solid.
For simple composite assembly after the figure content is already strong, use the optional secondary workflow in references/composite-assembly.md.
Primary contract
Inputs
Expect some combination of:
- the scientific communication goal,
- available data shape,
- venue or style constraints,
- whether the artifact is a figure, table, or mixed deliverable,
- optional existing assets such as code, spreadsheets,
.tex, screenshots, or draft plots, - whether the user needs a first draft, a publication-ready artifact, or a review/revision pass.
Outputs
The minimum useful output is:
- the recommended figure/table form,
- the recommended
pubfig/pubtabroute, - a minimal runnable code snippet or CLI command,
- explicit export filenames and formats,
- a publication QA summary,
- and, when needed, a revision plan.
Default workflow
0. Probe the environment and artifact state
Before generating anything, identify:
- whether
pubfigorpubtabis actually available, - whether the user already has code / spreadsheets /
.tex/ screenshots, - whether the deliverable is a fresh build or a revision,
- whether the result needs exact values, fast visual perception, or both.
Prefer the smallest environment check that helps execution. When the bundled helper script is available, use it first:
python3 scripts/ensure_publication_tooling.py --require pubfig --jsonpython3 scripts/ensure_publication_tooling.py --require pubtab --json
Equivalent manual checks are still acceptable when needed:
python -c "import pubfig; print(pubfig.__version__)"python -c "import pubtab; print(pubtab.__version__)"pubtab --help
Report the result clearly as available or missing.
If a dependency is missing and the task requires runnable execution:
- auto-install it by default,
- prefer the user’s active environment instead of guessing a random global interpreter,
- use
python3 scripts/ensure_publication_tooling.py --require ...as the default bundled route when the script is present, - let that helper choose
uvvspython -m pipagainst the active interpreter, - re-run the availability probe after installation,
- and only then continue with the artifact workflow.
Equivalent concrete commands include:
python3 scripts/ensure_publication_tooling.py --require pubfigpython3 scripts/ensure_publication_tooling.py --require pubtabuv pip install pubfiguv pip install pubtabpython -m pip install pubfigpython -m pip install pubtab
If auto-install fails, report the exact failure and then degrade gracefully.
Do not block on a full environment audit.
1. Classify the task
Classify the request along these axes:
- artifact type: figure / table / mixed deliverable
- maturity: exploratory draft / publication-ready generation / revision of an existing artifact
- structure: single panel / multi-panel / figure-plus-table package
- evidence mode: pattern perception / exact value lookup / both
Do not jump into plotting code before the communication target is clear.
Before plotting research results, lock the evidence contract:
- primary scientific claim,
- unit of analysis,
- primary metric and metric direction,
- whether repeated rows are independent,
- missing cells or incomplete comparison blocks,
- error-bar basis: subject, subject-task, fold, seed, run, or bootstrap sample,
- whether exact values need a companion table,
- whether the current evidence allows a winner/significance claim.
If these are unclear, ask or produce an audit recommendation instead of a polished figure. Do not create a paper-ready plot while the unit of analysis, missing-cell handling, or error-bar basis is unresolved.
2. Choose the representation
Choose the representation based on the scientific claim, not novelty or visual flair.
Common families:
- comparison — grouped scatter, bar, line comparison, benchmark summary, companion table
- ablation — grouped comparison, dumbbell, paired comparison, compact table
- distribution — box, violin, raincloud, histogram, density, ECDF, QQ
- relationship — scatter, bubble, contour2d, hexbin
- trend — line, area
- evaluation / diagnostic — calibration, ROC, PR, Bland–Altman, forest plot, volcano
- composition / hierarchy — UpSet, stacked ratio, donut, radial hierarchy, circular grouped or stacked bars
- table — benchmark table, ablation table, dataset summary, appendix table, error breakdown
Avoid weak defaults:
- avoid pie/donut when exact comparison matters and a bar/table is clearer,
- avoid radar unless the comparison is genuinely profile-like and low-cardinality,
- avoid 3D, decorative gradients, and dense legends used only for style,
- avoid forcing every result into a figure when a publication table communicates the evidence better.
If the request is ambiguous, explicitly state what scientific claim the artifact is supposed to support.
3. Map to the toolchain
Default mapping:
- Figures →
pubfig - Tables →
pubtab - Mixed deliverables → use both, with each artifact carrying a distinct role
Responsibility boundary:
publication-chart-skillowns the evidence contract, figure-versus-table decision, representation family, andpubfig/pubtabroute.- For figures,
scientific-visualizationowns encoding integrity, accessibility, physical-size planning, export provenance, and delivered-file inspection. pubfiggeneration is not a substitute for the figure-integrity and export checks. Whenscientific-visualizationis available, use its relevant checks after the representation is chosen; do not rerun the artifact-selection stage.- Tables remain under the
pubtaband table-QA route unless a companion figure is also requested.
Tool roles:
pubfigis the default figure engine for scientific plots and paper-ready export.pubtabis the default table engine for Excel ↔ LaTeX workflows, preview, and publication-ready table export.- Figma/composite assembly is an optional secondary branch for multi-panel finishing.
Route selection rules:
- prefer Python for
pubfigfigure generation, - prefer CLI for
pubtabwhen the task is file-driven, - prefer Python for
pubtabwhen the task is already inside a notebook or scripted pipeline, - keep the figure and table responsibilities separate in mixed requests.
4. Generate concrete artifact instructions
Prefer the smallest production-ready artifact first:
- minimal runnable Python for
pubfig, or - minimal CLI/Python for
pubtab
Then add publication parameters only when justified:
- labels, caption, width, export format, backend, preview, panel packaging, or composite layout.
Keep filenames and suffixes explicit.
Good defaults:
- figures: one
pubfigcall + onesave_figure(...) - multiple figure outputs:
batch_export(...) - tables: one
pubtab xlsx2tex ...orpubtab.preview ... - mixed requests: one figure route + one table route, clearly separated
5. Define the delivery contract
For every response, make these explicit when possible:
- the claim the artifact supports,
- which part is handled by
pubfigand which bypubtab, - the output filenames,
- the output formats,
- whether the artifact is draft / final / revision,
- what still needs user-provided data or manuscript context.
6. Run publication QA
After generation, check:
- title and legend density,
- axis labels and units,
- category ordering and baseline clarity,
- color accessibility and grayscale robustness,
- font / line-weight consistency,
- caption readiness,
- figure/table readability after downscaling,
- panel consistency for multi-panel figures,
- venue-fit issues such as width, crowding, or over-annotation.
The QA output must be concrete. Do not say “looks better” without naming why.
7. Revise
If the result is weak, revise with specific changes such as:
- switch chart family,
- remove chartjunk,
- reorder categories,
- move exact values into a table,
- split a crowded panel,
- add or simplify the caption,
- change export width,
- or convert the deliverable from figure-first to table-first.
Missing dependency behavior
If pubfig or pubtab is not available:
- do not fail immediately,
- first attempt automatic installation into the active environment,
- prefer
python3 scripts/ensure_publication_tooling.py --require ...when the bundled script exists, - explicitly state which dependency is missing,
- state which install command or helper route is being used,
- re-check availability after installation,
- if installation succeeds, continue with the runnable workflow,
- if installation fails, degrade to a design/specification workflow,
- provide pseudocode or draft commands,
- preserve the recommended figure/table structure,
- still provide QA and revision guidance.
Composite assembly rule
Treat composite or Figma assembly as secondary:
- use it when the user explicitly wants a multi-panel paper figure,
- or when panel-level export and layout polishing are genuinely needed.
Do not escalate simple figure tasks into composite/Figma workflows by default.
Output style rules
- Prefer direct, implementation-usable outputs.
- Explain the why of chart/table choice briefly, then give the runnable route.
- When execution matters, include a short environment status block such as
pubfig: available/missing,pubtab: available/missing. - If a dependency is missing, state the exact helper command or install command, perform the installation, and report the post-install status.
- When a table is stronger than a figure, say so explicitly.
- When a figure is stronger than a table, say so explicitly.
- When both are needed, assign them different communication roles.
- Keep revision guidance actionable and falsifiable.
Recommended response shape
A strong response using this skill usually has 6 parts:
- Artifact decision — figure / table / paired deliverable, and why
- Tool route —
pubfig,pubtab, or both - Minimal implementation — runnable code or CLI
- Export plan — filenames, formats, width/backend/preview choices
- Publication QA — what to verify before paper submission
- Revision plan — what to change if the current artifact is weak
Resources
Load these as needed:
references/workflow.md— full end-to-end decision order and delivery contractreferences/chart-selection.md— task-to-chart mapping and anti-patternsreferences/execution-and-verification.md— environment probing, forced install behavior, and runnable verificationscripts/ensure_publication_tooling.py— bundled probe + auto-install helper forpubfig/pubtabreferences/pubfig-recipes.md— shortest useful figure patterns and export routesreferences/pubtab-recipes.md— shortest useful table routes and backend guidancereferences/source-guides/pubfig-architecture.md— package layout and figure-generation boundaries from sourcereferences/source-guides/pubfig-api-map.md— stable public pubfig surface and chart-family map from__init__.pyreferences/source-guides/pubfig-export-flow.md— figure export, publication sizing, and panel-export flow from sourcereferences/source-guides/pubtab-architecture.md— package layout and forward/reverse conversion architecture from sourcereferences/source-guides/pubtab-cli-api-flow.md— CLI-to-API control flow and batch/sheet behavior from sourcereferences/source-guides/pubtab-backend-and-preview.md— backend/theme split and real preview compile pipeline from sourcereferences/publication-qa-checklist.md— figure/table QA checklistreferences/composite-assembly.md— optional multi-panel and Figma branch
For prompt-shaped examples, see examples/.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

