CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

content-without-css

Use when reviewing rendered HTML, layout components, or design-system patterns that may depend on presentation for meaning. Check the DOM order, semantic structure, form relationships, and whether CSS generated content carries essential information.

Quality

78%

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/content-without-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.

Well-structured with excellent progressive disclosure to a verified reference file, but the body itself is thin on executable detail — no concrete test method or markup examples — and the Quick Reference duplicates the Check/Fix sections. The description is stronger than the body.

Suggestions

Consolidate the Quick Reference bullets with the Check and Fix sections to remove duplication and tighten token usage.

Add a concrete verification procedure in the Check section, e.g. how to disable author styles (DevTools rendering emulation or a user-stylesheet override) before testing key journeys.

Inline one small bad/good markup example (e.g. label conveyed only via ::after content vs. a real <label> element) so the body is actionable without opening the reference.

DimensionReasoningScore

Conciseness

Mostly efficient, but the Quick Reference bullets largely duplicate the Check/Fix sections, and the intro paragraph explains rationale (custom styles, high contrast modes, reader tools) that Claude already knows; both could be tightened.

3 / 5

Actionability

Provides concrete checklist items (logical reading order, visible labels, error text, pseudo-elements, visual-only cues) but gives no specific test procedure for disabling author styles and no markup examples in the body — key execution details live only in the reference file.

3 / 5

Workflow Clarity

The Check → Fix → Explain → Code Review sections form a coherent flow with verification embedded ("Test key journeys with author styles disabled"), but the sequence is implicit rather than explicitly ordered with checkpoints.

4 / 5

Progressive Disclosure

A concise overview body with a single clearly signaled, one-level-deep reference ("For full implementation details, code examples, and framework-specific guidance, see `references/rule.md`"), which exists and contains that detail; navigation is easy.

5 / 5

Total

15

/

20

Passed

Description

83%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 strong description with an explicit 'Use when...' trigger clause and several concrete checking actions. Minor improvements possible: mention remediation and add common accessibility synonyms like 'a11y' or 'styles disabled' to widen trigger coverage.

DimensionReasoningScore

Specificity

Lists several concrete actions ("Check the DOM order, semantic structure, form relationships, and whether CSS generated content carries essential information") but omits remediation actions that the skill body covers, so coverage has minor gaps rather than being comprehensive.

4 / 5

Completeness

Explicitly answers both what (the four concrete checks) and when ("Use when reviewing rendered HTML, layout components, or design-system patterns that may depend on presentation for meaning") with concrete trigger phrases.

5 / 5

Trigger Term Quality

Good natural keyword coverage ("rendered HTML", "layout components", "design-system patterns", "CSS generated content") but misses common user phrasings like "accessibility", "a11y", "screen reader", or "styles disabled".

4 / 5

Distinctiveness Conflict Risk

Clear niche (content resilience without CSS) with mostly distinct triggers, but "reviewing rendered HTML, layout components" is broad enough to overlap with general HTML or design-system review skills.

4 / 5

Total

17

/

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/content-without-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.