CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

embedded-or-inline-css

Use when reviewing stylesheets, component styles, and responsive behavior related to Avoid embedded and inline CSS. 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
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/embedded-or-inline-css/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

63%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-organized overview with excellent progressive disclosure — the body appropriately splits detail into a clearly signaled, one-level-deep reference. The weaknesses are repetition: the caching/exceptions rationale is restated across four sections, and the Check step says what to verify without any executable detection detail in the body itself.

Suggestions

State the rationale once and cut the duplicates — the intro sentence, the "Inline CSS breaks caching and increases HTML size" Quick Reference bullet, and the Explain section all restate concepts Claude already knows.

Add one concrete detection hint to the Check section (e.g., search for style= attributes and <style> blocks, or name the ESLint/Stylelint rules) so the step is executable without opening the reference.

Sequence the description's rendered-layout check explicitly (verify across breakpoints and interaction states after moving styles) to close the workflow's post-fix validation gap.

DimensionReasoningScore

Conciseness

The same guidance is restated roughly four times — the intro ("Inline CSS cannot be cached separately, increases HTML payload, breaks separation of concerns"), the Quick Reference bullet ("Inline CSS breaks caching and increases HTML size"), the Check section ("avoided except for valid use cases like critical CSS, dynamic styles"), and the Fix section. The body could be meaningfully tightened by merging these, matching anchor 3 (mostly efficient but could be tightened) rather than 4, which expects only minor trimmable instances.

3 / 5

Actionability

Guidance is concrete at the level of intent ("Move inline styles to external CSS files or CSS-in-JS", "Flag exact selectors, declarations, or breakpoints"), but the body contains no code, commands, or detection specifics — no grep targets (style= attributes, <style> blocks) or lint rule names — with all executable detail delegated to references/rule.md. Anchor 4 requires concrete code or commands, so anchor 3 (some concrete guidance but missing key details) is the better fit.

3 / 5

Workflow Clarity

The Quick Reference → Check → Fix → Explain → Code Review sections sequence this simple, non-destructive review task clearly and unambiguously. It falls short of 5 because there is no post-fix verification step — the description's "Check the rendered layout across breakpoints and interaction states before proposing a fix" check is never sequenced in the body — leaving a minor validation gap rather than the missing checkpoints of anchor 3.

4 / 5

Progressive Disclosure

A lean ~30-line overview that appropriately delegates 774 lines of implementation detail via a clearly signaled, one-level-deep pointer ("For full implementation details, code examples, and framework-specific guidance, see references/rule.md"). The referenced file exists, contains the code examples and framework-specific guidance promised, and holds no nested references, matching anchor 5.

5 / 5

Total

15

/

20

Passed

Description

75%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 solid third-person description with an explicit "Use when" trigger and several concrete review actions. Its main weaknesses are that the core remediation capability is only implied via the rule title rather than stated, and trigger coverage misses natural synonyms like "style tag", "style attribute", and "external CSS".

Suggestions

State the core capability explicitly (e.g., "Detect and flag inline and embedded CSS (style= attributes, <style> blocks) and move them to external stylesheets") instead of relying on the embedded rule title.

Add trigger synonyms such as "style tag", "style attribute", and "external CSS" to broaden natural-term coverage.

DimensionReasoningScore

Specificity

Lists several concrete actions — "reviewing stylesheets, component styles, and responsive behavior" and "Check the rendered layout across breakpoints and interaction states before proposing a fix" — but never states the core remediation (moving inline/embedded CSS to external files), leaving minor coverage gaps. Fits anchor 4 rather than 5 because the action list is not comprehensive, and rather than 3 because more than 1-2 specific actions are named.

4 / 5

Completeness

"When" is explicit ("Use when reviewing stylesheets, component styles, and responsive behavior related to Avoid embedded and inline CSS") and a partial "what" is present ("Check the rendered layout across breakpoints and interaction states before proposing a fix"), but the core capability — detecting inline/embedded CSS and moving it to external stylesheets — is only implied via the rule title, not stated. Both are present yet the "what" could be more explicit, matching anchor 4 rather than 5.

4 / 5

Trigger Term Quality

Good natural keyword coverage — "stylesheets", "component styles", "responsive behavior", "inline CSS", "breakpoints", "interaction states" — but misses common variations users would say such as "style tag", "style attribute", or "external CSS". Anchor 4 (good coverage, a few natural terms missing) fits better than 3, which requires only minimal relevant keywords.

4 / 5

Distinctiveness Conflict Risk

A clear CSS-review niche with distinct triggers ("inline CSS", "stylesheets", "component styles"), but "responsive behavior" and "breakpoints" broaden it into general responsive-layout review, creating minor overlap risk with closely related CSS skills. Mostly distinct, matching anchor 4 rather than 5's minimal-conflict bar.

4 / 5

Total

16

/

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/embedded-or-inline-css/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.