agentleFS
unravel11unravel11/research-paper-skills/.claude/skills/scientific-visualization/SKILL.md

scientific-visualization

Skill0 starsChanged 27 days agoMITView on GitHub

Create and audit truthful, accessible, publication-ready scientific figures with Matplotlib, Seaborn, or Plotly. Use for figure design, multi-panel layouts, uncertainty and missing-data displays, color/contrast review, image metadata validation, and journal export planning.

25 other projects use a version of this, 7 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use usfiscaldata, etetoolkit and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • yf8578Skill

    usfiscaldata

    Query the U.S. Treasury Fiscal Data API for federal financial data including national debt, government spending, revenue, interest rates, exchange rates, and savings bonds. Access 54 datasets and 182 data tables with no API key required. Use when working with U.S. federal fiscal data, national debt tracking (Debt to the Penny), Daily Treasury Statements, Monthly Treasury Statements, Treasury securities auctions, interest rates on Treasury securities, foreign exchange rates, savings bonds, or any U.S. government financial statistics.

    Also in 6 projects that use this

  • garri333Skill

    etetoolkit

    Phylogenetic tree toolkit (ETE). Tree manipulation (Newick/NHX), evolutionary event detection, orthology/paralogy, NCBI taxonomy, visualization (PDF/SVG), for phylogenomics.

    Also in 11 projects that use this

  • garri333Skill

    deeptools

    NGS analysis toolkit. BAM to bigWig conversion, QC (correlation, PCA, fingerprints), heatmaps/profiles (TSS, peaks), for ChIP-seq, RNA-seq, ATAC-seq visualization.

    Also in 10 projects that use this

  • Hongyu-yuSkill

    torch-geometric

    Graph Neural Networks (PyG). Node/graph classification, link prediction, GCN, GAT, GraphSAGE, heterogeneous graphs, molecular property prediction, for geometric deep learning.

    Also in 9 projects that use this

  • +8 more from garri333

The file

Show its rules and text

We split this skill into the rules it gives an agent

19 rules. 0 are common, 13 are distinctive, and 6 are very specific to this project.

  • 0

    Common

    Most of the 25 edited versions we read keep these.

  • 13

    Distinctive

    This author's own choices. Worth a look.

  • 6

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Never alter, hide, invent, or selectively enhance data to improve a figure.

    line 17
  2. Distinctive:

    Do not infer journal requirements.

    line 19
  3. Distinctive:

    Do not claim that a palette, DPI value, format, or automated report makes a figure accessible or journal-compliant.

    line 20
  4. Distinctive:

    Do not silently connect missing observations, suppress inconvenient points, upsample images as if detail increased, or tune axes/dual axes …

    line 21
  5. Distinctive:

    Do not assign favorable or unfavorable colors from method roles such as "ours", "proposed", or "baseline".

    line 22
  6. Distinctive:

    Keep interactive and static outputs as distinct deliverables.

    line 23
  7. Very specific:

    Read references/publication_guidelines.md for deceptive-encoding and integrity checks.

    line 25
  8. Distinctive:

    If requirements are not known, create a provisional general figure and label all publisher choices as pending verification.

    line 40
  9. Distinctive:

    Prefer position on a common scale.

    line 44
  10. Distinctive:

    Dual axes: prefer aligned panels; if unavoidable, justify units and do not engineer apparent correlation.

    line 56
  11. Distinctive:

    Use color plus marker, line style, hatching, direct label, or panel separation.

    line 61
  12. Distinctive:

    Treat WCAG 2.2 as web guidance: 4.5:1 normal text, 3:1 large text, and 3:1 for graphical objects required for understanding.

    line 66
  13. Distinctive:

    Use Matplotlib's object-oriented API and temporary style contexts:

    line 72
  14. Very specific:

    Use LogNorm, CenteredNorm, SymLogNorm, BoundaryNorm, or TwoSlopeNorm only when its mapping matches the scientific meaning.

    line 106
  15. Very specific:

    Use write_html() for interaction and write_image()/plotly.io.write_images() for static output.

    line 131
  16. Very specific:

    Do not pass deprecated engine= or use Orca/plotly.io.kaleido.scope.

    line 134
  17. Distinctive:

    Use an opaque explicit background unless transparency is required.

    line 168
  18. Very specific:

    All helpers are deterministic, network-free, bounded, reject symlink inputs/destinations where relevant, and refuse overwrite unless …

    line 200
  19. Very specific:

    Add --input figure.pdf to screen machine-readable properties.

    line 237

