number-details

Add decorative 01, 02, 03 numeric detail markers.

Quality

70%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

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

Quality

Content

86%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 content is lean, well-structured, and gives concrete styling directives well suited to a simple decorative skill. The main gap is the absence of a concrete rendered markup or CSS example that would make the guidance directly copy-paste executable.

Suggestions

Add a short rendered markup/CSS snippet showing a marker in a card corner so the guidance is copy-paste ready.

Include a one-line verification cue (e.g. confirm markers do not visually compete with headings) to close the workflow with a checkpoint.

Optionally show a before/after pairing to make the 'secondary visual structure, not primary content' guardrail concrete.

Dimension	Reasoning	Score
Conciseness	The body is lean (~15 lines) with no padding and no over-explanation of concepts Claude already knows; every line earns its place. It is not 4 because there are no instances of over-explanation to trim.	5 / 5
Actionability	Concrete, specific guidance is given for an instruction-only skill (positions: 'card corners, section gutters, timeline rails'; typography: 'mono or narrow uppercase... low contrast'; format: 'two-digit numbers such as 01, 02, 03'). Not 5 because no rendered markup/CSS example is provided to make it copy-paste ready; not 3 because the directives are specific rather than abstract.	4 / 5
Workflow Clarity	Five steps are clearly sequenced and unambiguous, and the task is a non-destructive styling operation so the validation cap does not apply. Not 5 because no verification checkpoint is present, even though one is arguably unnecessary here; not 3 because the sequence is well-defined with no gaps.	4 / 5
Progressive Disclosure	The skill is under 50 lines, single-purpose, needs no external references, and is organized into clear 'Use When', 'Workflow', and 'Guardrails' sections, satisfying the simple-skill exception. No bundle files exist to verify, so structure alone is scored.	5 / 5
	Total	18 / 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 conveys a specific, distinctive purpose but lacks any 'Use when' trigger guidance, capping completeness and limiting trigger-term quality. Adding an explicit usage clause with natural user phrases would lift the weakest dimensions.

Suggestions

Append a 'Use when...' clause naming natural triggers, e.g. 'Use when adding numbered step, card, or section markers to layouts.'

Include common synonyms users say ('numbered markers', 'step numbers') alongside '01, 02, 03' to broaden trigger coverage.

Add a second concrete action verb (e.g. 'Add and align decorative 01, 02, 03 numeric detail markers') to raise specificity beyond a single action.

Dimension	Reasoning	Score
Specificity	Names a concrete, specific domain ('decorative 01, 02, 03 numeric detail markers') with one concrete action ('Add'). It is not 2 because the domain is specific rather than generic, and not 4 because only a single action is named rather than several.	3 / 5
Completeness	A clear 'what' is present ('Add decorative 01, 02, 03 numeric detail markers') but there is no 'Use when...' clause or equivalent trigger guidance, which per the guidelines caps completeness at 3. It is not 4 because 'when' is entirely absent rather than weakly implied.	3 / 5
Trigger Term Quality	Relevant keywords appear ('01, 02, 03', 'numeric', 'markers') but common natural variations users would say (e.g. 'numbered steps', 'step numbers') are missing. Not 2 because the keywords are domain-relevant, not 4 because coverage of natural phrasings is thin.	3 / 5
Distinctiveness Conflict Risk	The niche is narrow and distinct (decorative two-digit numeric markers), so overlap risk is low. Not 5 because the lack of an explicit trigger phrase leaves activation guidance slightly underspecified compared to the anchor example.	4 / 5
	Total	13 / 20 Passed

Validation

100%

Warnings & errors only

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
Path: agent-skills/web-design/number-details/SKILL.md
Commit: 321c769

Reviewed: 5 days ago

Table of Contents

Discovery Implementation Validation

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.