CtrlK
BlogDocsLog inGet started
Tessl Logo

time-svg-creator

Creates an SVG time card showing the current time for Dubai. Writes the SVG to agent-teams/output/dubai-time.svg and updates agent-teams/output/output.md.

56

Quality

66%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./agent-teams/.claude/skills/time-svg-creator/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

65%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is concise and well-structured for a simple skill, but its actionability and navigation are undermined because the referenced bundle files (reference.md, examples.md) are not present. Adding the missing references (or inlining the SVG/markdown templates) would resolve the main gaps.

Suggestions

Provide the missing reference.md (SVG template, output template, design specs) and examples.md, or inline the templates directly in SKILL.md.

Add an explicit validation step (e.g. verify the written SVG is self-contained and parses) after writing the output files.

Specify the placeholder names in the SVG template so the 'replacing placeholders' instruction is unambiguous even without opening the reference.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence — it states the task, three numbered steps, and constraints without explaining SVG or markdown concepts Claude already knows. Not score 2 because there is no padded or unnecessary explanation to tighten.

3 / 3

Actionability

Output paths are concrete, but the core 'Create SVG' step defers to 'the SVG template from reference.md' which is not bundled (no references/ directory, file absent), leaving the actual SVG construction unspecified. Not score 1 because concrete file targets and rules are given; not score 3 because the key creation step relies on a missing, non-executable reference.

2 / 3

Workflow Clarity

The three steps (create SVG, write SVG, write summary) are clearly sequenced, but there are no explicit validation/verification checkpoints and the first step depends on a missing template. Not score 3 because checkpoints are absent/implicit; not score 1 because the sequence itself is unambiguous.

2 / 3

Progressive Disclosure

The body is well organized into Task/Instructions/Rules/Additional resources and signals one-level-deep references to reference.md and examples.md, but those referenced files do not exist in the bundle, so navigation fails. Not score 3 because 'easy navigation' is broken by the dangling references; not score 1 because the structure and signaling themselves are clean and shallow.

2 / 3

Total

9

/

12

Passed

Description

67%

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 distinctive, clearly stating what the skill does and where it writes output. Its main weakness is the absence of any 'Use when...' trigger guidance and limited natural trigger-term coverage.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user asks for a visual time card or clock image for Dubai.'

Broaden trigger terms to include natural phrasings like 'time card', 'clock image', or 'Dubai time'.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'Creates an SVG time card', 'Writes the SVG to agent-teams/output/dubai-time.svg', 'updates agent-teams/output/output.md' — matching the multiple-specific-actions anchor. Not score 2 because it goes beyond naming a domain to enumerating distinct operations.

3 / 3

Completeness

Clearly states what the skill does but provides no 'Use when...' clause or equivalent trigger guidance, so per the rubric cap completeness is held at 2. Not score 3 because the 'when' is entirely missing rather than explicit.

2 / 3

Trigger Term Quality

Contains some natural terms ('SVG time card', 'current time for Dubai') but lacks common variations (e.g. 'time card', 'clock', 'Dubai time') and has no usage context. Not score 3 because coverage of naturally-said keywords is thin; not score 1 because the terms present are user-relevant rather than jargon.

2 / 3

Distinctiveness Conflict Risk

The narrow niche — an SVG time card specifically for Dubai — is highly specific and unlikely to conflict with other skills. Not score 2 because the domain is far more constrained than 'works with document files'.

3 / 3

Total

10

/

12

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

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

Warning

relative_links

Relative link issues: 4 missing

Warning

Total

14

/

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.