CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

paper-figure

Generate publication-quality figures and tables from experiment results. Use when user says "画图", "作图", "generate figures", "paper figures", or needs plots for a paper.

Quality

79%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/skills-codex-claude-review/paper-figure/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

70%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-engineered, highly actionable skill body: an 8-step workflow with real validation loops (render-then-verify, external review, partitioned checklist) and mostly copy-paste-ready code. Its weaknesses are redundancy (two overlapping figure-type tables, an off-topic opening blockquote) and the absence of any progressive disclosure — all reference material is inlined in a single long file.

Suggestions

Move the Step 8 correctness checklist and the Figure Type Reference table into a `references/` file (or delete the duplicate table, since Step 3 already covers it) to cut length and enable progressive disclosure.

Remove or relocate the opening blockquote about Codex reviewer installation — it is unrelated to figure generation and reads as injected noise at the top of the body.

Fix the bar-chart example to import from `paper_plot_style` and read data from a file, matching the skill's own "Do NOT hardcode data" Key Rule and making every snippet directly executable.

DimensionReasoningScore

Conciseness

The body is mostly dense, actionable material with no concept-explainer padding, but it can be tightened: the "Figure Type Reference" table largely duplicates the Step 3 decision tree, the opening blockquote about Codex reviewer installation is unrelated to figure generation, and the bar-chart example hardcodes data against the skill's own "Do NOT hardcode data" Key Rule. This matches anchor 3 (mostly efficient but could be tightened), not 2 since there is no tutorial-style over-explanation.

3 / 5

Actionability

The guidance is largely copy-paste ready: a complete style-config module, a working line-plot script, a bash run loop, LaTeX table and include snippets, and a concrete MCP review invocation. Minor gaps keep it below a 5 — the bar-chart snippet omits the `from paper_plot_style import *` line (so `COLORS`/`FONT_SIZE` are undefined as shown) and uses hardcoded values, and the Step 7 prompt leaves a raw `[VENUE]` placeholder.

4 / 5

Workflow Clarity

Eight clearly sequenced steps with explicit validation checkpoints and feedback loops: Step 5 requires render-then-verify on the rendered PDF/PNG (not the script) before review, Step 7 polls the reviewer to `done=true` and preserves `threadId` for follow-up, and Step 8 partitions a checklist into binding correctness rules and overridable guidance. This matches the top anchor — clear sequence, explicit validation, error-recovery loops, and a checklist for a complex process.

5 / 5

Progressive Disclosure

There are no bundle files at all (verified: no references/, scripts/, or assets/ directories exist), so everything lives in one ~315-line SKILL.md. Section headers make it navigable, but content that clearly belongs in separate reference files — the figure-type reference table and the long Step 8 correctness checklist — is inlined, matching anchor 3 (some structure, but content that should be separate is inline) rather than 2 since sections are well-signaled.

3 / 5

Total

15

/

20

Passed

Description

78%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description with an explicit what-and-when structure and natural trigger terms in two languages. Its main gap is thin action coverage — only two actions are named, leaving the reader to infer the full capability set (LaTeX tables, include snippets, style presets) from the body.

Suggestions

Enumerate one or two more concrete actions in the description, e.g. "...tables, LaTeX include snippets, and comparison tables from experiment data" to lift specificity beyond two actions.

Add common trigger synonyms such as "charts", "plots", or "tables" to broaden natural trigger coverage.

DimensionReasoningScore

Specificity

The description explicitly names the domain ("publication-quality figures and tables from experiment results") and exactly two concrete actions — generating figures and generating tables. This matches the anchor for naming the domain with 1-2 concrete actions but not comprehensive coverage; a 4 would require several listed specific actions.

3 / 5

Completeness

It clearly answers both questions: "Generate publication-quality figures and tables from experiment results" states the what, and "Use when user says..." gives explicit concrete trigger phrases for the when. This matches the top anchor exactly.

5 / 5

Trigger Term Quality

Triggers include natural phrases users would actually say: "generate figures", "paper figures", "画图", "作图", and "needs plots for a paper". Coverage is good but a 5 would also include common synonyms like "charts", "visualizations", or "tables".

4 / 5

Distinctiveness Conflict Risk

The paper-specific framing ("publication-quality", "plots for a paper") carves out a distinct niche, but the skill could still overlap with general plotting or dataviz skills that trigger on "figures" or "plots" — minor overlap risk with closely related skills, matching anchor 4.

4 / 5

Total

16

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

wanshuiyin/Auto-claude-code-research-in-sleep

Path

skills/skills-codex-claude-review/paper-figure/SKILL.md

Reviewed

Table of Contents

Is this your skill?

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.