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

74%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/css-grid/SKILL.md

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 lean, well-structured instruction body with concrete detection and fix guidance and exemplary progressive disclosure to a single reference file. Its only weaknesses are minor redundancy with the reference file and the description, plus verification detail being deferred rather than stated inline.

Dimension	Reasoning	Score
Conciseness	The ~35-line body is efficient overall, but the opening paragraph ('CSS Grid solves layout problems that previously required JavaScript or complex CSS hacks...') duplicates rule.md's 'Why It Matters' verbatim, and the 'Code Review' section restates the frontmatter description — both trimmable without losing information.	4 / 5
Actionability	Concrete, property-level instruction is present: 'Look for float-based or Flexbox layouts... trying to control both rows and columns' and 'Convert... with appropriate grid-template-columns, grid-template-rows, and grid-template-areas'. It stops short of fully copy-paste-ready guidance because the executable code examples live entirely in the reference file with no compact inline example for the common case.	4 / 5
Workflow Clarity	The Check → Fix → Explain → Code Review sections give a clear, labeled sequence for this simple review task, and rendered-UI verification appears in Check/Code Review. The full validation loop (post-fix breakpoint verification) is deferred to references/rule.md's Verification section rather than stated inline, a minor gap against the explicit validate-and-retry anchor.	4 / 5
Progressive Disclosure	The body is a clear overview with a well-signaled, one-level-deep reference ('For full implementation details, code examples, and framework-specific guidance, see references/rule.md' — a real file), an appropriate split of summary vs. detail, and easy navigation including the source rule page URL.	5 / 5
	Total	17 / 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.

A serviceable description with an explicit 'Use when...' trigger and a couple of concrete review actions, weakened by templated phrasing and thin trigger-term coverage. The rule title embedded mid-sentence reads awkwardly and misses natural synonyms like '.css' and 'flexbox'.

Suggestions

Rewrite the trigger clause into natural user phrasing, e.g. 'Use when the user mentions CSS Grid, grid layouts, .css files, or asks whether a layout should use Grid instead of Flexbox.'

Add one more concrete capability to the 'what' portion (e.g. 'convert Flexbox/float-based two-dimensional layouts to grid-template-columns/areas') so specificity moves beyond two actions.

List explicit trigger keywords including 'flexbox', 'grid vs flexbox', and '.css' to reduce missed invocations and improve distinctiveness from sibling CSS-rule skills.

Dimension	Reasoning	Score
Specificity	The description names the domain (stylesheets, component styles, responsive behavior) and two concrete actions ('reviewing', 'Check the rendered layout across breakpoints and interaction states'), but coverage is not comprehensive. The template phrase 'related to Use CSS Grid for two-dimensional layouts' adds no additional concrete action, keeping it at the 1-2-actions anchor rather than the several-actions anchor.	3 / 5
Completeness	Both 'what' (review styles and check the rendered layout across breakpoints/interaction states before proposing a fix) and an explicit 'Use when...' clause are present. It falls short of the top anchor because the trigger sentence is a run-on template construction ('related to Use CSS Grid for two-dimensional layouts') rather than crisp, concrete trigger phrases.	4 / 5
Trigger Term Quality	Good natural keyword coverage: 'stylesheets', 'component styles', 'responsive behavior', 'breakpoints', 'CSS Grid', 'rendered layout'. A few common variations are missing, notably '.css' file extensions, 'flexbox', and 'grid layout' phrasings a user would naturally say.	4 / 5
Distinctiveness Conflict Risk	The CSS Grid rule gives it a clear niche with distinct triggers, but 'reviewing stylesheets, component styles, and responsive behavior' is generic enough to overlap with sibling CSS-rule skills (e.g., a flexbox or media-query rule) in the same family.	4 / 5
	Total	15 / 20 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Repository: thedaviddias/Front-End-Checklist
Path: skills/css-grid/SKILL.md
Commit: 7bfd868

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

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.