CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

css-containment

Use when reviewing stylesheets, component styles, and responsive behavior related to Use CSS containment to limit repaint scope. Check the rendered layout across breakpoints and interaction states before proposing a fix.

Quality

71%

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

Quality

Content

63%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 a well-organized overview with an appropriately signaled single one-level-deep reference, but it opens with a concept explanation Claude already knows and defers all executable CSS to the reference file, leaving the fix guidance concrete in naming yet incomplete in executable detail.

Suggestions

Delete or compress the opening concept explanation ('By default, a CSS change anywhere on the page...') — Claude already knows what CSS containment is; keep only rule-specific framing.

Add one small executable CSS snippet to the Fix section (e.g., '.widget { contain: content; }' and 'ul li { content-visibility: auto; contain-intrinsic-size: auto 500px; }') so the body handles the common case without loading the reference.

Add an explicit post-fix validation step — re-check the rendered layout at each breakpoint after applying contain, since size containment can break element dimensions.

DimensionReasoningScore

Conciseness

The opening paragraph ('By default, a CSS change anywhere on the page can potentially affect any other element's layout. CSS containment declares that certain elements are isolated...') explains a concept Claude already knows, which is more than a minor instance of over-explanation. The remaining sections are tight, so this sits at anchor 3 rather than 4 or 2.

3 / 5

Actionability

Concrete guidance exists ('Add appropriate contain values to self-contained components. Add content-visibility: auto to repeated off-screen list items') plus identification criteria ('no overflow, no interaction with elements outside'), but the body contains no executable CSS example — code lives only in references/rule.md. Some concrete guidance, incomplete in the body itself, matches anchor 3; it is above anchor 2 because specific declarations and criteria are given.

3 / 5

Workflow Clarity

A clear Check → Fix → Explain → Code Review sequence runs identify-before-fix, and the Code Review section directs flagging 'exact selectors, declarations, or breakpoints that violate the rule in the rendered UI'. The gap is no explicit post-fix validation that containment didn't break layout, so it fits anchor 4's 'minor validation gaps' rather than anchor 5.

4 / 5

Progressive Disclosure

'For full implementation details, code examples, and framework-specific guidance, see references/rule.md' is a clearly signaled, one-level-deep reference to a verified real file containing the full code examples, and the body is a well-organized overview (Quick Reference / Check / Fix / Explain / Code Review). This matches the top anchor: clear overview, appropriate split, easy navigation.

5 / 5

Total

15

/

20

Passed

Description

66%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 clause and good natural keywords, but its capability statement is process-generic and the distinctive containment content appears only as an awkwardly embedded rule title, creating overlap risk with sibling CSS review skills.

Suggestions

State the skill's concrete capabilities explicitly (e.g., 'Flags selectors missing contain or content-visibility and proposes containment values to limit repaint scope') instead of only describing the review process.

Lead with distinctive trigger terms (CSS containment, contain property, content-visibility, repaint/reflow performance) rather than the generic 'reviewing stylesheets' prefix likely shared with sibling rule skills.

Rewrite the embedded rule title 'related to Use CSS containment to limit repaint scope' into natural trigger phrases a user would actually say.

DimensionReasoningScore

Specificity

Names the domain ('stylesheets, component styles, and responsive behavior') and a couple of concrete actions ('Check the rendered layout across breakpoints and interaction states before proposing a fix'), but coverage is not comprehensive — the distinctive capability (applying contain values, content-visibility) is never stated. The listed actions are process-generic, so it fits anchor 3 better than anchor 4's 'several specific actions'.

3 / 5

Completeness

Both parts are present: an explicit 'when' ('Use when reviewing stylesheets, component styles, and responsive behavior related to...') and a process-implied 'what' ('Check the rendered layout across breakpoints and interaction states before proposing a fix'). The 'what' is never stated as a concrete capability (e.g., flagging containment violations and proposing contain fixes), so it falls short of anchor 5's clearly explicit both-parts standard.

4 / 5

Trigger Term Quality

Good natural keyword coverage: 'stylesheets', 'component styles', 'responsive behavior', 'CSS containment', 'repaint', 'breakpoints', 'interaction states'. A few natural terms are missing (reflow, rendering performance, contain property, content-visibility), matching anchor 4 rather than anchor 5's comprehensive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

The prefix 'reviewing stylesheets, component styles, and responsive behavior' is generic and would overlap with many sibling CSS review skills; only the embedded rule title 'Use CSS containment to limit repaint scope' distinguishes it. Somewhat specific but genuine overlap risk with closely related skills, matching anchor 3 rather than anchor 4's 'minor overlap risk'.

3 / 5

Total

14

/

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/css-containment/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.