CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

table-duplicate-name

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

Quality

80%

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-duplicate-name/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.

A lean, well-structured review skill: concrete check/fix guidance, verification pointers, and an exemplary one-level-deep pointer to references/rule.md for all implementation detail. The main gaps are a triple-repeated rationale and a vague Explain section that adds tokens without adding action.

Suggestions

Make the Explain section concrete (e.g., the specific user-facing sentence to deliver about screen-reader table navigation) or fold it into Fix to remove the vague meta-direction.

Trim the redundant rationale — the intro sentence, the Quick Reference bullet "Helps screen reader users distinguish between multiple tables", and the Explain section all restate the same 'why'; one statement suffices.

Inline one minimal good/bad markup example (<caption> vs aria-label) so the Fix section is copy-paste ready without opening the reference file.

DimensionReasoningScore

Conciseness

The ~35-line body is lean, assumes Claude's competence, and defers all examples and detail to the reference file. It falls short of anchor 5 only through minor redundancy: the rationale ("unique names allow users of assistive technology to quickly identify and navigate to the data they need", "Helps screen reader users distinguish between multiple tables", and the entire Explain section) is restated three times and could be trimmed.

4 / 5

Actionability

Check and Fix give concrete, executable instruction ("Verify that every table has a unique accessible name via caption or ARIA attributes", "Add a unique <caption> or aria-label to the table") with concrete attribute names, and code examples are correctly delegated to references/rule.md. It is not anchor 5 because the Explain section is vague meta-direction ("Explain why unique table names are necessary...") rather than actionable guidance.

4 / 5

Workflow Clarity

The Check → Fix → Explain → Code Review structure presents a clear, simple sequence, and verification is addressed ("note how to verify the fix with browser accessibility tooling or assistive tech", plus the Verification section in references/rule.md). This is a non-destructive single-purpose review skill, so no feedback-loop cap applies; it sits at anchor 4 rather than 5 only because the checkpoints live partly in the reference file rather than in an explicit inline sequence.

4 / 5

Progressive Disclosure

The body is a concise overview with well-organized sections, and the single bundle file references/rule.md exists, is clearly signaled ("For full implementation details, code examples, and framework-specific guidance, see references/rule.md"), and is exactly one level deep with no nested references. This matches the anchor for a clear overview with well-signaled one-level-deep references and appropriately split content.

5 / 5

Total

17

/

20

Passed

Description

75%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.

A solid description with an explicit 'Use when...' trigger and multiple concrete inspection actions, held back from the top level by the awkwardly templated phrase "related to Ensure tables have unique accessible names" and missing natural trigger terms like 'caption' and 'aria-label'. Voice is appropriately third-person imperative with no over-claims.

Suggestions

Rewrite the trigger clause using natural user phrasing, e.g. "Use when reviewing HTML tables for accessibility, or when a page has multiple tables that need distinguishing names (captions, aria-labels)."

Replace the embedded rule-title phrase "related to Ensure tables have unique accessible names" with concrete nouns users would actually say — "table captions", "aria-label", "screen readers" — to sharpen both trigger quality and distinctiveness.

Mention the primary remediation capability (adding a unique <caption> or aria-label) alongside the inspection actions to round out the 'what' coverage.

DimensionReasoningScore

Specificity

The description names the domain ("rendered HTML, interactive components, or design-system patterns") and lists several concrete actions: "Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output". It stops short of anchor 5 because coverage is not comprehensive — the core fix actions (adding a <caption> or aria-label) are absent — and the templated phrase "related to Ensure tables have unique accessible names" blurs rather than sharpens the capability list.

4 / 5

Completeness

Both parts are present: an explicit trigger ("Use when reviewing rendered HTML, interactive components, or design-system patterns related to...") and a clear what ("Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output"). The 'when' clause is present but reads awkwardly — the rule title is embedded as a noun phrase instead of a natural trigger condition — matching anchor 4 ('when' could be more explicit or specific) rather than anchor 5's concrete, natural trigger phrasing.

4 / 5

Trigger Term Quality

Good keyword coverage with natural terms a user would plausibly say: "tables", "accessible names", "screen-reader output", "keyboard behavior", "focus", "HTML". It misses a few common variations users actually say, such as "caption", "aria-label", "table headers", or "screen reader" as a standalone noun, so it fits anchor 4 rather than anchor 5.

4 / 5

Distinctiveness Conflict Risk

The niche is mostly distinct — table accessible names with a review/audit orientation — and would not trigger for unrelated skills. There is minor overlap risk with closely related accessibility skills (focus management, keyboard navigation, general screen-reader testing), and the generic "interactive components, or design-system patterns" wording widens the net slightly, placing it at anchor 4 rather than anchor 5's clearly distinct trigger set.

4 / 5

Total

16

/

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-duplicate-name/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.