
Descriptive Anchor Text Audit
Checks that web link text is descriptive instead of generic like 'click here'.
- Repository
- thedaviddias/Front-End-Checklist
- Stars
- 74,632
- Licence
- MIT
- Files
- 2 files
What it does
This skill gives an AI agent a checklist for reviewing links on a website so the link text says what the target page is about, rather than vague phrases like 'click here' or 'read more'. Once installed, when asked to audit SEO or accessibility, the agent will look for these generic links, suggest clearer wording, and check the rendered page output rather than only the source files. It is a single written guide with no executable tools described.
Great for
- Web developers reviewing site templates for SEO and accessibility problems
- SEO specialists checking internal linking quality
- Content editors who want clearer link wording
Skip it if
- Sites where you need automated scanning of every page at scale, since the skill only gives guidance and does not include a crawler (the agent would need its own tools)
- Anyone expecting legal compliance certification, because the skill is a best-practice checklist, not an accessibility audit standard
Try asking
- “Audit the templates in this project for generic link text like 'click here' and suggest better wording”
- “Review our blog navigation and footer links for descriptive anchor text”
- “Explain to my team why 'read more' links hurt screen reader users and how to fix them”
Install in 3 steps
- 1
Download the skill
The ZIP contains the 2 original files, the MIT licence and an attribution note.
anchor-text.zip - 2
Add it to your agent
Claude Code (all projects)
mkdir -p ~/.claude/skills && unzip anchor-text.zip -d ~/.claude/skills/Claude Code / Agent SDK (this project only)
mkdir -p .claude/skills && unzip anchor-text.zip -d .claude/skills/Claude apps (web/desktop): Settings → Capabilities → Skills → Upload skill, and choose the ZIP.
- 3
Ask for the task
No special command needed — the agent reads the skill's description and loads it when your request matches. Try one of the prompts above.
Get better results
- Point the agent at specific files or routes so it can flag exact templates that need changes.
- Ask it to verify the rendered HTML output, since the skill recommends checking the final page rather than only source code.
- Read references/rule.md for framework-specific examples if you need implementation detail, as SKILL.md alone is brief.
What's inside
- references/rule.md
- SKILL.md
Redistributed unmodified from thedaviddias/Front-End-Checklist under the MIT licence. The assessment was drafted with AI from the skill's files on 2026-10-29. Skills can instruct your agent to run code — read SKILL.md and any scripts before installing.