“Common” is measured: kept by at least 6 in 10 of the 25 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Scientific Visualization

Build figures that preserve scientific meaning before optimizing appearance. Separate universal principles from dated publisher rules, preserve raw data and transformations, use color redundantly, and inspect delivered files rather than trusting plotting defaults.

Non-negotiable guardrails

  • Never alter, hide, invent, or selectively enhance data to improve a figure.
  • Preserve raw tables/images, exclusions, missing-value codes, analysis code, normalization, binning, image adjustments, and random seeds.
  • Do not infer journal requirements. Identify the exact journal, article type, figure type, and submission phase; verify its live official guidance.
  • Do not claim that a palette, DPI value, format, or automated report makes a figure accessible or journal-compliant.
  • Do not silently connect missing observations, suppress inconvenient points, upsample images as if detail increased, or tune axes/dual axes to exaggerate a conclusion.
  • Do not assign favorable or unfavorable colors from method roles such as "ours", "proposed", or "baseline". Map color to declared data semantics, and use a restrained, redundant highlight only when the communication goal justifies it.
  • Keep interactive and static outputs as distinct deliverables. Interactive hover is not a substitute for labels, alt text, keyboard access, an accessible data table, or a static fallback.

Read references/publication_guidelines.md for deceptive-encoding and integrity checks. Read references/journal_requirements.md only after the target and phase are known.

Workflow

1. Define the evidence and destination

Record:

  • audience and medium: manuscript, web, slide, poster, supplement;
  • exact publisher/journal, article type, submission phase, and intended final width;
  • variable semantics, units, sample/replicate structure, missing/censored values;
  • estimator and uncertainty definition;
  • transformations: filtering, aggregation, normalization, smoothing, bins, image processing;
  • source-data paths/identifiers and output provenance.

If requirements are not known, create a provisional general figure and label all publisher choices as pending verification.

2. Choose an honest encoding

Prefer position on a common scale. Before coding, check:

  • Bars/areas: normally include zero because length/area is measured from a baseline.
  • Points/lines: nonzero limits can be valid; show context and disclose breaks.
  • Exact labels: annotate values only when the panel remains readable; labels do not replace axes, units, uncertainty, or a companion table.
  • Uncertainty: name SD, SE, CI, percentile, posterior, or another interval; state n and the unit of replication.
  • Raw observations: show them when feasible; do not let jitter obscure categories/values.
  • Missing data: distinguish missing, zero, censored, and excluded; use gaps or explicit model/interpolation styling.
  • Area/volume: scale area/volume, not radius/diameter; avoid decorative 3D.
  • Log axes: label the base/transform and declare how zero/negative values are handled.
  • Binning/smoothing: record edges, bandwidth/window, method, and sensitivity.
  • Normalization: state formula/reference and keep limits consistent across compared panels.
  • Dual axes: prefer aligned panels; if unavoidable, justify units and do not engineer apparent correlation.
  • Images: preserve originals, disclose whole-image adjustments, show scale bars, and avoid clipped/erased background.

3. Design accessibility in, not after

  • Use color plus marker, line style, hatching, direct label, or panel separation.
  • Choose qualitative, sequential, diverging, or cyclic color according to data semantics.
  • Audit foreground/background contrast at the rendered size.
  • Make missing and out-of-range values explicit.
  • Provide alt text, a longer description for complex figures, and underlying data for web delivery.
  • Treat WCAG 2.2 as web guidance: 4.5:1 normal text, 3:1 large text, and 3:1 for graphical objects required for understanding; color cannot be the only cue. Applicability and exceptions matter.

See references/color_palettes.md. A grayscale screen is useful but is not a complete color-vision or accessibility test.

4. Implement with scoped styles

Use Matplotlib's object-oriented API and temporary style contexts:

import matplotlib.pyplot as plt

from style_presets import style_context

