CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.

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 ./skills/reset-css/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

57%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-structured with exemplary progressive disclosure — a lean overview deferring cleanly to a real references/rule.md — but the substance is thin: three of four sections restate the same concept, executable detail (the import statement, fix code) is deferred without inline basics, and the check→fix workflow lacks a verification step. It reads more like a rule summary card than operational guidance.

Suggestions

Replace the vague Fix section with executable guidance: show the import ('import \"normalize.css\";' or '@import') alongside the existing pnpm install command, and note where it must load relative to custom styles.

Add a post-fix verification step to the workflow, e.g. 'After applying, confirm rendered layout across Chrome/Firefox/Safari/Edge at key breakpoints before considering the fix done' — currently the check-then-fix sequence has no validation checkpoint.

Collapse the redundant intro/Check/Explain restatements of 'resets eliminate browser default inconsistencies' into one line; the freed tokens are better spent on the concrete import and verification details.

DimensionReasoningScore

Conciseness

The body is short overall, but the intro sentence, '## Check', '## Fix', and '## Explain' sections all restate the same browser-consistency concept Claude already knows, and '## Explain' ('Explain how CSS resets eliminate browser default styles...') is pure padding. Not 2 because the total token footprint is lean and there is no extended tutorial prose — the issue is repeated restatement, not volume.

3 / 5

Actionability

Some concrete guidance exists ('Install with pnpm: `pnpm add normalize.css`', 'Choose normalize.css for preservation or modern reset for clean slate', 'Check if your CSS framework includes a built-in reset'), but the 'Import before your custom styles' step lacks the actual import statement and the Fix section stays at the 'Implement a modern CSS reset like...' level with no code in the body. Not 4 because key steps are not executable as written.

3 / 5

Workflow Clarity

A rough Check→Fix sequence is implied by the section order, but there is no post-fix verification step in the body — the 'check the rendered layout across breakpoints' guidance appears only in the description, not in the workflow. Not 4 because checkpoints are missing or implicit rather than present with minor gaps.

3 / 5

Progressive Disclosure

A lean, well-sectioned overview under 50 lines with a single clearly-signaled, one-level-deep reference ('For full implementation details, code examples, and framework-specific guidance, see `references/rule.md`'), and that file exists and delivers the promised code examples. Content is appropriately split between the overview and the reference.

5 / 5

Total

14

/

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.

A serviceable description with an explicit use-when clause and domain-appropriate trigger terms, but it suffers from a templated duplication ('related to Use a CSS reset or normalize stylesheet') that garbles the capability statement, and it never states the skill's core action of applying a reset. The trigger scope is also broad enough to risk overlap with other CSS review skills.

Suggestions

State the core capability explicitly and separately from the when-clause, e.g. 'Implements or recommends a CSS reset/normalize stylesheet (normalize.css, CSS Remedy, or custom) and flags missing resets during stylesheet review.'

Fix the duplicated templated phrase 'related to Use a CSS reset or normalize stylesheet' — it reads as a generation artifact and obscures both the what and the trigger.

Add natural trigger synonyms such as 'cross-browser consistency', 'browser default styles', or 'styles look different across browsers' to broaden keyword coverage.

DimensionReasoningScore

Specificity

Names concrete actions ('reviewing stylesheets, component styles, and responsive behavior', 'Check the rendered layout across breakpoints and interaction states before proposing a fix') but coverage is incomplete — the core capability of applying/implementing a reset is never stated — and the templated duplication 'related to Use a CSS reset or normalize stylesheet' muddles the action statement. Not 4 because the gaps go beyond minor: a key action is missing and the sentence structure is garbled.

3 / 5

Completeness

An explicit 'Use when...' clause is present ('Use when reviewing stylesheets, component styles, and responsive behavior...') and a what-ish action is given ('Check the rendered layout... before proposing a fix'). Not 5 because the what is never cleanly separated from the when and the skill's primary action (implement/apply a reset) is only implied via the awkward 'related to Use a CSS reset or normalize stylesheet' fragment; not 3 because both elements are explicitly present.

4 / 5

Trigger Term Quality

Good natural keyword coverage within the CSS domain: 'stylesheets', 'component styles', 'responsive behavior', 'breakpoints', 'interaction states', 'CSS reset', 'normalize stylesheet'. Not 5 because common variations users would say — 'cross-browser consistency', 'browser default styles', 'browser inconsistencies' — are absent.

4 / 5

Distinctiveness Conflict Risk

The 'CSS reset or normalize stylesheet' niche with 'breakpoints' and 'interaction states' triggers is mostly distinct from unrelated skills. Not 5 because the broad lead-in 'reviewing stylesheets, component styles, and responsive behavior' overlaps with sibling CSS/responsive-review checklist skills.

4 / 5

Total

15

/

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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository

thedaviddias/Front-End-Checklist

Path

skills/reset-css/SKILL.md

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.