CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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

73%

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/td-headers-attr/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 well-structured, token-efficient overview that delegates detail appropriately to a real, accurately-described reference file. Its main weakness is actionability: the check and fix directives name the goal but provide no in-body example or verification mechanism, so execution depends entirely on the reference.

Suggestions

Add a minimal correct-vs-incorrect markup pair (a td with headers="h-q1" pointing at a real th id, versus a stale/duplicate id) so the check is executable without opening the reference.

Name one concrete verification method in the body (e.g. an axe rule id or a quick DOM query for td[headers] ids not matching any th id) instead of the generic "browser accessibility tooling" phrasing.

Trim or merge the boilerplate Code Review paragraph into the Check section, since it largely restates the description.

DimensionReasoningScore

Conciseness

The body is lean with no explanations of concepts Claude already knows, but the generic "Code Review" paragraph ("Flag exact elements, roles, labels, focus behavior, or keyboard interactions...") is boilerplate that adds little beyond the description and could be trimmed.

4 / 5

Actionability

"Verify that `td` headers attributes reference valid and existing `th` IDs" is a concrete, doable check, but the body contains no correct/incorrect markup example, selector, or verification command — the executable how is entirely delegated to references/rule.md, leaving key details missing.

3 / 5

Workflow Clarity

The Check → Fix → Explain → Code Review sections give a clear, unambiguous progression for a single-purpose, non-destructive skill, though no explicit re-verification step appears in the body's own sequence (verification steps live only in the reference).

4 / 5

Progressive Disclosure

The body is a concise overview with a single well-signaled, one-level-deep pointer ("For full implementation details, code examples, and framework-specific guidance, see `references/rule.md`") that accurately describes the reference's contents; the reference exists and nests no further references.

5 / 5

Total

16

/

20

Passed

Description

63%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 has a solid explicit what/when structure with several concrete inspection actions, but its trigger phrasing is diluted: the generic opening would collide with sibling accessibility skills, the most natural user synonyms (accessibility, a11y, WCAG, data tables) are absent, and the rule title is wedged in as an ungrammatical noun phrase instead of actionable language.

Suggestions

State the core action explicitly, e.g. "Verify that td headers attributes reference valid, existing th IDs and fix invalid references" instead of the noun phrase "related to Link table cells to headers using IDs".

Add natural trigger synonyms users would say: "accessibility", "a11y", "WCAG", "data tables", "screen readers", "table headers".

Differentiate from sibling design-system/a11y skills by making the table-specific trigger lead the when-clause (e.g. "Use when reviewing complex data tables or table markup where header-cell relationships matter").

DimensionReasoningScore

Specificity

The description lists several concrete inspection actions ("Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output"), but the core rule task is buried in an awkward rule-title noun phrase ("related to Link table cells to headers using IDs") rather than stated as an action, leaving minor gaps in coverage.

4 / 5

Completeness

Both what ("Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output") and when ("Use when reviewing rendered HTML, interactive components, or design-system patterns") are explicitly present, but the when-clause is convoluted by the trailing rule-title phrase and lacks crisp concrete trigger phrasing.

4 / 5

Trigger Term Quality

Some relevant natural keywords are present ("rendered HTML", "screen-reader output", "keyboard behavior", "table cells"), but common synonyms a user would actually say — "accessibility", "a11y", "WCAG", "data tables" — are missing, and "Link table cells to headers using IDs" is rule-title language rather than user phrasing.

3 / 5

Distinctiveness Conflict Risk

The leading triggers ("reviewing rendered HTML, interactive components, or design-system patterns") are broad boilerplate that would equally match many sibling accessibility/design-system skills, so distinctiveness rests entirely on the trailing rule-title clause — somewhat specific but with real overlap risk against closely related table-accessibility skills.

3 / 5

Total

14

/

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/td-headers-attr/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.