with style_context("default", palette_name="okabe_ito_on_white"):
    fig, ax = plt.subplots(
        figsize=(89 / 25.4, 60 / 25.4),
        layout="constrained",
    )
    ax.plot(x, y, marker="o", label="Observed")
    ax.set(xlabel="Time (hours)", ylabel="Response (unit)")
    ax.legend()

layout="constrained" supports colorbars, nested GridSpec, subfigures, and subplot_mosaic. Do not call tight_layout() afterward; it disables constrained layout.

For exact physical dimensions, do not use bbox_inches="tight" unless the changed page size is intentional.

For dense comparison or multi-panel figures, read references/real_world_patterns.md. It provides three bounded patterns derived from public production examples: a dedicated legend axis, conditional bar-value labels, and layout dimensions derived from the target physical width. Treat them as candidates after the evidence contract is locked, not as a house style or universal default.

Color normalization

import matplotlib as mpl

norm = mpl.colors.TwoSlopeNorm(vmin=-2, vcenter=0, vmax=5)
cmap = mpl.colormaps["RdBu_r"].with_extremes(bad="#777777")
image = ax.imshow(values, norm=norm, cmap=cmap, interpolation="nearest")
fig.colorbar(image, ax=ax, label="Change (unit)")

Use LogNorm, CenteredNorm, SymLogNorm, BoundaryNorm, or TwoSlopeNorm only when its mapping matches the scientific meaning.

Seaborn

Seaborn 0.13.2 uses the current errorbar API:

sns.lineplot(
    data=frame,
    x="time",
    y="response",
    hue="treatment",
    style="treatment",
    markers=True,
    errorbar=("ci", 95),
    n_boot=5000,
    seed=20260723,
    ax=ax,
)

Axes-level functions fit custom Matplotlib layouts; figure-level functions create their own figures/facets. Do not customize Seaborn's internal artist lists as if they were stable API.

Plotly

  • Use write_html() for interaction and write_image()/plotly.io.write_images() for static output.
  • Kaleido 1.3.0 requires Chrome/Chromium; it no longer bundles Chrome.
  • Current static formats: PNG, JPEG, WebP, SVG, PDF. EPS is Kaleido v0-only.
  • Do not pass deprecated engine= or use Orca/plotly.io.kaleido.scope.
  • width, height, and scale control pixels; scale=3 is not inherently “300 DPI.”
  • WebGL traces embed raster content in PDF/SVG.
  • Fully offline exports need local external assets when a figure references MathJax/topojson/tiles.

5. Export explicitly and record provenance

from figure_export import export_figure

report = export_figure(
    fig,
    "outputs/figure1",
    formats=["pdf", "png"],
    dpi=600,
    bbox_inches=None,  # preserve figure page dimensions
    provenance={
        "raw_data": "data/source.csv",
        "transformations": ["predeclared QC filter", "group mean"],
        "uncertainty": "95% bootstrap CI; seed 20260723",
        "missing_data": "retained as gaps",
    },
    write_manifest=True,
)

The exporter refuses implicit overwrite, writes atomically, keeps vector DPI for embedded rasters, uses TIFF LZW, and can use PDF/PS Type 42 fonts. It does not validate scientific content or publisher acceptance.

For editable fonts:

  • PDF/PS Type 42 embeds TrueType fonts.
  • svg.fonttype="none" keeps text editable/searchable but does not embed fonts; appearance depends on installed fonts.
  • svg.fonttype="path" preserves glyph appearance as paths but loses editable/searchable text.

Use an opaque explicit background unless transparency is required; blending against another background changes apparent contrast.

6. Inspect, compare, and review

  1. Inspect file metadata.
  2. Audit palette contrast/grayscale separation.
  3. Compare against a dated publisher snapshot.
  4. View at final size in the manuscript/web context.
  5. Manually review fonts, embedded rasters, clipping, legends, scale bars, image integrity, caption, alt text, and source data.
  6. Re-check the live target-journal page immediately before upload.

Pinned snapshot

Environment compatibility: Python 3.11+ is required, and the pinned examples use uv. Bundled CLIs are network-free and load Matplotlib, Pillow, or pypdf only when needed. Plotly static export with Kaleido v1 requires a compatible Chrome/Chromium installation.

