CtrlK
BlogDocsLog inGet started
Tessl Logo

number-details

Add decorative 01, 02, 03 numeric detail markers.

62

Quality

73%

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 ./agent-skills/web-design/number-details/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

92%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 an exemplary lean, well-structured instruction-only skill: concise, concrete about format, placement, and typography, with explicit use-when and guardrail sections. Its only real gap is the absence of a concrete example (snippet or specimen layout) that would make the visual pattern immediately reproducible.

DimensionReasoningScore

Conciseness

The ~21-line body is lean with no padding and no explanation of concepts Claude already knows; each line adds non-obvious guidance (positions, typography treatment, guardrails). It matches the "every token earns its place" anchor rather than the anchor 4 example of content that could be trimmed.

5 / 5

Actionability

Guidance is concrete and executable for an instruction-only skill: "two-digit numbers such as 01, 02, 03", "card corners, section gutters, timeline rails, or beside headings", "mono or narrow uppercase typography with low contrast". Not a 5 because there is no copy-paste-ready example (e.g., a sample markup/CSS snippet or a rendered example) covering the common case.

4 / 5

Workflow Clarity

This is a simple single-task skill under 50 lines, and the single action is unambiguous: the five workflow steps plus a Use When section and guardrails make application criteria explicit. No validation loop is required since nothing destructive or batch-oriented is involved, so the simple-skill exception applies.

5 / 5

Progressive Disclosure

For a skill under 50 lines with no need for external references, well-organized sections suffice: Use When, Workflow, and Guardrails are cleanly separated and no inlined content belongs in a separate file, and no bundle files exist to reference.

5 / 5

Total

19

/

20

Passed

Description

53%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 concise and concrete about what the skill does, but it omits any explicit "Use when..." trigger guidance and offers only thin keyword coverage for how users would naturally request this. It is distinct enough to avoid most conflicts, yet it reads as a bare capability statement rather than a complete triggering description.

Suggestions

Append an explicit trigger clause, e.g. "Use when the user wants 01/02/03-style step markers, numbered card corners, or editorial numbering details."

Include natural synonyms and phrasings users would actually say ("numbered detail", "step markers", "section numbering") to broaden trigger-term coverage.

Optionally mention the contexts it serves (cards, timelines, process sections) in the description so the "what" and "when" are both fully explicit.

DimensionReasoningScore

Specificity

"Add decorative 01, 02, 03 numeric detail markers" names the domain and one concrete action with a specific format, but lists only a single action rather than several specific capabilities. Not a 4 because there are no additional actions to cover minor gaps; not a 2 because the action named is concrete, not generic.

3 / 5

Completeness

The "what" is clear (add decorative two-digit numeric detail markers), but there is no "Use when..." clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines. Not a 2 because the "what" half is concrete and specific.

3 / 5

Trigger Term Quality

Terms like "numeric detail markers", "01, 02, 03", and "decorative" are relevant and somewhat natural, but common variations users might say (e.g., "numbering", "step numbers", "editorial numbering", "index markers") are missing. Not a 4 because keyword coverage is thin for such a short description.

3 / 5

Distinctiveness Conflict Risk

The decorative-numbering niche is fairly distinctive and unlikely to trigger the wrong skill, with only minor overlap risk against closely related skills like numbered-list or section-numbering helpers. Not a 5 because "numeric detail markers" could plausibly collide with general numbering/annotation skills.

4 / 5

Total

13

/

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
MengTo/Skills
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.