CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.

Quality

78%

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/frame-title/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

77%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 well-structured, appropriately sized overview with a concrete check/fix workflow and exemplary progressive disclosure to a verified references/rule.md. Its only real weakness is moderate token waste: a rationale paragraph, redundant Quick Reference bullets, and boilerplate Code Review text that covers checks irrelevant to frame titles.

Suggestions

Cut the intro rationale sentence ("Frame titles allow users of assistive technology to..."), the third Quick Reference bullet, and merge Quick Reference into Check/Fix — Claude already knows why frame titles matter.

Trim the Code Review section's irrelevant boilerplate ("roles, labels, focus behavior, or keyboard interactions") down to what applies to frame titles, e.g. flagging specific <iframe>/<frame> elements missing or with empty/non-descriptive title attributes.

Add one inline good/bad example (e.g. <iframe src="https://example.com/ad"></iframe> vs <iframe title="Advertisement" src="..."></iframe>) so the fix is copy-paste ready without opening the reference.

DimensionReasoningScore

Conciseness

The core Check/Fix guidance is tight, but there is avoidable padding: the intro rationale ("Frame titles allow users of assistive technology to quickly understand the content of an iframe... which is crucial for navigation and orientation"), the redundant Quick Reference bullet "Helps screen reader users navigate between frames", Quick Reference overlapping Check/Fix, and Code Review text covering checks irrelevant to frame titles ("roles, labels, focus behavior, or keyboard interactions"). This matches anchor 3 (mostly efficient with some unnecessary explanation); it is not anchor 2 because the document is short and the operative guidance earns its tokens.

3 / 5

Actionability

The Check and Fix sections give concrete, executable instructions — "Verify that all <iframe> and <frame> elements have a non-empty 'title' attribute" and "Add a descriptive 'title' attribute to the <iframe> tag that explains what the embedded content is" — with executable markup examples correctly placed in references/rule.md (verified to contain real <iframe title="..."> examples). This matches anchor 4 (mostly executable with minor gaps); the absence of an inline good/bad title example and the vague boilerplate in Code Review keep it from anchor 5.

4 / 5

Workflow Clarity

This is a simple, single-purpose skill under 50 lines with a clear Check → Fix → Explain → Code Review sequence and an unambiguous core action (verify a non-empty title attribute on every frame), so the simple-skill exception applies and workflow clarity earns 5. No destructive or batch operations are involved, so the validation cap does not apply.

5 / 5

Progressive Disclosure

The body is a concise overview with details appropriately split into a clearly signaled, one-level-deep reference — "For full implementation details, code examples, and framework-specific guidance, see `references/rule.md`" — and that file exists and contains the code examples without nesting further references. This matches anchor 5 (clear overview, well-signaled one-level-deep references, easy navigation).

5 / 5

Total

17

/

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.

The description has an explicit "Use when..." trigger and a concrete action list, placing it solidly above average. Its main weakness is that the what-portion is generic accessibility-review boilerplate shared across sibling rule skills rather than rule-specific actions, weakening both completeness and distinctiveness.

Suggestions

Replace the generic review playbook with rule-specific actions in the what-portion, e.g. "Verifies every <iframe> and <frame> has a non-empty, descriptive title attribute; guides adding titles that name the embedded content."

Lead with the rule-specific function and keywords ("title attribute", "iframes", "accessibility") instead of embedding the rule name mid-phrase ("related to Provide titles for iframes and frames"), so the skill is distinguishable from sibling accessibility rule skills.

Add missing natural trigger terms such as "title attribute", "accessibility"/"a11y", and "embedded content" (ads, video embeds, social media widgets) to improve trigger and distinctiveness scores.

DimensionReasoningScore

Specificity

The description lists several concrete actions — "Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output" — which matches anchor 4 (several specific actions, minor gaps). It never states the rule-specific actions (verify a non-empty title attribute on iframes/frames, add a descriptive one), so it falls short of anchor 5's comprehensive coverage while exceeding anchor 3's 1-2 actions.

4 / 5

Completeness

Both parts are present: an explicit "Use when reviewing rendered HTML, interactive components, or design-system patterns..." clause and a what-portion listing concrete inspection actions, matching anchor 4. The what describes the generic accessibility review procedure ("Check native semantics first, then inspect keyboard behavior...") rather than the frame-title check itself, and "where relevant" hedges it, so it does not clearly earn anchor 5; the when is explicit, so it is above anchor 3.

4 / 5

Trigger Term Quality

Natural terms users would say are present: "iframes and frames", "rendered HTML", "screen-reader output", "focus flow", matching anchor 4 (good coverage, a few natural terms missing). It lacks "title attribute", "accessibility"/"a11y", and "embedded content", so it does not reach anchor 5's comprehensive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

The trigger framing ("reviewing rendered HTML, interactive components, or design-system patterns") and the inspection actions are boilerplate shared across a whole family of accessibility rule skills; only the mid-sentence rule name "Provide titles for iframes and frames" distinguishes this skill, matching anchor 3 (somewhat specific but could still overlap with similar skills). It is not anchor 4 because the overlap with sibling a11y skills is more than minor, and not anchor 2 because it is scoped to frame titles rather than being very broad.

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/frame-title/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.