CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

object-alt

Use when reviewing rendered HTML, interactive components, or design-system patterns related to Provide alternative text for objects. Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output where relevant.

Quality

76%

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/object-alt/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.

A well-organized, brief skill body with clean section structure, a verification cue, and exemplary progressive disclosure via a single one-level-deep reference. The weakest area is actionability: the body gives specific direction but no inline good/bad markup example, leaving the executable detail entirely in the reference file.

Suggestions

Include a short inline good/bad markup pair (an `<object>` element with and without descriptive fallback content) so the Fix guidance is actionable without opening the reference.

Deduplicate the Check section against the nearly identical Quick Reference bullet, replacing the repetition with specifics (e.g., what counts as 'descriptive' fallback, how to handle nested `<object>` fallback for unsupported formats).

Add an explicit re-check step after applying the fix (e.g., reload with the object blocked or re-inspect with a screen reader) to close the workflow's feedback loop.

DimensionReasoningScore

Conciseness

The body is lean overall, but the opening rationale ("If an object fails to load or the user's browser doesn't support the format, alternative text ensures that the information is still accessible") explains a concept Claude already knows, and the Check section nearly repeats a Quick Reference bullet ("Check all `<object>` elements in the HTML to ensure they contain descriptive fallback content"). These minor trimmable instances match anchor 4 rather than anchor 5.

4 / 5

Actionability

Guidance names the exact element and action ("Check all `<object>` elements in the HTML..."; "Add alternative text or a semantic fallback inside the `<object>` tags") but includes no markup example of compliant fallback — the single most useful artifact for this rule is deferred entirely to references/rule.md. This matches anchor 3 (some concrete guidance, missing key details) rather than anchor 4's mostly-executable guidance.

3 / 5

Workflow Clarity

Sections form a coherent Quick Reference → Check → Fix → Explain → Code Review sequence, and verification is present ("note how to verify the fix with browser accessibility tooling or assistive tech"), matching anchor 4. Not anchor 5 because there is no explicit feedback loop (re-check after fixing) and the sequence is implied by section order rather than stated.

4 / 5

Progressive Disclosure

The body is a concise overview with a clearly signaled, one-level-deep pointer: "For full implementation details, code examples, and framework-specific guidance, see `references/rule.md`." The bundle confirms the split is appropriate — references/rule.md exists and contains only external spec links (MDN, HTML standard, WCAG) with no nested skill references — matching anchor 5 exactly.

5 / 5

Total

16

/

20

Passed

Description

71%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 solidly structured description with an explicit 'Use when...' trigger and several concrete actions, scoring 4 on specificity, trigger quality, and completeness. Its main weakness is distinctiveness: the listed actions are generic to nearly all accessibility-review skills, leaving the embedded rule title as the only differentiator.

Suggestions

State the rule-specific task as the 'what' (e.g., "Verify every `<object>` element contains descriptive fallback content and flag violations") so it is concrete and distinct from generic a11y review methodology.

Add distinguishing trigger terms such as "`<object>` elements", "alt text", "fallback content", or "embedded objects" to reduce overlap with other accessibility skills and capture natural user phrasing.

Trim or narrow the generic checklist (keyboard behavior, focus flow, accessible names) to the checks specific to object fallback content, since that list matches almost any accessibility skill.

DimensionReasoningScore

Specificity

The description lists several concrete actions ("Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output") within a named domain ("reviewing rendered HTML, interactive components, or design-system patterns"). It falls short of anchor 5 because the actions are generic accessibility-review methodology — the rule-specific task of verifying `<object>` fallback content is never stated — but exceeds anchor 3 with more than 1-2 concrete actions and broad coverage.

4 / 5

Completeness

Both parts are explicitly present: "Use when reviewing rendered HTML..." answers when, and "Check native semantics first, then inspect..." answers what. Not anchor 5 because the 'what' describes generic review process rather than the concrete rule-specific deliverable (no mention of `<object>` elements or fallback verification); well above anchor 3 since the 'when' is explicit, not weakly implied.

4 / 5

Trigger Term Quality

Terms like "rendered HTML", "interactive components", "keyboard behavior", "accessible names", "screen-reader output", and "alternative text" give good natural-keyword coverage matching anchor 4. Not anchor 5 because common variations users actually say ("alt text", "a11y", "accessibility", "`<object>`", "fallback content") are missing, and "Provide alternative text for objects" reads as a rule title rather than natural user phrasing.

4 / 5

Distinctiveness Conflict Risk

The action list ("Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output") applies to virtually any accessibility-review skill, so it would equally trigger for images-alt, button-name, or focus-order needs — only the embedded rule title "related to Provide alternative text for objects" differentiates. Fits anchor 3 (somewhat specific but real overlap risk with similar skills), below anchor 4 whose overlap risk must be minor.

3 / 5

Total

15

/

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/object-alt/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.