figure-style
Publication-grade correctness and legibility rules for final-deliverable scientific figures, not exploratory plots. Use for a figure that will ship in a report, paper, export, or kept artifact.
Install / Use
npx skills add aipoch/open-science --skill figure-styleInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
Development & EngineeringSupported Platforms
Tags
Our assessment of figure-style
figure-style scores 94/100 on our quality scale, 492nd of 4,700 Development & Engineering skills we index (top 11%).
Its SKILL.md is 20 KB long, well organised into 15 sections with 3 code examples: a thorough specification that gives an agent plenty to work with.
With 4,918 GitHub stars, it is one of the more widely adopted skills in the catalogue.
Maintenance, license and trust
- The repository was last updated about 2 months ago, so figure-style is actively maintained.
- Our last check on 2026-11-16 found the source still online.
- It is released under the Apache-2.0 license, a permissive license that allows use, modification and commercial use with attribution.
- Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.
AI review by kimi-k2.7-code on 2026-09-29. Automated pattern scan on 2026-09-28. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
figure-style compared with similar skills
All 4 of these similar skills score higher than figure-style; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| figure-style (this skill)by aipoch | 94 | 4.9k | 53d ago | SKILL.md |
| taste-skillby Leonxlnx | 100 | 116.8k | 8d ago | CLAUDE.md |
| ai-job-searchby ai-job-search-dev | 100 | 72.1k | today | CLAUDE.md |
| claude-howtoby luongnv89 | 100 | 47.3k | 2d ago | CLAUDE.md |
| lobehubby lobehub | 100 | 85.6k | today | MCP Server |
Frequently asked questions
- How do I install figure-style?
- Run
npx skills add aipoch/open-science --skill figure-style. The install tabs above show the steps for each supported agent. - Which AI agents does figure-style work with?
- It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is figure-style safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is Apache-2.0-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is figure-style still maintained?
- The repository was last updated about 2 months ago, so figure-style is actively maintained.
Skill content
View source on GitHubname: figure-style
description: 'Publication-grade correctness and legibility rules for final-deliverable scientific figures, not exploratory plots. Use for a figure that will ship in a report, paper, export, or kept artifact. Covers data fidelity, label economy, color threading, chart choice, layout, and render-then-verify QA without imposing a visual house style. For multi-panel composition use figure-composer; for whole-paper ordering use paper-narrative.'
license: Apache-2.0
Publication-Grade Figure Rules
A checklist for correct, legible, internally-consistent scientific figures. This
skill does not impose a visual house style — frame, font, and palette are
parameters. Before plotting, follow the Notebook call below and invoke
apply_figure_style().
Open-Science Notebook call
Every notebook_execute request whose code uses a function named in this skill
includes this skill ID:
{ "kernelSkillIds": ["figure-style"], "code": "apply_figure_style()\n..." }
kernelSkillIds contains the skill ID; function calls belong in code. This
request is complete as written: call the named functions directly and do not add
an import or discovery step.
§0 Scope
Load trigger (same rule as the system prompt's "Publication-grade plots" section): this skill is for final-deliverable figures — those shipping in a report, paper, or export, or saved as an artifact the user will keep — not for exploratory/intermediate plots (quick looks, EDA, sanity checks), which are drawn plainly without it. Once loaded, "every plot" below means every plot you render toward the deliverable.
§1–§3, §8, and §9 are correctness — they apply to every plot, in every
context, and have no aesthetic content. §4–§7 are guidance — defaults that
produce a clean result but that a deliberate alternative can override
(individual rules inside §4–§7 that state a factual/perceptual invariant — e.g.
§4.4 semantic-zero centering, §4.5 CVD, §6.9 leader anchoring — still bind). On
its own, this skill is the inner tier (make one plot good); figure-composer
and paper-narrative supply multi-panel and whole-paper context.
§1 Data fidelity & self-consistency
1.1 Excluded rows. A row marked excluded or flagged in the source data is either omitted entirely or drawn with a visually distinct open/hatched marker and named in the key. It never enters a summary statistic plotted alongside the included rows.
1.2 Comparable conditions only. Arms measured under non-comparable conditions (different N, epoch budget, initialization, protocol) are not plotted as visual peers. Separate them with a facet break or a marker on the label, and state the difference once in the caption.
1.3 Self-consistency. Every key, threshold, and title inside the figure must be satisfied by every plotted row. Before saving, walk each categorical outcome label back to the rule that defines it; if a row's value contradicts its label or the title, the figure is wrong, not the data.
1.4 Claim-titles must be true. A sentence-title (§5.1) is tested against every category on the axis before rendering. If any contradicts it, qualify the title ("on 3 of 4 pairs") or downgrade it to a description.
1.5 State n and what was held fixed. Every panel that draws a summary mark
states n and the unit of replication, and every small-multiple that holds a
variable fixed states the fixed value — in the panel or, when §2 budget is
tight, in the caption.
1.6 Reference structure is reference. A tree, ordering, or topology drawn as context (a scale bar, a category strip) uses an established reference, not one inferred from the plotted data. Infer the structure only when the structure is the result.
1.7 One number per claim. A quantitative claim (runtime, accuracy, count) has exactly one canonical value across every panel, caption, and the abstract. Define what it measures and use that value everywhere.
§2 Label economy — floor and ceiling
The figure shows the pattern; the caption carries the context. Design for a general scientific reader, not the author.
2.1 Floor (non-removable). Every distinct mark, series, glyph, or comparator must be identifiable from the figure alone. The caption explains why it matters, not what it is. A label is non-removable if deleting it leaves a reader asking "what is that?"; it is removable only if the question becomes "why is that there?". Comparator labels name the thing ("prior method", "no joint training"), never a bare role word ("baseline", "previous"). Any term a general scientist can't parse gets a one-word gloss.
2.2 Ceiling. Per panel: title + axis labels + tick labels + series identity (labeled once per row of small multiples) + at most 2–3 result annotations. Count the strings; >6 beyond axes/ticks means you're over. The ceiling counts narrative annotations (callouts, value labels, brackets) — identity labels are floor, not budget.
2.3 Move to the caption: n=, what's-held-fixed, abbreviation expansions, non-comparable footnotes, exclusion rationale, methodological caveats.
2.4 Titles are takeaways. A reader seeing only the title knows what the panel shows. "Robust to gene dropout" passes; "Fewer genes" fails. Test: read it aloud cold — if the listener asks "fewer genes what?", rewrite. For a row of small multiples that vary one thing, drop per-panel titles for one row-header.
2.5 Value-on-mark only for the headline number — the one a reader would quote. Everything else is read off the axis.
2.6 When in doubt, delete the label and re-read. If the message survives, it stays deleted.
§3 Axes, scales, small multiples
When an existing axes needs a frame different from the figure-wide setting, call
set_frame(ax, style=...).
3.1 Axis padding. Axis limits clear the data by ≥ one marker radius on every
side; markers and text never touch a spine. ax.margins(0.04) after plotting,
or extend the limit past any annotation.
3.2 Axis breaks over wasted range. When data occupy <40 % of an axis, break the axis or start it at the data floor with a clear non-zero tick. Never draw a reference line, threshold, or annotation inside a broken-axis gap — the gap has no coordinate.
3.3 Log axes get human-readable ticks — 10², 10³, or 1k / 10k / 100k,
not raw exponents. Never draw filled bars on a log-scaled value axis (bar
length encodes ratio to an arbitrary floor); use points + median tick instead.
3.4 Shared axes across small multiples. A row or column of small multiples
shows tick labels once (leftmost / bottommost panel); interior panels keep ticks
but drop labels. When the panels share a y-axis and differ only by x-variable,
render them as abutting subplots (wspace≤0.06) with one row-header title.
3.5 Fill the box. A panel's data envelope occupies ≥75 % of its allotted rectangle. If a panel's natural aspect leaves dead bands, reshape the grid (rowspan, stacked complementary panels) — don't pad the panel.
3.6 Direction of goodness. When higher- or lower-is-better is not obvious
from the axis label, place a small upright cue ("higher = better") in the
margin — once per row of panels, never per panel, and never only in the caption.
A directional glyph embedded in rotated text rotates with it; set the cue
upright. goodness_arrow(ax, ...) places this cue.
3.7 Physical width. A single-row figure at 300 dpi fits the venue's double-column width. Adding a schematic or labels does not push data panels narrower than they were before.
§4 Color
4.1 Threading. Once a color is bound to an entity (a method, a feature, a condition), reuse that exact color for every mark representing that entity across the figure — line, fill, marker, text, heatmap row. Color is the cross-reference; a reader should never have to consult a legend twice.
4.2 Limit hues. Use as few distinct hues as the data require. When the
figure compares a focal series against others, make the focal series visually
dominant (saturated, heavier weight) and render comparators with lower visual
weight (desaturated, lighter, or thinner). The focal hue must not coincide with
any hue in a categorical palette used in the same figure. The focal series must
remain identifiable even when its mark is zero-width or coincident with others —
via outline, marker, or a light tinted band. Use focal_palette(...) to bind the
focal and comparator colors to the ordered labels.
4.3 Hierarchical categories. When categories nest (groups within groups), the outer level picks the hue family and the inner level samples within it.
4.4 Continuous and diverging. Use a perceptually uniform sequential map for generic continuous values; a single-hue ramp for ordinal rank or size; a diverging map for signed quantities — always centered at the semantically meaningful zero (0, 1.0, or median), never the data midpoint.
4.5 CVD safety. Never rely on a red/green contrast for a binary or opposing distinction. Any binary pair should remain distinguishable in deuteranopia simulation. Reserve one alarm hue for error/anomaly/perturbation marks and do not reuse it as a data-series color.
4.6 Two palettes, two legends. When a figure uses two categorical color systems, each legend sits adjacent to the first panel where its palette applies.
§5 Typography
5.1 Sentence titles. A panel title states the comparison in plain language, regular weight, left-aligned. Metric names go on the axis, not in the title.
5.2 Role-mapped size ladder. A figure uses at most three font sizes,
mapped to role not space: titles/axis-labels/series-identity at the base size;
legend/annotation text one step down; tick labels one step further. Panel
letters are the only exception (bold, larger). If a label doesn't fit at its
role's size, fix the layout or shorten the text — don't reach for an
intermediate size. apply_figure_style(sizes=(8,7,6)) sets the ladder. When one
secondary metadata line is necessary, build the two-line text with
two_tier_label(name, meta).
5.3 Nomenclature. Species, gene, and variable names that scientific convention italicizes are italicized. Abbreviated codes inherit the rule; expand once on first appearance.
5.4 Magnitude suffixes. Large counts use k / M / B (4.2B, 120 kb),
not comma-grouped full numerals.
5.5 Numeric annotations. On-mark numbers use at most 2 significant figures — unless 2-sf rounding would make two distinct rows print the same value, in which case show the digit that separates them. Text on a filled mark reaches ≥4.5:1 contrast; if it doesn't, place the text outside the mark.
5.6 No internal codes. Axis labels use plain-language names; codebase abbreviations appear only in parentheses after the readable name or in the caption. Comparator series are labeled with what they are, not a role word.
5.7 Panel letters. Bold, top-left, outside the axes box. Case follows the
target venue's convention; panel_letter(ax, 'a', case=...) handles either.
§6 Chart-family guidance (by data shape)
6.1 Categorical × numeric. Show the distribution, not just the summary.
Chart choice follows n: jittered strip with a median tick for small n; box or
violin for large n; bar + overlaid raw points or bar + interval when the mean is
the message. Use strip_with_median(...) for the jittered-strip form and
bar_with_points(...) for bars with raw points or an interval. The
errorbar='ci95' interval is the t-distribution 95% CI of the mean (half-width
t_{0.975,n−1}·s/√n), so it is valid at small n. Error bars and raw-point
overlays are alternatives — showing both is usually redundant. A category
absent from a group is marked (n.d., —, or a hatched ghost) at its slot; an
empty slot reads as zero. A zero-valued bar gets a visible stub or dot at the
baseline.
6.2 Single-observation categories. A filled dot with a thin
Truncated for display — read the full file on GitHub.
Related Skills
taste-skill
116.8kAgent skills that give coding agents taste: art direction, reference images and a browser check instead of generic AI pages
ai-job-search
72.1kThe job search that runs on your machine. AI job application framework built on Claude Code: evaluate postings, tailor CVs, write cover letters, prep interviews. Fork it and own it.
claude-howto
47.3kA visual, example-driven guide to Claude Code — from basic concepts to advanced agents, with copy-paste templates that bring immediate value.
lobehub
85.6k🤯 LobeHub - Super-Agents on Your Team. Add super-agents to the chats your team already uses.They take on work by themselves and get better every week.
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
