CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

naming-conventions

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

Quality

68%

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/naming-conventions/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

65%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.

A well-structured overview body that appropriately defers implementation detail to a real, clearly signaled reference file. Its weaknesses are a padding-heavy intro paragraph explaining why conventions matter (known material) and a missing validation loop after the batch rename step.

Suggestions

Cut the opening paragraph's explanation of why naming conventions matter and the redundant Quick Reference bullet; keep only the .active → .button--active contrast as a one-line illustration.

Add a verification step after the Fix section, e.g. 'After renaming, search the codebase for remaining references to the old class names (templates, JS selectors, tests) before finishing', since renaming is a batch operation.

Include one inline before/after rename pair (e.g., .card.active → .card--active) in the Fix section so the pattern is immediately executable without opening the reference.

DimensionReasoningScore

Conciseness

The body is mostly tight, but the opening paragraph ('Without a naming convention, class names become a guessing game — does .active mean...') explains why naming conventions matter — a concept Claude already knows — and the Quick Reference bullet 'Consistent naming lets you understand a class's purpose without reading its styles' restates the same point. This is more than a minor trim, matching 'mostly efficient but includes some unnecessary explanation'.

3 / 5

Actionability

Concrete guidance throughout: 'Rename classes to follow BEM methodology: Block, Block__Element, Block--Modifier pattern', 'Use kebab-case for class names (not camelCase or snake_case)', and 'Namespace utility classes and JS hooks separately'. As an instruction-only skill, deferring executable examples to references/rule.md is acceptable, though the Fix section is a single formula line without one inline before/after rename example, so it falls short of fully copy-paste-ready.

4 / 5

Workflow Clarity

Check → Fix → Explain → Code Review is a recognizable sequence, but renaming classes across a stylesheet is a batch operation and there is no validation step after the Fix (e.g., searching for now-broken references to old class names or re-checking the rendered output). Per the rubric's cap on batch operations without validation, this cannot score above 3.

3 / 5

Progressive Disclosure

A concise ~30-line overview with clearly labeled sections and exactly one reference — 'For full implementation details, code examples, and framework-specific guidance, see references/rule.md' — which is well-signaled, one level deep, and verified to exist with full BEM CSS/HTML examples. Content is appropriately split between overview and detail.

5 / 5

Total

15

/

20

Passed

Description

58%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 has an explicit 'Use when' trigger and names its domain, but suffers from a garbled mid-sentence title paste ('related to Use consistent CSS naming conventions'), missing core trigger terms like 'class names' and 'BEM', and layout/breakpoint language that muddies what the skill actually does. It reads as a review-process instruction rather than a statement of the skill's capability.

Suggestions

Rewrite the trigger around the skill's core vocabulary, e.g. 'Use when reviewing or renaming CSS class names, applying BEM (Block__Element--Modifier), or auditing selectors for naming consistency.'

State the capability in third person up front ('Audits and renames CSS class names to a consistent BEM convention') instead of leading with the 'Use when' clause and a broken title paste.

Remove or reduce the 'rendered layout across breakpoints and interaction states' language — it belongs to responsive-design skills and raises conflict risk with unrelated layout skills.

DimensionReasoningScore

Specificity

The domain is named ('Use consistent CSS naming conventions') with a few stated actions ('reviewing stylesheets, component styles, and responsive behavior', 'Check the rendered layout across breakpoints and interaction states before proposing a fix'), but the actions are generic review-verbs and the layout-checking action is misaligned with the skill's actual capability of auditing and renaming class names. Not 4: the actions are neither specific to the skill's core work nor comprehensive; not 2: multiple actions and a named domain are present.

3 / 5

Completeness

Both parts are present: an explicit trigger ('Use when reviewing stylesheets, component styles, and responsive behavior...') and an action statement ('Check the rendered layout across breakpoints and interaction states before proposing a fix'). Not 5: the 'what' is garbled ('related to Use consistent CSS naming conventions') and its clearest action describes layout verification rather than the skill's actual capability; not 3: the 'when' clause is explicit, which anchor 3 excludes.

4 / 5

Trigger Term Quality

Relevant keywords are present ('stylesheets', 'component styles', 'CSS naming conventions', 'breakpoints'), but the most natural terms for this exact task — 'class names', 'BEM', 'selectors' — are absent, leaving common synonyms missing per the anchor. Not 4: the missing terms are the core vocabulary a user would actually say, not just a few peripheral additions.

3 / 5

Distinctiveness Conflict Risk

The naming-convention core is somewhat specific, but 'responsive behavior', 'rendered layout', and 'breakpoints' language overlaps heavily with responsive-design and layout-review skills, risking mis-triggers for layout tasks unrelated to naming. Not 4: the overlap is more than minor since the second sentence is almost entirely about layout verification.

3 / 5

Total

13

/

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/naming-conventions/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.