CtrlK
BlogDocsLog inGet started
Tessl Logo

reset-css

Use when reviewing stylesheets, component styles, and responsive behavior related to Use a CSS reset or normalize stylesheet. Check the rendered layout across breakpoints and interaction states before proposing a fix.

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.

The body is concise, well-structured, and uses progressive disclosure effectively with a single real reference file. Weaknesses are minor: a touch of concept re-explanation up top and the absence of an inline import code snippet or an explicit review feedback loop.

DimensionReasoningScore

Conciseness

Lean and sectioned with tight Quick Reference bullets; only the opening line re-explains a concept Claude already knows ('CSS resets eliminate browser default inconsistencies...'), keeping it just short of a 5.

4 / 5

Actionability

Concrete, executable guidance (named tools: normalize.css, CSS remedy; command 'pnpm add normalize.css'; 'Import before your custom styles') with minor gaps — no inline import code snippet, though it lives in the reference.

4 / 5

Workflow Clarity

Check/Fix/Explain/Code Review sections sequence a single-purpose review skill clearly, and 'Check the rendered layout across breakpoints and interaction states before proposing a fix' acts as a checkpoint, but there is no explicit validate→fix→retry loop.

4 / 5

Progressive Disclosure

A concise overview body with well-organized sections and one clearly signaled, one-level-deep pointer to the real references/rule.md file — exactly the intended structure.

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.

The description is concrete and explicitly paired with a 'Use when' trigger, covering what and when well. Its main weakness is trigger-term breadth — it omits the most natural synonyms ('CSS reset', 'normalize', 'cross-browser').

DimensionReasoningScore

Specificity

Lists several specific actions — 'reviewing stylesheets, component styles, and responsive behavior', 'Check the rendered layout across breakpoints and interaction states', 'before proposing a fix' — with only minor coverage gaps (no install/implement guidance).

4 / 5

Completeness

Explicitly answers both what (review/check/fix stylesheets and responsive layout) and when via a concrete 'Use when reviewing stylesheets...' trigger phrase.

5 / 5

Trigger Term Quality

Good natural keyword coverage ('stylesheets', 'component styles', 'responsive behavior', 'breakpoints', 'interaction states') but misses common synonyms like 'CSS reset', 'normalize', and 'cross-browser'.

4 / 5

Distinctiveness Conflict Risk

Clear CSS-reset/review niche with distinct triggers; only minor overlap risk with broader CSS or frontend-review skills.

4 / 5

Total

17

/

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

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository
thedaviddias/Front-End-Checklist
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.