th-has-data-cells

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

Quality

67%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/th-has-data-cells/SKILL.md

Quality

Content

57%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The skill is well-structured with a clean progressive-disclosure split to a real reference file, but the body's guidance is short on concrete mechanisms and explicit verification steps.

Suggestions

Add one concrete fix mechanism in the body — e.g. 'add scope="col"/"row" or link via headers="id"' — so the Fix step is actionable without opening the reference.

Make verification explicit in the workflow, e.g. 'Confirm each <th> maps to ≥1 <td> in the accessibility tree before closing the review.'

Trim redundancy: fold the Quick Reference bullets into Check/Fix or drop the meta 'Explain' section to tighten token use.

Dimension	Reasoning	Score
Conciseness	The body is lean and avoids explaining basics, but the Quick Reference bullets overlap with the Check/Fix sections and the 'Explain' section is meta guidance that could be trimmed.	2 / 3
Actionability	It states concrete rules ('Every <th> must be associated with one or more <td> cells') but the how-to is vague — 'ensure they are correctly mapped to data cells' gives no mechanism (scope, headers/id) and the body carries no example.	2 / 3
Workflow Clarity	A Check→Fix→Code Review sequence exists, but verification checkpoints are only implicit in the body (the actual validation steps live in the reference), so it is not a fully validated workflow.	2 / 3
Progressive Disclosure	The body is a clear overview with a single well-signaled one-level-deep pointer to references/rule.md (which exists), matching the clean-split anchor.	3 / 3
	Total	9 / 12 Passed

Description

77%

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 concrete actions and an explicit trigger clause, but its trigger phrasing is awkward and broad enough to risk overlap with other accessibility skills.

Suggestions

Lead with a natural trigger users would say, e.g. 'Use when reviewing HTML tables for accessibility — e.g. empty or orphaned <th> headers, missing header/data-cell associations.'

Narrow the trigger from generic 'rendered HTML, interactive components, design-system patterns' to table-specific cues so it is less likely to fire for unrelated a11y skills.

Reword the embedded rule title into fluent prose rather than the literal 'Ensure table headers associate with data cells' fragment.

Dimension	Reasoning	Score
Specificity	Lists several concrete review actions — 'check native semantics', 'inspect keyboard behavior, focus flow, accessible names, and screen-reader output' — matching the multi-action anchor rather than the single-domain anchor below.	3 / 3
Completeness	An explicit 'Use when...' clause supplies the trigger and the subsequent action list supplies the what, satisfying both halves; not capped at 2 because the trigger guidance is present.	3 / 3
Trigger Term Quality	'rendered HTML, interactive components, design-system patterns' are relevant, but 'Ensure table headers associate with data cells' is embedded awkwardly mid-sentence rather than as natural user phrasing, and common variations like 'table headers' or 'empty headers' are absent.	2 / 3
Distinctiveness Conflict Risk	The triggers 'rendered HTML, interactive components, design-system patterns' are broad accessibility-review language that could overlap with sibling a11y skills, so it is only somewhat specific.	2 / 3
	Total	10 / 12 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/th-has-data-cells/SKILL.md
Commit: 48405aa

Reviewed: about 7 hours 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.