CtrlK
BlogDocsLog inGet started
Tessl Logo

table-headers

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

56

Quality

65%

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/table-headers/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

55%

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 overview pointing to a real, one-level-deep reference file, but its inline guidance is light on executable examples and its Check/Fix workflow lacks explicit validation checkpoints despite mentioning verification tooling.

Suggestions

Add a small inline HTML example showing the before/after of converting a <td> header to <th scope="col"> so the Fix step is copy-paste ready rather than a prose instruction.

Insert an explicit verification checkpoint in the workflow (e.g., run axe/Lighthouse or inspect the accessibility tree) between Fix and Explain so the sequence has a validation feedback loop.

Trim the opening sentence explaining what headers do for screen readers, since it restates a concept Claude already knows.

DimensionReasoningScore

Conciseness

The body is mostly lean, but lines like 'Properly defined headers allow screen readers to announce the context for each data cell' explain a basic accessibility concept Claude already knows, and the Code Review section restates the Check/Explain framing.

2 / 3

Actionability

It gives concrete directives ('Use <th>', 'Apply scope="col" or scope="row"') but provides no executable code or example markup inline; the only code example lives in the offloaded reference, and the Fix step is a vague instruction rather than a copy-paste-ready snippet.

2 / 3

Workflow Clarity

The Check/Fix/Explain/Code Review sections imply a sequence, but there are no explicit validation checkpoints or verify-the-fix steps despite the body flagging browser accessibility tooling as a verification aid.

2 / 3

Progressive Disclosure

The body is a concise overview that clearly signals one-level-deep references ('see references/rule.md'), the referenced file exists and is well-organized, and navigation is easy with no nested reference chains.

3 / 3

Total

9

/

12

Passed

Description

75%

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 an explicit trigger, but it is hampered by an awkward embedded rule-title fragment ('related to Define proper table headers') that reads unnaturally and broad framing that risks overlap with general accessibility skills.

Suggestions

Reword 'related to Define proper table headers' into natural user phrasing such as 'related to table headers and accessible tables' so the trigger reads as something a user would actually say.

Tighten the broad opening ('reviewing rendered HTML, interactive components, or design-system patterns') to scope specifically to table semantics and header associations to reduce overlap with general accessibility skills.

Lead with the concrete action (define or fix table headers using <th> and scope) before the review framing so the capability is immediately clear.

DimensionReasoningScore

Specificity

It names the domain (reviewing rendered HTML, design-system patterns, accessibility) and several actions (inspect keyboard behavior, focus flow, accessible names, screen-reader output), but these are review activities rather than the concrete edit actions the skill's Fix step implies, so it is not fully comprehensive.

2 / 3

Completeness

It explicitly states what it does ('Check native semantics first, then inspect...') and when to use it ('Use when reviewing rendered HTML...'), satisfying both halves with an explicit trigger clause.

3 / 3

Trigger Term Quality

It includes relevant natural terms (HTML, design-system patterns, screen-reader output), but the anchor phrase 'related to Define proper table headers' is an awkward, rule-title fragment rather than natural user wording like 'table headers' or 'accessible tables'.

2 / 3

Distinctiveness Conflict Risk

The accessibility review framing is reasonably specific to table-header issues, but the phrase 'reviewing rendered HTML, interactive components, or design-system patterns' is broad enough to overlap with many general accessibility or component-review skills.

2 / 3

Total

9

/

12

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository
thedaviddias/Front-End-Checklist
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.