CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

file-upload-accessibility

Use when reviewing templates, rendered HTML, or shared components related to Make file uploads accessible. Validate the final browser-facing markup, not just the source framework abstraction.

Quality

75%

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/file-upload-accessibility/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, token-efficient overview body with exemplary progressive disclosure to a verified one-level reference file. The main gap is actionability: the body names the right techniques but delegates all executable detail to the reference, leaving someone reading only SKILL.md without markup examples or key implementation specifics.

Suggestions

Inline one compact good/bad markup snippet (a labeled file input with accept attribute and an ARIA live region for upload status) so the body is actionable without opening the reference.

Specify how drag-and-drop zones become keyboard accessible (e.g., a focusable fallback button or input trigger activated by Enter/Space) instead of the bare direction 'Make drag-and-drop zones keyboard accessible'.

Add a post-fix verification step (re-check the rendered markup or run an accessibility audit) to close the Check → Fix loop.

DimensionReasoningScore

Conciseness

The ~30-line body is lean with no concept explanations or padding; every section is 1-2 sentences. Minor trim opportunities exist: the Quick Reference bullets overlap with the Check and Fix sections, and the 'Explain' section is meta-direction, keeping it below the every-token-earns-its-place level of 5.

4 / 5

Actionability

The body names concrete techniques ('accept attribute restrictions', 'ARIA live region feedback', 'drag-and-drop alternatives', 'visible labels') but includes no markup example and omits key details such as which labeling pattern to use or how a drop zone becomes keyboard-operable. All executable specifics (code examples, framework guidance) are delegated to references/rule.md, so the body alone provides some concrete but incomplete guidance rather than mostly-executable guidance.

3 / 5

Workflow Clarity

A clear review sequence is present (Check → Fix → Explain → Code Review), and the Check section defines explicit verification criteria (labels, accept attributes, progress/error feedback) that act as checkpoints for this review-type skill. It stops short of 5 because there is no post-fix re-validation step and the relationship of the 'Code Review' section to the other steps is left implicit.

4 / 5

Progressive Disclosure

The body is a lean overview with a clearly signaled, one-level-deep pointer to references/rule.md for 'full implementation details, code examples, and framework-specific guidance' — verified to exist, contain the code examples, and reference no further files — plus the source rule URL. Content is appropriately split between overview and detail file with easy navigation.

5 / 5

Total

16

/

20

Passed

Description

70%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 a clear niche, held back by an under-specified 'what': it says where to look (rendered markup, not framework abstraction) but not what to check (labels, accept attributes, ARIA feedback, keyboard-accessible drop zones). The embedded rule-name phrase "related to Make file uploads accessible" also reads awkwardly mid-sentence.

Suggestions

Enumerate the concrete checks in the description itself, e.g. 'Check that file inputs have associated labels, accept attribute restrictions, accessible progress/error feedback, and keyboard-operable drop zones.'

Add natural trigger synonyms users would actually say — 'a11y', 'screen reader', 'drag and drop', 'file input' — to improve matching beyond the current term set.

Rephrase 'related to Make file uploads accessible' into a natural capability statement instead of embedding the rule name mid-sentence.

DimensionReasoningScore

Specificity

The description names the domain (file upload accessibility in rendered markup) and 1-2 concrete actions ("reviewing templates, rendered HTML, or shared components", "Validate the final browser-facing markup") but never enumerates the specific checks performed (labels, accept attributes, ARIA feedback, keyboard-accessible drop zones). It falls short of 4 because only two broad actions are listed rather than several specific ones, and exceeds 2 because it goes beyond merely naming the domain.

3 / 5

Completeness

Both parts are present: an explicit trigger ("Use when reviewing templates, rendered HTML, or shared components...") and a what ("Validate the final browser-facing markup, not just the source framework abstraction"). The 'what' could be more explicit about what the skill actually does (the concrete accessibility checks), so it does not reach the 5 anchor's fully concrete what-and-when pairing.

4 / 5

Trigger Term Quality

Good natural keyword coverage: "file uploads", "templates", "rendered HTML", "shared components", "browser-facing markup" are phrases users would naturally say. Missing common variations and synonyms such as "a11y", "screen reader", "drag and drop", "file input", or "WCAG", which keeps it below 5 but above 3's partial coverage.

4 / 5

Distinctiveness Conflict Risk

It carves a clear niche (file-upload accessibility in final browser-facing markup) with distinct triggers. Minor overlap risk remains with general HTML or component-review skills because "templates, rendered HTML, shared components" are broad frontend terms that could fire on unrelated review requests, preventing a 5.

4 / 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/file-upload-accessibility/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.