CtrlK
BlogDocsLog inGet started
Tessl Logo

figure-style

Apply scientific plotting and figure-quality rules to a single plot or panel. Use when drawing, cleaning, labeling, or reviewing plots for research artifacts.

67

Quality

81%

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

SKILL.md
Quality
Evals
Security

Quality

Content

78%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 tight, well-organized checklist that is maximally token-efficient and clearly sequenced for a simple, non-destructive task. Its weakness is actionability: it states principles rather than providing executable code or concrete parameters that would make the guidance directly applicable.

Suggestions

Add a short executable code snippet (e.g. matplotlib savefig with dpi and bbox_inches) to anchor the labeling/saving steps in concrete practice.

Optional: include one-line guidance on accessibility checks (e.g. colorblind-safe palettes, font sizes) to lift the color/labeling steps from principle to actionable rule.

DimensionReasoningScore

Conciseness

The body is a lean ~10-line checklist that assumes Claude's competence and adds only figure-specific guidance Claude would not reliably infer; every line earns its place with no concept padding.

5 / 5

Actionability

Guidance is concrete in intent ('Label axes with units', 'Use color only for meaningful grouping') but provides no executable code, commands, or specific parameters; it instructs at a principle level rather than giving copy-paste-ready steps.

3 / 5

Workflow Clarity

The five-step checklist is a clear, ordered sequence (pick type, label, color, render-and-inspect, save) with an implicit inspection checkpoint in step 4; it lacks an explicit validate/retry feedback loop but is well-sequenced for a non-destructive task.

4 / 5

Progressive Disclosure

A short, single-purpose skill with no bundle files and no need for external references; the content is well-organized into a titled section and numbered checklist, satisfying the simple-skill exception for progressive disclosure.

5 / 5

Total

17

/

20

Passed

Description

83%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 concise, third-person description that answers both what and when with concrete trigger actions. It is well-scoped to a clear niche with low conflict risk; the main improvement would be adding more natural synonyms (figure, chart) for broader trigger coverage.

Suggestions

Add common synonyms users say, e.g. 'figure', 'chart', 'axis labels', or 'legend', to broaden natural trigger coverage.

Consider mentioning the output artifact (e.g. publication-quality figures) to further sharpen distinctiveness from general charting skills.

DimensionReasoningScore

Specificity

Lists several concrete actions ('drawing, cleaning, labeling, or reviewing plots') with a clear domain (scientific plotting / figure-quality rules); minor gaps in coverage such as export formats or specific plot libraries keep it just below comprehensive.

4 / 5

Completeness

Clearly answers 'what' ('Apply scientific plotting and figure-quality rules to a single plot or panel') and 'when' ('Use when drawing, cleaning, labeling, or reviewing plots for research artifacts') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Includes natural user-facing terms ('plot', 'panel', 'drawing', 'cleaning', 'labeling', 'reviewing plots'), but misses common synonyms like 'figure', 'chart', 'axis labels', or 'legend' that users would naturally say.

4 / 5

Distinctiveness Conflict Risk

Scoped to 'a single plot or panel' and 'research artifacts' gives it a clear niche with minimal conflict risk, though it could still overlap slightly with general data-visualization or charting skills.

4 / 5

Total

17

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
companion-inc/feynman
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.