CtrlK
BlogDocsLog inGet started
Tessl Logo

frame-title

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

72

Quality

88%

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

SKILL.md
Quality
Evals
Security

Quality

Content

85%

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 clean, well-organized overview that progresses sensibly and appropriately offloads detail to a single one-level-deep reference. Its one gap is actionability: it gives clear instructions but no copy-paste markup example of a correctly titled iframe.

Suggestions

Add a concrete copy-paste example such as `<iframe src="ad.html" title="Advertisement"></iframe>` (and a non-empty vs empty contrast) under Fix.

Include a brief verification step, e.g., checking the Accessibility tree or running an axe-core rule for frame-title, to make the Check section executable.

DimensionReasoningScore

Conciseness

The body is lean with no padding or explanations of concepts Claude already knows; short bullets and imperatives each earn their place, matching the lean-and-efficient anchor.

3 / 3

Actionability

Guidance is concrete ("Add a descriptive title attribute to every <iframe>", "Verify that all <iframe> and <frame> elements have a non-empty 'title' attribute") but lacks a copy-paste HTML example showing the attribute applied, leaving it incomplete rather than fully executable.

2 / 3

Workflow Clarity

As a simple single-purpose skill, the Check -> Fix -> Explain -> Code Review sections give an unambiguous sequence with no destructive or batch operation requiring validation checkpoints, qualifying for the simple-skill score-3 allowance.

3 / 3

Progressive Disclosure

A concise, well-sectioned overview points one level deep to "references/rule.md" (a real, existing file), matching the clear-overview-with-well-signaled-one-level-deep-references anchor.

3 / 3

Total

11

/

12

Passed

Description

92%

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 is concise, third-person, and explicitly pairs a "Use when" trigger with concrete review actions, satisfying completeness and specificity well. Its main weakness is that the generic accessibility opener could conflict with similar frontend a11y skills before the frame-specific qualifier kicks in.

Suggestions

Lead with the frame-title niche (e.g., "Review iframe and frame elements for non-empty title attributes") so the distinct trigger appears before the broad accessibility framing.

Add common natural terms like "iframe title" and "frame title attribute" to broaden trigger-term coverage.

DimensionReasoningScore

Specificity

Names multiple concrete actions — "Check native semantics first", "inspect keyboard behavior, focus flow, accessible names, and screen-reader output" — matching the multiple-specific-actions anchor rather than the partial score-2 anchor.

3 / 3

Completeness

Explicitly answers both what (check semantics, keyboard, focus, accessible names, screen-reader output) and when ("Use when reviewing rendered HTML...") with an explicit trigger clause, matching the score-3 anchor.

3 / 3

Trigger Term Quality

Uses natural terms a user would say ("rendered HTML", "interactive components", "iframes and frames", "screen-reader output") with good coverage, though it omits common variations like "frame title".

3 / 3

Distinctiveness Conflict Risk

The broad opener "reviewing rendered HTML, interactive components, or design-system patterns" overlaps with sibling accessibility skills even though the qualifying "Provide titles for iframes and frames" narrows the niche.

2 / 3

Total

11

/

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.