CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

styles-lint

Use when reviewing stylesheets, component styles, and responsive behavior related to Lint CSS and SCSS files. Check the rendered layout across breakpoints and interaction states before proposing a fix.

Quality

72%

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/styles-lint/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 skill body is well-structured for progressive disclosure, correctly keeping its 905-line detail file one reference away, but the in-body guidance is repetitive and lacks any executable commands, config examples, or validation steps. Consolidating the redundant setup sections and adding a lint command plus a verify step would materially improve it.

Suggestions

Remove the intro sentence explaining what CSS linting does (Claude already knows this) and merge the redundant setup guidance from Quick Reference, Check, and Fix into a single section.

Add at least one executable command (e.g., `npm install --save-dev stylelint stylelint-config-standard` and `npx stylelint "**/*.{css,scss}" --fix`) or a minimal .stylelintrc example instead of "Configure Stylelint with appropriate rules".

Add a validation checkpoint to the workflow, such as running stylelint after auto-fix and reviewing the diff before committing, since auto-fix is a batch modification of many files.

DimensionReasoningScore

Conciseness

The body is short but opens with a concept Claude already knows ("CSS linting catches syntax errors, enforces consistent coding standards, and prevents maintainability issues") and restates the same setup guidance three times across "Quick Reference", "Check" ("Set up CSS/SCSS linting tools like Stylelint"), and "Fix" ("Configure Stylelint with appropriate rules and integrate it into your build process"). Mostly efficient, but it could be tightened by consolidating these sections.

3 / 5

Actionability

It names concrete tools and integration points ("stylelint-config-standard", "stylelint-config-standard-scss", "pre-commit hooks", "CI/CD pipeline") but provides no executable commands or config examples — "Configure Stylelint with appropriate rules" is a high-level hint missing the specific steps. Some concrete guidance, but incomplete without the referenced rule.md.

3 / 5

Workflow Clarity

The Check/Fix/Explain/Code Review sections list a recognizable sequence, but no validation checkpoints exist (e.g., "run stylelint and confirm zero errors"). Because the skill enables auto-fix across stylesheets — a batch file-modifying operation — the missing feedback loop caps this at 3 per the batch-operations guideline.

3 / 5

Progressive Disclosure

The body is a lean overview that defers bulk detail to the clearly signaled, one-level-deep `references/rule.md` ("For full implementation details, code examples, and framework-specific guidance, see references/rule.md"), which exists in the bundle. Content is appropriately split and easy to navigate.

5 / 5

Total

14

/

20

Passed

Description

75%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 a solid, mostly-specific trigger: it names the domain (CSS/SCSS linting), includes an explicit "Use when" clause, and describes concrete review actions with rendered-layout checks. Its main weaknesses are burying the core linting capability inside the when-clause and omitting file-extension trigger terms.

Suggestions

Lead with the core capability in third-person/imperative form before the trigger clause, e.g., "Lints CSS and SCSS files with Stylelint and reviews rendered layout across breakpoints. Use when..."

Add file extensions and common synonyms as trigger terms (e.g., ".css", ".scss", "styles") to improve trigger-term coverage.

DimensionReasoningScore

Specificity

It lists several specific actions — "Lint CSS and SCSS files", "Check the rendered layout across breakpoints and interaction states", "reviewing stylesheets, component styles, and responsive behavior" — with minor gaps in coverage. It exceeds anchor 3 (more than 1-2 actions) but is not comprehensive enough for anchor 5, and the "reviewing ... related to" phrasing is awkward.

4 / 5

Completeness

Both are present: an explicit "Use when reviewing stylesheets, component styles, and responsive behavior" trigger plus a what-clause ("Check the rendered layout across breakpoints and interaction states before proposing a fix"). It is not anchor 5 because the core action (linting) is buried inside the when-clause rather than led with as a clear capability statement.

4 / 5

Trigger Term Quality

Good natural keyword coverage: "stylesheets", "CSS", "SCSS", "lint", "responsive", "breakpoints", "interaction states". A few natural terms are missing, such as the standalone word "style" and file extensions (.css, .scss), so it falls short of anchor 5's comprehensive synonym/extension coverage.

4 / 5

Distinctiveness Conflict Risk

CSS/SCSS linting is a mostly distinct niche with specific triggers, but "reviewing stylesheets, component styles, and responsive behavior" carries minor overlap risk with general frontend code-review skills. Not anchor 5 because the review-oriented framing could collide with broader review skills.

4 / 5

Total

16

/

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/styles-lint/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.