Guide · Agent skill
How to use the Form Label Checker agent skill (form-labels)
Updated · written with AI from the project's own documentation and checked against our catalogue data
The form-labels skill is an agent skill for Claude that reviews web page markup and interactive components to check that every input, select and textarea has a proper label. It is aimed at front-end developers, designers and accessibility auditors. After reading this guide you will know what the skill does, how to install it, how to ask for a review in plain language, and what to expect from its output.
Form Label Checkerthedaviddias/Front-End-Checklist · MIT Download the skill Quick start
- 1Download the ZIP. Get the form-labels skill ZIP from this page.
- 2Unzip into a skills folder. Extract it into ~/.claude/skills/ for personal use, or into a project's .claude/skills/ folder.
- 3Or upload in the Claude apps. Go to Settings, then Capabilities, then Skills, and upload the skill.
- 4Send a review request. Paste your form markup or describe the component and ask for a label check.
- 5Read the findings. Check each flagged element and the suggested for and id or fieldset and legend fix.
- 6Verify the fix. Confirm the changes with browser accessibility tooling or assistive technology.
What is an agent skill and what does form-labels make the agent do?
An agent skill is a folder containing instructions (a SKILL.md file) and supporting reference files that an AI agent loads when a task matches the skill's description. The form-labels skill tells the agent to check that form controls are labelled so screen readers can announce what each field is for.
When the skill is active, the agent reviews rendered HTML and interactive components. It flags placeholder-only fields, flags groups of checkboxes or radio buttons that lack a fieldset and legend, and suggests concrete fixes such as adding a label with a for attribute that matches the id of the input. The skill works from a checklist-style rule and a reference document. It does not run any tooling itself.
- Checks that inputs, selects and textareas have associated labels
- Flags placeholder-only fields
- Flags related checkboxes or radio buttons without a fieldset and legend
- Suggests specific fixes, including for and id attributes
How do you install the form-labels skill?
You can install the skill in one of two ways. Download the ZIP file from this page and unzip it into your personal skills folder at ~/.claude/skills/, or into a project's .claude/skills/ folder if you want it available only for that project.
Alternatively, upload the skill in the Claude apps under Settings, then Capabilities, then Skills.
- Personal install: unzip into ~/.claude/skills/
- Project install: unzip into the project's .claude/skills/ folder
- Claude apps: Settings → Capabilities → Skills, then upload
Files included in the skill
The skill folder contains two files. SKILL.md holds the skill's description, metadata and the Check, Fix and Code Review guidance. references/rule.md holds fuller implementation details, correct and incorrect HTML examples, and the reasons labels matter.
- SKILL.md: triggering description and review instructions
- references/rule.md: detailed rule with HTML examples
How do you trigger the skill with a natural request?
You do not need a special command. Describe the task in plain language that mentions forms, labels or the related patterns. The skill's description covers reviewing rendered HTML, interactive components and design-system patterns for labelling form controls, so requests about those topics are the ones most likely to load it.
Include the markup or the page so the agent has something concrete to review.
- Review this signup form for label problems and show me the fixes.
- Check this checkbox group for a missing fieldset and legend.
- Audit the form components in our design system for accessible labels.
- Are any of these inputs placeholder-only with no real label?
What output should you expect?
The agent names the exact elements it reviewed, states which ones violate the rule, and proposes a fix for each. For a missing label, the suggested fix follows the pattern in the source: a label element whose for attribute matches the input's id.
The skill's guidance also notes how to verify fixes with browser accessibility tooling or assistive technology. The skill itself does not run those tools, so you should confirm results yourself.
<label for="email-address">Email Address</label>
<input type="email" id="email-address" name="email">What are the requirements, safety notes and limits?
The skill lists no requirements. It does not run scripts and does not use the network, so it only reads the material you give it and the reference files in its folder.
The skill gives guidance and review, not certified results. It is not a replacement for automated testing or a proof of WCAG compliance, and it does not apply to form tools outside HTML.
- Requires: nothing listed
- Runs scripts: no
- Uses network: no
- Not suitable as proof of WCAG compliance or as automated testing
What people use it for
- Reviewing a signup or checkout form before release
- Checking that design-system form patterns label their controls
- Flagging placeholder-only fields in an existing page during an accessibility audit
- Checking radio button and checkbox groups for a fieldset and legend
Frequently asked questions
Is the form-labels skill free?
The skill is released under the MIT licence, as stated on this page. Check the licence file in the repository for the full terms.
What do I need to use form-labels?
The skill lists no requirements. It does not run scripts and does not use the network, so no extra tools are needed to load it.
How do I install an agent skill like form-labels?
Unzip the downloaded skill into ~/.claude/skills/ or a project's .claude/skills/ folder, or upload it under Settings, Capabilities, Skills in the Claude apps.
Why does my form need a label if it has placeholder text?
Placeholder text is not a label and must not be the only field name. Screen readers need a real label, which the skill checks for.
Does form-labels check WCAG compliance?
No. The skill gives guidance and review, not certified results, so it cannot prove WCAG compliance on its own.
How does form-labels compare to automated accessibility testing tools?
The skill works from a checklist rule and reference document and does not run tooling. Use browser accessibility tools or assistive technology to verify the fixes it suggests.
New agent skills, repos and AI tools — every week
The best new skills and open-source projects, the fastest-growing repos, and one free prompt. Five minutes to read. Unsubscribe anytime.
Our verdict
Front-end developers reviewing forms before release, designers checking form patterns in a design system, and teams running accessibility audits of existing pages will get useful, specific label reviews from this skill. If you need automated testing or certified compliance results, or your forms are not HTML-based, pick a different tool.
Download the skill