CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.

Quality

77%

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

78%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 tight, well-structured overview: concrete Quick Reference rules, unambiguous Check/Fix guidance, and a correctly used one-level reference file for code examples and verification details. The only notable weakness is the templated Code Review section that duplicates the description and awkwardly embeds the rule title.

DimensionReasoningScore

Conciseness

The body is lean — the Quick Reference bullets ("Use `<th>` for all table headers, not `<td>`", "Apply `scope="col"` or `scope="row"`") earn their tokens — but the Code Review section is templated filler that largely restates the description, including the awkward "affect Define proper table headers" phrase. Efficient with minor trimming possible, so not 5.

4 / 5

Actionability

Concrete directives name specific elements, attributes, and values ("Convert header cells to `<th>` and add the correct `scope` attribute"), with full code examples correctly deferred to `references/rule.md`, which exists and delivers them. Held at 4 because there is no inline example and "Ensure every data cell is associated with at least one header" doesn't say how (via `scope` or `headers`/`id`).

4 / 5

Workflow Clarity

The Check → Fix → Explain sequence is clear and the single core action (convert header cells to `<th>` with the correct `scope`) is unambiguous, so the simple-skill exception applies. Not 5 because the header-association bullet lacks a mechanism and no explicit verify step appears inline (verification lives only in the reference file).

4 / 5

Progressive Disclosure

A short, well-sectioned overview with a single clearly signaled one-level-deep reference ("For full implementation details, code examples, and framework-specific guidance, see `references/rule.md`") that exists and contains exactly the promised code example and verification guidance. This matches the clear-overview anchor.

5 / 5

Total

17

/

20

Passed

Description

66%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 an explicit "Use when…" trigger with decent natural keywords, but it reads like a filled-in template: the rule title is pasted mid-sentence ("related to Define proper table headers"), and the capability specific to this skill — fixing `<td>`/`<th>` and `scope` semantics — is never mentioned. The generic inspection phrasing also creates overlap risk with sibling accessibility rules.

Suggestions

State the skill's concrete capability up front, e.g. "Audits data tables for header semantics and converts `<td>` header cells to `<th>` with the correct `scope` attribute."

Replace the pasted rule title with a natural trigger phrase, e.g. "Use when reviewing or fixing table accessibility: table headers, `<th>` elements, or `scope` attributes in rendered HTML."

Add natural trigger synonyms users would say, such as "accessibility", "screen reader", "data table", and "a11y".

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 these are the generic review process shared across the rule family; the skill's own capability — converting `<td>` header cells to `<th>` with `scope` attributes — is never stated, which is more than a minor coverage gap.

3 / 5

Completeness

Explicitly answers "when" ("Use when reviewing rendered HTML, interactive components, or design-system patterns related to Define proper table headers") and gives what-actions ("Check native semantics first, then inspect…"). Not 5 because the "what" describes a generic inspection process rather than the skill's concrete fix capability, leaving the what slightly less clear than the when.

4 / 5

Trigger Term Quality

Good natural keyword coverage: "rendered HTML", "table headers", "keyboard behavior", "focus flow", "accessible names", and "screen-reader output". Falls short of 5 because common variations and synonyms like "accessibility", "data table", "screen reader" (unhyphenated), and "scope" are missing, and the embedded rule title "Define proper table headers" is not a phrase users would naturally say.

4 / 5

Distinctiveness Conflict Risk

"table headers" carves out a niche, but the templated prefix "Use when reviewing rendered HTML, interactive components, or design-system patterns" is shared verbatim across sibling accessibility rules in this checklist family, so it could still overlap with closely related accessibility-review skills — matching the "somewhat specific but could still overlap" anchor.

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/table-headers/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.