Advises on the design of the three core figures in a technical paper: the Motivated Example (Figure 1), the Solution Overview (Methodology), and the Experimental Results figures. Recommends the right design paradigm, layout, labelling, and tool for each figure type, then runs a quality-control audit. Use when the user asks to 'design a figure', 'draw Figure 1', 'plot experiment results', 'choose the right chart type', 'which figure tool to use', or 'figure looks unprofessional'.
80
100%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Passed
No findings from the security scan
A top-venue paper typically carries six to eight figures, with three carrying almost all the storytelling weight: the Motivated Example (Figure 1, on page 1 or the top of page 2), the Solution Overview (inside the Methodology section), and the Experimental Results figures (inside the Experiments section). Reviewers scan these three in under a minute to decide whether the paper is worth reading in detail; weak figures sink otherwise-strong papers.
This skill takes the user's intent (what they want to communicate) plus context (research area, method name, target venue) and returns the recommended paradigm, a layout sketch, labelling guidance, tool suggestion, and a quality-control audit against a universal rule set (vector format, font size, colour-blind-safe encoding, self-contained caption, honest axis ranges).
intro-drafter or
tech-paper-template first to decide what figures the paper
needs.pre-submission-reviewer.Decide which of the three core types the figure is. If the user's request does not match any, either it is a supporting figure (use the experimental-results guidance as a base) or it does not belong in the paper.
If the mode is figure-audit and the user has provided an image
path, load the image with the Read tool before proceeding to
Step 2. Vision-based inspection enables the universal rule audit
in Step 6 to check font legibility, colour palette, raster-vs-
vector tells, and chartjunk directly rather than relying on user
description. If no image is provided, continue in text-only mode
and mark vision-only rules (font size, raster detection, colour
palette) as "user must verify" in the final audit report.
See: references/motivated-example.md, references/solution-overview.md, or references/experimental-results.md depending on figure type.
Each figure type has two to three canonical paradigms. Pick the one that fits the user's storytelling need, and explain why the other paradigms fit less well.
Produce a text description of the layout: panel positions, element placement, arrows, colour assignments. The goal is that the user could draw the first draft from the sketch alone.
See: references/tools.md for the tool matrix and the decision heuristic.
Default recommendations:
plot_utils.py script.See: references/design-rules.md for the full universal rule set.
Verify every proposed or existing figure against:
Flag every violation with severity.
Run the checks in the Integrity gate section below.
Emit the full design in the Output format below.
Bullets tagged [inspection] are checked by the LLM from its own output. Bullets tagged [user-verify] require the user to confirm because the check depends on either the drawn figure or knowledge the skill does not have (paper context, prior Introduction).
Before returning the design:
If any [inspection] check fails, mark the design as "needs user attention". For [user-verify] items, surface them to the user as items they must confirm before submission.
aff5de9
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.