CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

flexbox-patterns

Use when reviewing stylesheets, component styles, and responsive behavior related to Apply Flexbox best practices. 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/flexbox-patterns/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.

A well-structured, appropriately split skill body: the Quick Reference delivers concrete Flexbox fixes with exact values, and details are correctly pushed to a clearly signaled reference file. The weaknesses are redundancy — Check, Fix, and Code Review repeat the same three mistakes, and Explain restates concepts Claude already knows — and the absence of a sequenced check→fix→verify workflow with a validation checkpoint.

Suggestions

Consolidate the overlapping 'Check', 'Fix', and 'Code Review' sections into a single section listing the three concrete checks paired with their fixes, and drop or trim the 'Explain' section since flex-grow/shrink/basis mechanics are knowledge Claude already has.

Turn the sections into an explicit sequence with a validation checkpoint, e.g. '1. Check the CSS for the three common mistakes; 2. Propose fixes (min-width:0, gap, corrected flex shorthand); 3. Verify the rendered layout across breakpoints and interaction states before finalizing' — this also carries the frontmatter's verification guidance into the body.

Add one small copy-paste-ready CSS snippet in the body showing the min-width:0 + gap pattern applied, so the most common fix is executable without opening the reference file.

DimensionReasoningScore

Conciseness

The Quick Reference bullets are lean and earn their tokens, but the 'Check', 'Fix', and 'Code Review' sections each restate the same three mistakes (min-width:0, margin vs gap, flex shorthand), and the 'Explain' section directs Claude to explain flex-grow/flex-shrink/flex-basis — concepts it already knows. This matches score 3 ('mostly efficient but could be tightened'), not 4, given several redundant sections relative to the body's short length.

3 / 5

Actionability

Concrete, directly applicable guidance is present with exact property values: 'Use flex: 1 1 0 (shorthand: flex:1)', 'Add min-width: 0 to flex children when text overflow truncation doesn't work', 'Use gap instead of margin'. Per the rubric's scoring note, absent inline code is not penalized in an instruction-only skill when the guidance is actionable; it is not a 5 because no copy-paste-ready example covers the common cases in the body (code is deferred to references/rule.md).

4 / 5

Workflow Clarity

The 'Check', 'Fix', 'Explain', and 'Code Review' headings read as parallel task modes rather than a sequenced workflow, and there is no post-fix validation step — the frontmatter's own guidance to 'Check the rendered layout across breakpoints and interaction states before proposing a fix' is not carried into the body. This fits score 3 ('steps listed but validation gaps; checkpoints missing or implicit') rather than 4, which requires a clear sequence with most checkpoints present.

3 / 5

Progressive Disclosure

The body is a short, well-sectioned overview (Quick Reference plus task summaries) with a single clearly signaled, one-level-deep reference: 'For full implementation details, code examples, and framework-specific guidance, see references/rule.md' (verified to exist, 150 lines). This matches score 5's 'clear overview with well-signaled one-level-deep references'.

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.

A serviceable description with an explicit 'Use when' trigger and good natural keywords centered on Flexbox, stylesheets, and responsive behavior. Its main weaknesses are an incomplete 'what' (only layout-checking is described, not the fix/explain/review capabilities) and the awkward jammed-in phrase 'related to Apply Flexbox best practices', which reads as a rule title pasted mid-sentence rather than a capability statement.

Suggestions

State the 'what' up front with concrete capabilities, e.g. 'Reviews and fixes Flexbox layout issues: adds min-width:0 to flex children, replaces inter-item margins with gap, and corrects flex shorthand values.'

Fix the grammatical splice 'related to Apply Flexbox best practices' by rephrasing to natural language such as 'related to Flexbox best practices', and add common synonyms like 'flex layout' or 'flex items' to broaden trigger coverage.

DimensionReasoningScore

Specificity

The description names the domain ('reviewing stylesheets, component styles, and responsive behavior related to Apply Flexbox best practices') and one concrete action ('Check the rendered layout across breakpoints and interaction states before proposing a fix'), but never enumerates the actual capabilities (identifying missing min-width:0, replacing margins with gap, correcting flex shorthand). It names the domain with 1-2 actions, matching the score-3 anchor rather than score 4's 'several specific actions'.

3 / 5

Completeness

The 'when' is explicit ('Use when reviewing stylesheets, component styles, and responsive behavior...') and a partial 'what' exists ('Check the rendered layout across breakpoints and interaction states before proposing a fix'), matching score 4's 'both present, when/what could be more explicit'. It is not a 5 because the 'what' omits the review/fix/explain capabilities the skill actually provides.

4 / 5

Trigger Term Quality

Natural trigger terms are present: 'stylesheets', 'component styles', 'responsive behavior', 'Flexbox', 'breakpoints', 'interaction states', 'layout' — phrases a user would realistically say. It falls short of score 5 because common synonyms and variations like 'flex', 'flex layout', 'flexbox bugs', or '.css' are missing.

4 / 5

Distinctiveness Conflict Risk

'Flexbox' anchors a clear niche with distinct triggers, but the broad framing 'reviewing stylesheets, component styles, and responsive behavior' creates minor overlap risk with general CSS-review or responsive-design skills, fitting score 4 ('mostly distinct; minor overlap risk') rather than 5's minimal conflict risk.

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/flexbox-patterns/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.