CtrlK
BlogDocsLog inGet started
Tessl Logo

weather-svg-creator

Creates an SVG weather card showing the current temperature for Dubai. Writes the SVG to orchestration-workflow/weather.svg and updates orchestration-workflow/output.md.

60

Quality

70%

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 ./.claude/skills/weather-svg-creator/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

71%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 well-organized, concise, and gives concrete file-writing steps, but it depends on reference.md and examples.md for its templates and examples, and those bundle files are absent, undermining both actionability and navigation.

Suggestions

Provide the referenced bundle files (reference.md with the SVG/markdown templates and design specs, and examples.md with input/output pairs) so the links resolve.

Name the specific placeholders in the SVG template that must be replaced (e.g. {{temperature}}, {{unit}}, {{city}}) instead of the generic 'replacing placeholders with actual values'.

Add an explicit validation step such as 'Verify the SVG parses and renders the temperature and unit correctly before finishing' to turn the 'valid' rule into a checkpoint.

DimensionReasoningScore

Conciseness

The body is lean with no concept over-explanation, but the opening line restates the Task section ('Create an SVG weather card and write both the SVG and a markdown summary'), a minor redundancy that could be trimmed.

4 / 5

Actionability

Steps are concrete with explicit output paths ('orchestration-workflow/weather.svg', 'orchestration-workflow/output.md'), but the actual templates live in reference.md and 'replacing placeholders' does not name which placeholders, leaving minor gaps.

4 / 5

Workflow Clarity

A clear numbered 3-step sequence (create, write SVG, write summary) for a simple skill, with 'The SVG must be self-contained and valid' as a rule, but there is no explicit validation checkpoint to confirm the SVG is valid before finishing.

4 / 5

Progressive Disclosure

Section structure is clean and references to reference.md and examples.md are clearly signaled at one level deep, but no references/ or assets/ bundle directories exist, so the linked files are missing and navigation breaks.

3 / 5

Total

15

/

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.

The description is concrete and narrowly scoped with clear output targets, but it omits any 'Use when...' trigger guidance, which caps its completeness and limits its usefulness for skill selection.

Suggestions

Add an explicit 'Use when...' clause naming natural triggers, e.g. 'Use when the user asks for a weather card, temperature visualization, or an SVG showing Dubai's current temperature.'

Include the .svg file extension and a synonym or two (e.g. 'weather graphic', 'temperature card') to broaden trigger-term coverage.

Reconsider whether three near-identical restatements of the task across description, header, and Task section are needed; consolidate to reduce redundancy.

DimensionReasoningScore

Specificity

Lists three concrete actions with explicit output paths ('Creates an SVG weather card', 'Writes the SVG to orchestration-workflow/weather.svg', 'updates orchestration-workflow/output.md'), matching the several-specific-actions anchor without reaching comprehensive coverage.

4 / 5

Completeness

The 'what' is clearly stated but there is no 'Use when...' clause or equivalent trigger guidance, which per the guidelines caps completeness at 3.

3 / 5

Trigger Term Quality

Natural terms a user would say are present ('SVG weather card', 'temperature for Dubai'), giving good keyword coverage, but synonyms and the .svg file extension are missing so it stops short of comprehensive.

4 / 5

Distinctiveness Conflict Risk

The niche is very specific — an SVG weather card for Dubai's temperature with named output paths — giving it distinct triggers and minimal conflict risk with other skills.

5 / 5

Total

16

/

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: 4 missing

Warning

Total

15

/

16

Passed

Repository
shanraisshan/claude-code-best-practice
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.