The examples and smoke tests use direct package pins current on 2026-07-23:

uv run --isolated --no-project --python 3.13 \
  --with "matplotlib==3.11.1" \
  --with "seaborn==0.13.2" \
  --with "plotly==6.9.0" \
  --with "kaleido==1.3.0" \
  --with "pillow==12.3.0" \
  --with "pypdf==6.14.2" \
  python your_figure.py

This is a dated direct-dependency snapshot, not a transitive lock. Use the project's uv lock for exact replay; this skill intentionally ships no dependency lock.

Bundled CLIs

All helpers are deterministic, network-free, bounded, reject symlink inputs/destinations where relevant, and refuse overwrite unless --force is explicit.

Inspect raster/vector metadata

uv run --isolated --no-project --python 3.13 \
  --with "pillow==12.3.0" \
  python scripts/image_metadata.py figure.tiff \
  --format tiff --mode RGB --min-dpi 300 --target-width-mm 85 \
  --alpha-policy forbid

Supports raster images (Pillow), SVG, PDF (pypdf), and EPS/PS. Reports dimensions, DPI/effective DPI, mode, alpha, ICC presence, compression, page size, and conservative first-page PDF font resources. It does not inspect every embedded raster in a vector container.

Audit palette contrast and grayscale

uv run --isolated --no-project --python 3.13 \
  python scripts/palette_audit.py \
  --palette okabe_ito_on_white \
  --background FFFFFF \
  --role graphical

Reports exact WCAG sRGB contrast plus pairwise CIE L* grayscale screening. The grayscale threshold is a heuristic, not a standard.

Plan/screen publisher export

uv run --isolated --no-project --python 3.13 \
  python scripts/export_plan.py \
  --publisher nature \
  --figure-type combination \
  --width single \
  --phase final

Add --input figure.pdf to screen machine-readable properties. Profiles are official-source snapshots accessed 2026-07-23, not automatic compliance rules.

Preview styles

uv run --isolated --no-project --python 3.13 \
  --with "matplotlib==3.11.1" \
  python scripts/style_preview.py \
  --output outputs/style-preview \
  --style default \
  --palette okabe_ito_on_white \
  --formats png,svg

Inspect/write styles and smoke-test export

uv run --isolated --no-project --python 3.13 \
  python scripts/style_presets.py --list
uv run --isolated --no-project --python 3.13 \
  python scripts/style_presets.py --show nature
uv run --isolated --no-project --python 3.13 \
  --with "matplotlib==3.11.1" \
  python scripts/figure_export.py --demo outputs/export-smoke --manifest

Assets

  • assets/publication.mplstyle: general print starting point.
  • assets/nature.mplstyle: dated flagship Nature visual starting point, not a compliance preset.
  • assets/presentation.mplstyle: larger projected-display style.
  • assets/color_palettes.py: importable Okabe-Ito and Paul Tol values with metadata.
  • assets/publisher_profiles.json: dated, machine-readable planning snapshots.

Matplotlib style files omit # in hex colors because # begins comments in .mplstyle parsing.

References

  • references/publication_guidelines.md: integrity, deceptive encodings, accessibility, static/interactive output.
  • references/color_palettes.md: palette semantics, exact values, WCAG contrast, grayscale caveats, color management.
  • references/journal_requirements.md: phase-specific official publisher snapshots.
  • references/matplotlib_examples.md: current, runnable Matplotlib/Seaborn/Plotly patterns.
  • references/real_world_patterns.md: provenance-aware production patterns and boundaries for legends, exact labels, and width-derived multi-panel layouts.
  • references/sources.md: official URLs, dates, versions, and research basis.

Final review checklist

  • Raw data/images and transformation code are preserved.
  • Missing values, exclusions, bins, normalization, and uncertainty are explicit.
  • Baselines, scales, limits, and area/volume encodings are honest.
  • Color is redundant and rendered contrast was reviewed.
  • Figure has an accessible description/data alternative where applicable.
  • Physical dimensions, DPI, format, fonts, transparency, and file size were inspected after export.
  • Publisher rules were verified for the exact journal and phase.
  • No automated report is presented as a scientific, accessibility, or compliance certification.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.