CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

css-order

Use when reviewing stylesheets, component styles, and responsive behavior related to Order CSS files correctly. Check the rendered layout across breakpoints and interaction states before proposing a fix.

Quality

76%

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

Quality

Content

71%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 body is a lean overview with a textbook progressive-disclosure structure: it states the rule and defers all code and framework detail to a real, well-matched reference file. Its main weakness is redundancy — the same CSS-before-JS directive is repeated across Quick Reference, Check, Fix, and Explain, plus an unneeded FOUC explainer. Actionability and workflow are solid, with only minor gaps (no inline head-ordering example, no post-fix verification step).

Suggestions

Merge Quick Reference and Check into one section — both restate "load all CSS files before JavaScript in the document head" — and drop the "Prevents FOUC" bullet that duplicates the intro.

Replace the opening FOUC explanation with a one-line statement of the rule and move the diagnostic detail to references/rule.md.

Add a short closing step to the Fix section: re-check the rendered layout (or head order) after reordering to confirm the fix, closing the feedback loop.

DimensionReasoningScore

Conciseness

The single rule is restated four to five times — "Load all CSS files before JavaScript in the document head" (Quick Reference), "Verify that all CSS files are loaded before JavaScript files" (Check), "Reorganize head section to load all CSS files before JavaScript files" (Fix), "Explain why CSS should load before JavaScript" (Explain) — and the opening sentence explains FOUC, a concept Claude already knows. Not a 2 because the body is short (~30 lines) with no extensive padding and each section adds a small nuance; not a 4 because the repetition exceeds minor trims — Quick Reference and Check are near-duplicates.

3 / 5

Actionability

Directives are concrete and executable: "Load all CSS files before JavaScript in the document head", "Use async/defer for non-critical JavaScript", "Inline critical CSS for faster first paint", "except for asynchronous scripts that don't block rendering", and the reference bundle carries complete HTML examples. Not a 5 because the body itself contains no concrete snippet (e.g., a correctly ordered <head>) and the common cases live only in references/rule.md; not a 3 because the guidance is specific and complete in direction, not vague hints or pseudocode.

4 / 5

Workflow Clarity

A coherent Check → Fix → Explain → Code Review sequence with a pre-fix checkpoint ("Check the rendered layout across breakpoints and interaction states before proposing a fix" / "Flag exact selectors, declarations, or breakpoints that violate the rule in the rendered UI"); this is a read-only review-plus-fix task, so no destructive-operation validation cap applies. Not a 5 because there is no explicit post-fix verification step (e.g., re-check rendering after reordering the head).

4 / 5

Progressive Disclosure

The body is a concise overview with a clearly signaled, one-level-deep pointer — "For full implementation details, code examples, and framework-specific guidance, see references/rule.md" — and that file exists and contains exactly what is promised (a Code Examples section and a Framework-Specific Implementation section covering React/Next.js, CRA, and Vue). No nesting, no buried references, no content that should have been inlined.

5 / 5

Total

16

/

20

Passed

Description

71%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 answers both what and when with several natural review keywords, but buries the rule's identity (CSS/JS load order, render-blocking, FOUC) inside a garbled clause, weakening distinctiveness against other CSS review skills. It reads as a generic CSS-review trigger with the actual rule name pasted in. Rewriting the trigger around load-order symptoms would lift the weaker dimensions.

Suggestions

Rewrite the when-clause around the rule's actual symptoms, e.g. "Use when CSS or script tags are out of order in the document head, pages flash unstyled content (FOUC), or rendering is blocked by scripts loading before styles."

Move the rule identity out of the trigger into an explicit what-clause: "Verifies CSS files load before JavaScript in the document head and reorders the head to prevent render-blocking and FOUC."

Drop generic scoping terms ("responsive behavior", "component styles") that overlap with every other CSS review skill, keeping only what distinguishes this rule.

DimensionReasoningScore

Specificity

Several concrete actions are named — "reviewing stylesheets, component styles, and responsive behavior", "Check the rendered layout across breakpoints and interaction states", "before proposing a fix" — going beyond the 1-2 actions of a score-3 description. Not a 5 because the core action of the rule (reordering CSS/JS in the head to prevent render-blocking/FOUC) is never stated, and the phrase "related to Order CSS files correctly" is garbled rather than concrete.

4 / 5

Completeness

Both parts are explicit: the what ("Check the rendered layout across breakpoints and interaction states before proposing a fix") and an explicit "Use when..." trigger clause. Not a 5 because the when-clause is convoluted ("Use when reviewing ... related to Order CSS files correctly") and lacks concrete trigger phrases tied to the rule's actual symptoms.

4 / 5

Trigger Term Quality

Natural review vocabulary is present ("stylesheets", "component styles", "responsive behavior", "rendered layout", "breakpoints", "interaction states"), giving good keyword coverage. Not a 5 because the distinctive natural terms a user with this exact problem would say — "CSS order", "render-blocking", "FOUC", "unstyled content", "scripts before styles" — are absent.

4 / 5

Distinctiveness Conflict Risk

"Reviewing stylesheets, component styles, and responsive behavior" describes nearly any CSS review skill, so this could trigger for the wrong sibling CSS rule; the distinctive element ("Order CSS files correctly") is embedded awkwardly. Not a 4 because the trigger scope is broad rather than mostly distinct; not a 2 because it is still anchored to one specific rule with rendered-layout checks.

3 / 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/css-order/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.