data-visualization-and-figures
Skill2 starsChanged 29 days agoMITView on GitHub
Choose or critique scientific plots, tables, image panels and explanatory figures. Exclude plotting-code fixes and implementation of settled visual specifications.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- jjfroehlich/agent-skills-for-academic-researchword for word, first seen Oct 17, 2026
Other versions1 project uses a version of this.
Word for word · 1
- jjfroehlich/agent-skills-for-academic-research★ 2100% same
Edited · 0
None found.
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 repository10 other files it gives its agents.
- career-developmentSkill
- grant-writingSkill
- life-science-research-handbookSkill
- literature-reading-and-synthesisSkill
- mentoring-management-and-lab-cultureSkill
- publishing-and-peer-reviewSkill
- research-strategy-and-project-designSkill
- scientific-communicationSkill
- scientific-feedbackSkill
- scientific-writingSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 18
Read the narrowest relevant references below.
- Distinctive: line 20
Use hierarchy deliberately.
- Very specific: line 34
Use checklists/publication-readiness.md for an actual readiness pass and examples/ for concrete applications.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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
Data Visualization And Figures
Help the reader make the scientific comparison accurately and easily. Use this skill when visual choices remain unresolved: chart form, evidence layers, scales, color, image presentation, diagrams, layout or export. Mixed code-and-design requests qualify when they require that judgment. Pure syntax fixes, plumbing, unchanged reruns and implementation of settled specifications do not call for redesign.
Work from the reader's task
- Identify the operation: compare amounts, distributions or effects; follow change; inspect relationships; understand a process; read image evidence; or look up exact values. Determine what each mark represents, the independent unit, relevant grouping/pairing and intended medium. Use supplied context before asking for missing details.
- Preserve settled specifications and meaningful existing styling. For unspecified ordinary trajectories, start with solid lines, circles if markers help, a restrained palette and clear labels. These are editorial starting preferences. Use dashes, shapes or stronger colors when they carry meaning or solve an actual reading problem.
- Read the narrowest relevant references below. Compare plausible designs, including what each reveals and hides. Resolve scientific meaning before cosmetic polish; do not let a generic rule override the task or evidence.
- Make important comparisons visible. For continuous groups, consider center, spread, shape and observations together. A box/violin/point combination can help; sparse groups can omit density while retaining points and a named center, and dense groups need not show every dot. Do not confuse descriptive spread with uncertainty of an estimate.
- Use hierarchy deliberately. Position, labels, facets and whitespace may already identify groups; extra color, dashes and shapes are not automatically necessary. Keep essential marks readable and equally important groups comparable in emphasis.
- Inspect the actual rendered figure at the intended size. Check scientific decoding, labels, scale, contrast, important structures and relevant accessibility conditions. If the artifact is unavailable, keep exact appearance claims conditional. Report checks actually performed.
Read according to the decision
references/chart-selection.md: reader operations, chart families, distribution diagnostics, composition and tables.references/statistics-and-uncertainty.md: distribution layers, estimands, pairing/nesting, intervals, smoothing and uncertainty displays.references/color-and-accessibility.md: palette meaning, restrained emphasis, identification cues and actual accessibility checks.references/specialized-figures.md: heatmaps, networks, genomic views, intersections, projections, maps and dense time series.references/biological-images.md: morphology versus intensity, scale, channels, annotations, representative images and analysis reporting.references/layout-and-typography.md: panel relationships, axes/transformations, labels, tables and final-size readability.references/conceptual-figures.md: graphical abstracts, mechanisms, spatial claims, arrows and known versus hypothesized relations.references/publication-technical-requirements.md: medium, formats, editable masters, reproducible revisions and export inspection.
Use checklists/publication-readiness.md for an actual readiness pass and examples/ for concrete applications. Consult references/handbook-access.md optionally when a fuller explanation or worked figure would help. The bundled reasoning works without the handbook; a text edition alone cannot establish visual quality.
Deliver the requested result
Give the figure, critique or recommendation the user asked for. Explain consequential choices through their purpose and tradeoff. A short request need not receive a full checklist report. When uncertainty matters, distinguish observed findings, reasonable assumptions and information still needed.
Reject invented metadata, hidden transformations, unsupported causality and unreported changes to the unit or estimand. Avoid automatic palette replacement, marker cycles, mean-only displays that conceal consequential structure, and complexity added solely to satisfy a rule. Prefer the least complicated design that preserves the important scientific information.
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.

