CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

figure-legend-gen

Generate standardized figure legends for scientific figures and charts; use when preparing publication-ready legends that summarize design, variables, sample size, and key statistical notes.

Quality

68%

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 ./scientific-skills/Academic Writing/figure-legend-gen/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

53%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 core usage guidance (CLI, parameters, examples, legend structure, well-split references) is concrete and executable, but the body is bloated with redundant governance boilerplate and the workflow lacks integrated validation checkpoints. Trimming the policy sections and sequencing verification into the workflow would materially raise quality.

Suggestions

Cut the generic governance sections (Risk Assessment, Security Checklist, Lifecycle Status, Evaluation Criteria, Required Inputs, Output Contract, User Checkpoints) and merge the three overlapping error-handling sections ('Workflow' step 5, 'Error Handling', 'Failure Handling') into one concise section — this alone would remove well over half the body.

Embed validation as sequenced workflow steps (e.g., step 0: 'python -m py_compile scripts/main.py'; after generation: verify the legend contains title, n, statistics, scale bar where applicable) instead of scattering it across 'Quick Check' and 'Quick Validation'.

Fix the broken third example ('python scripts/main.py --image.png --type scatter' is missing '--input') and either bundle a requirements.txt or replace the 'pip install -r requirements.txt' prerequisite with the actual dependency list (PIL, pytesseract).

DimensionReasoningScore

Conciseness

Roughly half the body is generic skill-governance boilerplate (Risk Assessment, Security Checklist, Lifecycle Status, Evaluation Criteria, Required Inputs, Output Contract, User Checkpoints) with the same error-handling policy repeated across 'Workflow' step 5, 'Error Handling', and 'Failure Handling', plus a duplicated 'python scripts/main.py --help' command. It never explains concepts Claude already knows, so it is above 1, but it is well below the 'mostly efficient' bar of 3.

2 / 5

Actionability

The Usage section provides an executable command, a complete parameter table, and concrete examples, and the Legend Structure plus real reference files give concrete output guidance. Not 5 because one example is broken ('python scripts/main.py --image.png --type scatter' is missing '--input') and Prerequisites references a requirements.txt that is not in the bundle.

4 / 5

Workflow Clarity

The 5-step Workflow lists a sequence including an explicit fallback step, but validation checkpoints are scattered across disconnected sections ('Quick Check', 'Quick Validation') rather than sequenced into the workflow, matching the 'steps listed but checkpoints implicit' anchor. Not 4 because no workflow step embeds a verify-and-proceed gate like the 4-anchor example.

3 / 5

Progressive Disclosure

The bundle split is genuinely good: legend templates and the academic style guide live in real one-level-deep reference files that are clearly listed in a References section, and the script is properly external. Not 5 because the SKILL.md overview itself carries 100+ lines of policy content that dilutes navigation and the references are listed at the end rather than signaled at point of use.

4 / 5

Total

13

/

20

Passed

Description

70%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 solid description with a clear what/when pair and natural trigger language for a well-defined niche. Its main limitation is single-action coverage and the absence of common synonyms like 'captions' that would sharpen triggering.

DimensionReasoningScore

Specificity

Names the domain ('scientific figures and charts') and one concrete action ('Generate standardized figure legends'); the clause about summarizing 'design, variables, sample size, and key statistical notes' describes output content rather than additional actions. Not 4 because it does not list several distinct actions like the 4-anchor examples do.

3 / 5

Completeness

Explicitly answers both 'what' ('Generate standardized figure legends for scientific figures and charts') and 'when' ('use when preparing publication-ready legends...'). Not 5 because the when-clause lacks concrete trigger phrases like 'or when the user mentions figure captions or axis labels', matching the 4-anchor example's level of explicitness.

4 / 5

Trigger Term Quality

Natural phrases a user would say are present: 'figure legends', 'scientific figures', 'charts', 'publication-ready legends'. Not 5 because common synonyms such as 'captions', 'panel labels', or figure-file extensions are missing.

4 / 5

Distinctiveness Conflict Risk

The publication-figure-legend niche is clearly distinct with domain-specific triggers. Not 5 because 'scientific figures and charts' has minor overlap risk with general academic-writing or chart-creation skills.

4 / 5

Total

15

/

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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

Repository

aipoch/medical-research-skills

Path

scientific-skills/Academic Writing/figure-legend-gen/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.