CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

subgrid

Use when reviewing card grid layouts with misaligned content areas, or any nested grid where child items need to align with sibling cards' corresponding sections without JavaScript intervention.

Quality

70%

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

Quality

Content

67%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 overview that defers implementation detail to a single clearly signaled reference file, with concrete property-level fix guidance. Its main weaknesses are the redundant background paragraph duplicated verbatim in the reference and a pointer that slightly over-states what the reference contains.

Suggestions

Remove the duplicated background paragraph — either drop the intro from SKILL.md or the "Why It Matters" section from references/rule.md — and keep one orientation copy in the body only.

Add a minimal inline parent+card subgrid snippet (grid-row: span N with grid-template-rows: subgrid) to the Fix section so the core pattern is executable without opening the reference.

Align the pointer text with the reference's actual contents (it has no framework-specific guidance), or add such a section to the reference.

DimensionReasoningScore

Conciseness

The opening paragraph ("Card grids are one of the most common UI patterns, but aligning content across cards — matching title heights, content areas, and footers — has historically required JavaScript height measurement or CSS hacks…") explains background Claude already knows and is duplicated nearly verbatim in references/rule.md's "Why It Matters" section; the Quick Reference bullets ("No JavaScript height matching needed") restate it again. That is more than 'minor instances of over-explanation', fitting the 'mostly efficient but includes some unnecessary explanation' anchor rather than the efficient one.

3 / 5

Actionability

Concrete, property-level guidance: "set grid-template-rows on the parent grid, then apply grid-row: span N and grid-template-rows: subgrid on each card", and the Code Review section flags specific smells ("JavaScript height matching, fixed heights, or display: contents workarounds"). As an instruction-only skill the absent inline code is acceptable since full executable examples are deferred to the reference, leaving only the minor gap of no minimal snippet in the body.

4 / 5

Workflow Clarity

The Check → Fix → Explain → Code Review modes are clearly delineated and each is unambiguous about what to do; browser-support facts are stated for decision-making. This is not a destructive or batch operation so no validation cap applies, but verification steps appear only in the reference file, not the body, which keeps it at 'clear sequence with minor validation gaps' rather than the full-checkpoint level.

4 / 5

Progressive Disclosure

The body is a short overview with one clearly signaled, one-level-deep reference ("For full implementation details, code examples, and framework-specific guidance, see references/rule.md"), and that file exists with the code examples as promised. Minor gaps: the pointer over-claims (rule.md contains no framework-specific guidance) and the intro paragraph is duplicated inside the reference, fitting 'good structure; minor organization gaps' rather than the top anchor.

4 / 5

Total

15

/

20

Passed

Description

61%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 well-crafted, specific trigger description with natural phrasing and a clear niche, but it is purely a 'when' clause: it never states the skill's action (applying CSS subgrid), omitting the most direct keyword and leaving the 'what' implied. Adding a leading capability statement naming subgrid would raise both completeness and trigger coverage.

Suggestions

Add an explicit 'what' statement before the trigger clause, e.g. "Applies CSS subgrid to align nested grid items with parent tracks" so the description answers both what and when.

Include the keyword "subgrid" itself plus common user phrasings like "cards not lining up" or "equal card heights" as trigger terms.

Consider naming CSS explicitly to further reduce overlap with generic layout-alignment skills.

DimensionReasoningScore

Specificity

Concrete scenario language is present ("reviewing card grid layouts with misaligned content areas", "align with sibling cards' corresponding sections"), but the description never states what the skill actually does — the mechanism (applying CSS subgrid) and the term itself are absent. This matches the anchor for a named domain with 1-2 concrete elements but not comprehensive action coverage, not the level above which requires several listed actions.

3 / 5

Completeness

The entire description is a single explicit 'Use when…' clause, so 'when' is strongly answered, but 'what' is only implied through the alignment outcome and never explicitly stated. It sits between the 'only when present without what' anchor and the 'clear what but weak when' mirror; the strongly implied purpose keeps it at 3, while the unnamed mechanism prevents a 4.

3 / 5

Trigger Term Quality

Includes natural phrases users would say: "card grid layouts", "misaligned content areas", "nested grid", "sibling cards", "without JavaScript". Good coverage, but the most direct keyword ("subgrid") and common variants ("cards not lining up", "equal card heights", "grid alignment") are missing, which matches the 'good keyword coverage; a few natural terms missing' anchor rather than the comprehensive one.

4 / 5

Distinctiveness Conflict Risk

The trigger carves a clear niche (cross-card alignment in nested grids without JavaScript) that would rarely fire the wrong skill. Minor overlap risk remains with generic CSS grid/layout skills because neither "CSS" nor "subgrid" appears in the description, matching the 'mostly distinct; minor overlap risk' anchor.

4 / 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/subgrid/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.