CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

css-grid

Use when reviewing stylesheets, component styles, and responsive behavior related to Use CSS Grid for two-dimensional layouts. Check the rendered layout across breakpoints and interaction states before proposing a fix.

Quality

84%

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

SKILL.md
Quality
Evals
Security

Quality

Content

78%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, brief rule body with a clean Check/Fix/Explain/Code Review organization and exemplary reference splitting to references/rule.md. The main improvement opportunities are trimming the conceptual intro, inlining one minimal conversion example, and surfacing the post-fix verification cue that currently lives only in the reference file.

Suggestions

Trim the opening 'why it matters' paragraph — CSS Grid's purpose is knowledge Claude already has, and references/rule.md's 'Why It Matters' section already covers the motivation.

Inline one minimal before/after snippet (a Flexbox row-and-column workaround next to its grid-template-areas replacement) so the Fix section is executable without opening the reference.

Add a post-fix validation cue in the body (e.g., 'after converting, re-check the rendered layout across breakpoints') mirroring the Verification section in references/rule.md.

DimensionReasoningScore

Conciseness

The 45-line body is lean overall — Quick Reference is terse bullets and Check/Fix/Explain are one to two sentences each — but the opening paragraph ('CSS Grid solves layout problems that previously required JavaScript or complex CSS hacks...') and parts of Quick Reference restate CSS fundamentals Claude already knows, and the 'why' content duplicates rule.md's 'Why It Matters' section. Not 5 because of that trimmable intro; not 3 because the padding is a single short paragraph in an otherwise efficient body.

4 / 5

Actionability

Check gives a concrete detection pattern ('Look for float-based or Flexbox layouts in this CSS that are trying to control both rows and columns') and Fix names the exact properties ('grid-template-columns, grid-template-rows, and grid-template-areas'), so the guidance is executable at the instruction level. Not 5 because no inline example shows a before/after conversion and 'appropriate' leaves the property values unspecified (code examples are deferred entirely to the reference); not 3 because the instructions are specific enough to act on directly without pseudocode vagueness.

4 / 5

Workflow Clarity

Check → Fix → Explain → Code Review reads as a natural detect-then-convert sequence, and the Code Review section ties flags to 'the rendered UI', giving a verification cue for the review task. Not 5 because the body itself lacks a post-fix validation step (re-checking the rendered layout after converting — that lives only in references/rule.md's Verification section); not 3 because the sequence and each step's intent are unambiguous for this simple single-purpose skill.

4 / 5

Progressive Disclosure

The body is a concise overview and implementation details are appropriately split into a clearly signaled, one-level-deep reference: 'For full implementation details, code examples, and framework-specific guidance, see references/rule.md'. The referenced file exists, contains the promised material (code examples, named areas, minmax, verification), and holds no nested references — matching the anchor of a well-organized overview with easy navigation.

5 / 5

Total

17

/

20

Passed

Description

83%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 strong description that explicitly covers both what the skill does and when to use it, with concrete review targets (breakpoints, interaction states, rendered layout). Main weaknesses are the awkward embedded rule title ('related to Use CSS Grid for two-dimensional layouts') and missing trigger synonyms like '.css files' or 'flexbox'.

Suggestions

Add natural trigger synonyms to the 'when' clause — e.g., '.css files', 'grid layouts', or 'Flexbox vs Grid decisions' — so it fires on the varied phrasings users actually say.

Rewrite the embedded rule title into natural syntax (e.g., 'related to CSS Grid layouts') and state the concrete fix action (converting float/Flexbox layouts to Grid) in the 'what' half to sharpen specificity.

DimensionReasoningScore

Specificity

The description lists several concrete actions — 'reviewing stylesheets, component styles, and responsive behavior', 'Check the rendered layout across breakpoints and interaction states before proposing a fix' — with only minor gaps (the fix action itself is merely implied by 'proposing a fix'). Not 5 because it stops short of naming the core capability (converting/fixing the layout to use Grid); not 3 because it goes beyond 1-2 generic actions with specific review targets and render-state checks.

4 / 5

Completeness

Both halves are explicit and concrete: an explicit trigger clause ('Use when reviewing stylesheets, component styles, and responsive behavior related to...') and an explicit what ('Check the rendered layout across breakpoints and interaction states before proposing a fix'). Not 4 because the 'when' is already specific about scope and mode, matching the anchor-5 pattern of concrete trigger phrases paired with a clear statement of what the skill does.

5 / 5

Trigger Term Quality

Natural front-end terms are present — 'stylesheets', 'component styles', 'responsive behavior', 'breakpoints', 'interaction states', 'CSS Grid', 'two-dimensional layouts' — phrases a user would plausibly say. Not 5 because common variations and synonyms are missing (e.g., '.css files', 'grid layout', 'Flexbox vs Grid decisions'); not 3 because coverage goes well beyond a single keyword with several distinct natural phrases.

4 / 5

Distinctiveness Conflict Risk

The description is bounded to a clear niche (CSS Grid layout review), and the embedded rule title anchors it to Grid specifically. Not 5 because generic triggers like 'reviewing stylesheets' and 'responsive behavior' overlap with sibling CSS checklist rules (e.g., flexbox or media-query rules); not 3 because the Grid-specific framing keeps conflict risk minor rather than broad.

4 / 5

Total

17

/

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-grid/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.