CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

63

Quality

75%

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-gemini-review/paper-figure/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

63%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.

The body is a thorough, actionable guide with concrete code and a clear step sequence, but it carries redundancy between its decision tables and inlines material that would benefit from being split into referenced files. Tightening the duplicated tables and adding a batch failure-retry loop would lift the weakest dimensions.

Suggestions

Consolidate the Step 3 decision tree and the trailing Figure Type Reference table into one table to remove redundancy and recover tokens.

Add a per-figure failure/retry step in Step 5 (e.g. re-run only failed scripts and re-verify) so the batch operation has an explicit feedback loop.

Move the full paper_plot_style.py configuration and the type×style reference into files under references/ and link to them, replacing inline bulk content and the missing shared-references links.

DimensionReasoningScore

Conciseness

Mostly efficient and task-relevant, but the Step 3 decision tree and the trailing Figure Type Reference table overlap substantially, and prose like "In practice: ~60% / ~40%" plus repeated rules add padding; not a 4 because the redundancy is noticeable rather than minor.

3 / 5

Actionability

Provides copy-paste-ready Python, a bash run loop, LaTeX snippets, and a concrete MCP review call; not a 5 because some examples hardcode values (e.g. values = [82.3, 85.1...]) which contradicts the skill's own "Do NOT hardcode data" rule.

4 / 5

Workflow Clarity

An explicit 8-step sequence with a Step 5 output-existence check and a Step 8 quality checklist supplies most checkpoints; not a 5 because the batch run loop lacks per-figure failure handling and an explicit fix-and-retry feedback loop.

4 / 5

Progressive Disclosure

Section headers give some structure, but large code blocks, the full style config, and duplicate decision/type tables are all inlined, and links point to shared-references/*.md files that are not present as bundle files; not a 4 because content that belongs in separate files stays inline and references are not clearly resolvable.

3 / 5

Total

14

/

20

Passed

Description

87%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.

The description is strong: it concisely pairs a concrete capability statement with explicit, multilingual trigger phrases, fully answering both what and when. Minor specificity gains are possible by acknowledging the LaTeX-snippet and review steps it performs.

DimensionReasoningScore

Specificity

Names the domain (figures and tables from experiment results) and several concrete actions (generate figures, generate tables); falls short of 5 because it omits adjacent actions it actually performs such as emitting LaTeX include snippets and running a Gemini review.

4 / 5

Completeness

Explicitly states what it does ("Generate publication-quality figures and tables from experiment results") and when to use it with concrete trigger phrases ("Use when user says..."), matching the anchor-5 example; not below 5 since both what and when are concrete.

5 / 5

Trigger Term Quality

Covers natural triggers across two languages ("画图", "作图", "generate figures", "paper figures", "needs plots for a paper"); not a 5 because some common phrasings (e.g. "make plots", "plot results") and extension-style triggers are absent.

4 / 5

Distinctiveness Conflict Risk

Targets a clear niche (publication figures/tables from experiment data) with distinctive multilingual triggers, minimizing overlap with other skills; no neighbor anchor fits better.

5 / 5

Total

18

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 3 suspicious

Warning

Total

15

/

16

Passed

Repository
wanshuiyin/Auto-claude-code-research-in-sleep
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.