td-headers-attr

Use when reviewing rendered HTML, interactive components, or design-system patterns related to Link table cells to headers using IDs. Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output where relevant.

Quality

89%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

86%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 concise, well-structured, and uses progressive disclosure effectively via a real one-level reference file. It could be slightly more actionable and its review workflow more explicit by inlining a minimal HTML example and a validate-fix-retry checkpoint.

Suggestions

Inline a minimal `headers`/`<th id>` HTML snippet in the body so reviewers have a copy-paste reference without opening references/rule.md.

Add an explicit validate-then-retry checkpoint to the Code Review section (e.g., re-run the accessibility checker and confirm the violation is gone before considering the fix complete).

State the specific verification command or tool (e.g., 'Run axe DevTools on the table') rather than the generic 'browser accessibility tooling'.

Dimension	Reasoning	Score
Conciseness	The body is lean bullets and short imperatives with no padding or over-explanation of known concepts; nearly every token earns its place.	5 / 5
Actionability	Quick Reference gives concrete rules (use the `headers` attribute, reference valid `th` IDs, space-separate IDs) and Check/Fix/Explain are specific, but no executable inline code example — the HTML pattern is deferred to references/rule.md.	4 / 5
Workflow Clarity	The Quick Reference → Check → Fix → Explain → Code Review sequence is clear and includes verification guidance ('verify the fix with browser accessibility tooling or assistive tech'), though it lacks an explicit validate-then-retry loop.	4 / 5
Progressive Disclosure	A clear overview in SKILL.md with a well-signaled one-level-deep pointer to references/rule.md (verified to exist and contain the full implementation), with content appropriately split.	5 / 5
	Total	18 / 20 Passed

Description

92%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 is strong: it names a specific accessibility niche, gives concrete review actions, and provides explicit 'use when' triggers covering both what and when. Only minor improvement is possible by adding accessibility-synonym trigger terms.

Dimension	Reasoning	Score
Specificity	Enumerates multiple concrete review actions ('Check native semantics first', 'inspect keyboard behavior, focus flow, accessible names, and screen-reader output') with comprehensive coverage of the review process.	5 / 5
Completeness	Explicitly answers both 'when' ('Use when reviewing rendered HTML... related to Link table cells to headers using IDs') and 'what' (the enumerated check-and-inspect actions) with concrete trigger phrases.	5 / 5
Trigger Term Quality	Includes natural terms a frontend/a11y reviewer would say ('rendered HTML', 'interactive components', 'design-system patterns', 'table cells', 'headers'), but misses common synonyms like 'a11y', 'accessibility audit', or 'WCAG'.	4 / 5
Distinctiveness Conflict Risk	Targets a single narrow accessibility rule (td-headers-attr) with a distinct niche and minimal overlap risk with other skills.	5 / 5
	Total	19 / 20 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Repository: thedaviddias/Front-End-Checklist
Path: skills/td-headers-attr/SKILL.md
Commit: 30756a7

Reviewed: 9 days ago

Table of Contents

Discovery Implementation Validation

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.