CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

container-queries

Use when reviewing stylesheets, component styles, and responsive behavior related to Use container queries for component-level responsiveness. Check the rendered layout across breakpoints and interaction states before proposing a fix.

Quality

73%

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/container-queries/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.

The SKILL.md body is a well-structured overview with excellent one-level-deep progressive disclosure into references/rule.md, and it names the exact CSS APIs to use. Its weaknesses are a duplicated concept-explanation paragraph that wastes tokens and a Check/Fix workflow that omits the verification checkpoints relegated to the reference file.

Suggestions

Delete or compress the opening "Media queries respond to viewport width..." paragraph — it re-teaches a concept Claude already knows and is duplicated verbatim as "Why It Matters" in references/rule.md.

Add a brief validation step to the body's workflow (e.g. after Fix: "Verify the rendered layout at the affected container breakpoints, per the Verification section in references/rule.md") so checkpoints are explicit rather than implicit.

Make the reference pointer a markdown link and note what each part of rule.md covers (code examples, named containers, container units, support notes, verification) so navigation is fully self-describing.

DimensionReasoningScore

Conciseness

The opening paragraph "Media queries respond to viewport width, which makes components context-dependent..." explains a concept Claude already knows and is duplicated verbatim as "Why It Matters" in references/rule.md, and the Quick Reference bullets partly restate the same points. Mostly efficient, but this redundant explanation is a clear trim target — below anchor 4, well above anchor 2.

3 / 5

Actionability

Concrete, executable guidance is present: "Set container-type: inline-size on the parent", "Use @container rule", and "Convert this component from media query-based to container query-based responsiveness using container-type and @container" name the exact CSS APIs. Not 5 because the body itself contains no code example — the executable examples are deferred to references/rule.md, leaving a minor gap for the inline guidance.

4 / 5

Workflow Clarity

The Check → Fix → Explain → Code Review sections present a coherent sequence, but validation checkpoints are absent from the body — the rendered-UI verification steps exist only in references/rule.md's "Verification" section. The sequence is present but checkpoints are implicit, matching anchor 3 rather than 4.

3 / 5

Progressive Disclosure

The body is a clean ~30-line overview with clear section headers and a single well-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 exactly the promised implementation detail. Content is appropriately split between overview and reference.

5 / 5

Total

15

/

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.

The description has an explicit 'Use when' trigger and a distinct container-queries niche, but the capability statement is weakened by the awkwardly embedded rule title "related to Use container queries for component-level responsiveness" and a thin action list. It reads as a templated review-skill description rather than a purpose-built one.

Suggestions

Rewrite the phrase "related to Use container queries for component-level responsiveness" into a natural capability statement, e.g. "Review CSS for viewport-locked media queries and convert components to container queries (@container / container-type) so they adapt to their own container's size."

Add the trigger synonyms users would naturally type — "@container", "container-type", "media query alternative" — so the skill fires on the vocabulary people actually use.

State the concrete actions performed (convert media-query breakpoints to @container rules, set container-type: inline-size on parents, verify rendered layout at container breakpoints) instead of one generic 'check the rendered layout' action.

DimensionReasoningScore

Specificity

Concrete actions are limited to "reviewing stylesheets, component styles, and responsive behavior" and "Check the rendered layout across breakpoints and interaction states before proposing a fix" — the domain is named with only 1-2 actions, and the clause "related to Use container queries for component-level responsiveness" is a pasted rule title rather than an action. It falls at anchor 3, not 4, because it does not list several distinct specific actions.

3 / 5

Completeness

An explicit "when" is present ("Use when reviewing stylesheets, component styles, and responsive behavior...") and a "what" is stated ("Check the rendered layout across breakpoints and interaction states before proposing a fix"). Not 5 because the "what" is thin and circular — the capability is defined only by the embedded rule title "Use container queries for component-level responsiveness".

4 / 5

Trigger Term Quality

Good natural keyword coverage: "stylesheets", "component styles", "responsive behavior", "breakpoints", "interaction states", plus the topic term "container queries". Not 5 because common synonyms users would say are missing ("@container", "container-type", "media queries", "CSS").

4 / 5

Distinctiveness Conflict Risk

The anchor "container queries for component-level responsiveness" carves a clear niche with minimal conflict risk. Not 5 because the generic boilerplate "reviewing stylesheets, component styles, and responsive behavior" overlaps with sibling CSS review skills that share the same template phrasing.

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/container-queries/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.