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

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/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.

A genuinely actionable skill body with executable code and a well-sequenced, validated workflow, weakened by duplication and injected reviewer-routing boilerplate that pad the token budget. The single-file monolith structure and a broken external reference leave organization room for improvement.

Suggestions

Delete the Figure Type Reference table (it duplicates the Step 3 decision tree) and merge Key Rules into the Step 8 checklist so vector-PDF and no-title rules are stated once.

Move the reviewer-routing blockquote (or all of Step 7's routing detail) into a separate reference file and fix or remove the ../shared-references/reviewer-backends.md link, which points at a file not in the bundle.

Add an explicit error-recovery loop to Step 5 (e.g., "if a render fails the self-check, fix the script and re-run it") to upgrade the workflow's feedback loop.

DimensionReasoningScore

Conciseness

The bulk is efficient, concrete material (style config, per-figure scripts, bash loop), but there is clear waste: the Figure Type Reference table duplicates the Step 3 decision-tree table, Key Rules restate Step 8 checklist items (vector PDF and no-titles-inside-figures each appear twice), and the reviewer-routing blockquote is process boilerplate unrelated to figure generation. Fits "mostly efficient but could be tightened"; not 2 because the padding is a minority of tokens.

3 / 5

Actionability

Concrete executable guidance throughout: a complete paper_plot_style.py, a copy-paste line-plot script, a bash run loop, LaTeX table and include snippets. Minor gaps: the bar-chart snippet lacks its script header/imports, and scatter/heatmap/box-plot types get prose-table treatment only — fits "mostly executable with minor gaps" rather than fully comprehensive.

4 / 5

Workflow Clarity

An explicit 8-step sequence with real checkpoints: verify outputs exist and are non-empty (Step 5), render-then-verify on the rendered PDF/PNG before review, and a partitioned correctness/guidance checklist (Step 8). Not 5 because there is no explicit on-failure recovery loop ("if check fails → fix script → re-run") and Step 7 is muddied by the injected reviewer-routing text.

4 / 5

Progressive Disclosure

A well-headered single file (~320 lines) with no bundle files at all, and its one external link (../shared-references/reviewer-backends.md) is dangling within this bundle. Content like the duplicate Figure Type Reference table and the extended checklist could live in reference files — fits "some structure but could be better organized"; the clear headers keep it above 2.

3 / 5

Total

14

/

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 that clearly states a concrete capability and gives explicit bilingual trigger phrases for when to use it. The main gaps are modest action coverage and a few missing natural trigger synonyms.

Suggestions

Enumerate the main deliverables (e.g., line/bar/scatter/heatmap plots, multi-panel figures, LaTeX comparison tables) to raise specificity.

Add a few natural trigger variations such as "make charts", "visualize experiment results", or "comparison tables" to broaden keyword coverage.

DimensionReasoningScore

Specificity

Names the domain ("figures and tables from experiment results") and the concrete actions "Generate publication-quality figures and tables", matching the anchor for domain plus 1-2 concrete actions. It does not list several specific actions (plot types, LaTeX table generation, multi-panel figures), so it falls short of the 4 anchor.

3 / 5

Completeness

Explicitly answers both what ("Generate publication-quality figures and tables from experiment results") and when ("Use when user says '画图', '作图', 'generate figures', 'paper figures', or needs plots for a paper") with concrete trigger phrases — a direct match to the top anchor.

5 / 5

Trigger Term Quality

Good natural keyword coverage with bilingual synonyms: "画图", "作图", "generate figures", "paper figures", "needs plots for a paper" — phrases users would naturally say. Not a 5 because common variations like "make charts", "visualize results", or "tables" are missing.

4 / 5

Distinctiveness Conflict Risk

The paper/publication framing ("publication-quality", "paper figures", "plots for a paper") carves a clear niche distinct from general document or data skills. Generic triggers like "画图" could overlap with general plotting/dataviz skills, so minor overlap risk remains — the 4 anchor fits; not 5.

4 / 5

Total

16

/

20

Passed

Validation

81%

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

Validation — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

relative_links

Relative link issues: 1 suspicious

Warning

Total

13

/

16

Passed

Repository

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

Path

skills/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.