figure-caption-audit
Skill4 starsChanged 31 days agoMITView on GitHub
Use when auditing a scientific figure, diagram, chart, or caption for agreement with the current manuscript, especially arrows, data support, stages, comparisons, and evaluation endpoints. Supports text-only diagram specifications without implying that an image was inspected.
In this repository17 other files it gives its agents.
- academic-prose-editingSkill
- academic-writing-auditSkill
- claim-evidence-auditSkill
- experiment-comparison-auditSkill
- latex-bibliography-auditSkill
- manuscript-release-checkSkill
- method-definition-auditSkill
- nondefensive-writingSkill
- reference-authenticity-auditSkill
- related-work-synthesisSkill
- research-manuscript-writingSkill
- results-interpretationSkill
- reviewer-comment-triageSkill
- reviewer-response-writingSkill
- revision-integrity-auditSkill
- scientific-story-auditSkill
- word-citation-auditSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are 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.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 9
Check what the figure tells a reader before polishing how it looks.
- Distinctive: line 37
Stop when the requested figure and caption accurately communicate the supplied evidence.
≈ “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
Figure and Caption Audit
Check what the figure tells a reader before polishing how it looks. A visually clear diagram can still describe the wrong experiment.
Set the scope
Identify the requested deliverable: findings, caption repair, diagram instructions, or an actual asset edit. Preserve the author's sound structure and source assets. Use the current manuscript and relevant protocol as evidence; an older figure approval or review memo does not establish agreement with today's source.
Inventory the available representation: textual specification, editable source, exported image, or rendered manuscript page. These support different checks. A text specification supports a semantic review, not conclusions about pixels, legibility, cropping, color, or page layout. A source edit does not establish that an exported or embedded figure changed.
Audit the scientific meaning
- Map the elements. For each box, curve, panel, symbol, or legend label, identify the real object it represents and its source definition. Distinguish collected records, eligible training examples, diagnostics, predictions, and measured outcomes. Keep names and units consistent across the figure, caption, Methods, and results.
- Read every arrow as a claim. Determine whether it means data flow, temporal order, optimization, selection, evaluation, or a hypothesized relationship. Verify the endpoints and direction. Training, validation, and test feedback are different operations. Changing an unsupported feedback arrow to a dotted line does not establish a supported meaning; remove it or supply an accurate label and connection.
- Check populations and comparisons. Show which examples each method can use. Shared architecture, nominal update budgets, or a common archive do not imply identical training support. Keep diagnostic-only records outside training paths. For charts, check denominators, conditions, uncertainty definitions, and whether panels describe the same experiment before allowing direct comparisons.
- Match the measured endpoint. Trace the final stage to the actual outcome criterion. Preserve all required conditions, including evaluation stopping points. A system that detects a target has not thereby completed the downstream intervention. A schematic output icon should not imply a measured capability absent from the study.
- Repair the caption and figure together. A corrected caption cannot reliably cancel a contradictory arrow or label. Put interpretation-critical conditions where a reader can find them; leave detailed settings to the paper when they are not needed to understand the figure. Distinguish an illustrative workflow from observed experimental results.
For example, a dataset may contain accepted images and excluded images kept for an audit. A single “all images → training” arrow misstates support even if the caption calls the archive comprehensive. Route the audit separately while preserving the useful overall organization.
Prose when drafting or revising
When drafting or revising prose, including audit explanations, read prose editing rules. Preserve scientific meaning, necessary reasoning and valid technical terms. Keep sound passages, do not add unreported properties, and limit edits to the requested scope. The local reference covers concept accuracy, clear sentences, repetition and punctuation, including the required exceptions.
Verify and report
Return a short verdict, then each consequential mismatch as element/location → implied claim → source evidence → smallest repair. Provide a replacement caption or edit instructions when requested. State which valid elements should remain. Separate scientific repairs from optional visual preferences.
If image or page evidence is available and visual review is in scope, inspect the actual artifact at a useful size. After authorized edits, check the new export and relevant manuscript placement when accessible. Report the exact representation and coverage inspected; do not reuse a stale preview as verification. When only text is available, label the outcome a specification review and identify the remaining visual check.
Stop when the requested figure and caption accurately communicate the supplied evidence. Do not redesign a sound figure, manufacture results, alter the scientific protocol to fit the artwork, or claim a render was checked without observing it. No justified change is a valid result.
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.

