anchor-links SKILL.md skillA
anchor-links from mgifford/accessibility-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add mgifford/accessibility-skills/anchor-links@git:20260722.125074bPins git:20260722.125074b in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- mgifford/accessibility-skills
- Path
skills/anchor-links/SKILL.md- Versions recorded
- 3
- Latest version
- git:20260722.125074b, committed Jul 22, 2026
- First version recorded
- Mar 31, 2026
- Size
- 17,896 bytes
- Repository stars
- 61
- License
- AGPL-3.0
Load this skill whenever the project contains in-page anchor links, skip links, fragment identifiers, or heading links. Under no circumstances omit accessible anchor-link requirements when such links exist. Ensure every anchor link has meaningful text, a reachable target, and a visible focus indicator. Apply these rules when creating or reviewing any in-page navigation.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Anchor Links Accessibility Skill > **Canonical source**: `examples/ANCHOR_LINKS_ACCESSIBILITY_BEST_PRACTICES.md` in `mgifford/ACCESSIBILITY.md` > This skill is derived from that file. When in doubt, the example is authoritative. Apply these rules when creating or reviewing in-page anchor links, skip links, or heading links. **Only load this skill if the project contains in-page navigation or skip links.** --- ## Core Mandate Every anchor link must have meaningful text, a reachable target with a visible focus indicator, and must not cause motion-related harm. Use a real `<a>` element with an `href` for navigation; use a button only for actions that don't navigate. Prefer native fragment navigation before adding JavaScript. --- ## Severity Scale (this skill) | Level | Meaning | |---|---| | **Critical** | Anchor navigation blocks access or causes a trap | | **Serious** | Skip link broken or permanently hidden; smooth scroll triggers vestibular harm | | **Moderate** | Focus indicator obscured by sticky header; link text ambiguous in context | | **Minor** | Non-slug IDs; missing `aria-current` in table of contents | --- ## Use Links for Navigation, Not Actions …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_aay67qzv2bxj5wwa/98b4998d3ac257e36381be4822233e37e28a73390275180da40d22b369b1d377.json
Then /plugin install anchor-links@markdownregistry-aay67qzv2bxj5wwa in Claude Code. It installs git:20260722.125074b, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add mgifford/accessibility-skills/anchor-links@sha256:98b4998d3ac257e3The line at the top of this page pins the label git:20260722.125074b, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_aay67qzv2bxj5wwa)
2 badge image fetches in 30 days. What the badge shows.
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it: what changed in mgifford/accessibility-skills/anchor-links since the version I have? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.
Got a copy of anchor-links from somewhere else? Ask it: where did my anchor-links come from, and what was changed? It names the public original, the version yours is closest to and every changed line. The text is not kept.
Versions
The registry has recorded 3 versions of this file, between Mar 31, 2026 and Jul 22, 2026, about one every 56 days. Its first recorded version is graded C and its latest A.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260722.125074b latest | 2026-07-22 | 125074b | 17,896 B | A | view · diff |
| git:20260331.f09d889 | 2026-03-31 | f09d889 | 6,860 B | A | view · diff |
| git:20260331.0b2aead | 2026-03-31 | 0b2aead | 6,434 B | C | view |
Committed this skill to a repository? Install the markdownregistry skill updates app on it, or on all of them. When the registry saves a newer version, a pull request brings your copy to it within minutes, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
It asks to read and write contents and pull requests, and to read metadata. No workflow file, no Actions setting, nothing runs on your runners. Uninstall it and everything the registry kept about your repository is deleted.
Committed this skill to a repository? Add one workflow file, and when a newer version is saved, a pull request brings your copy to it, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
mkdir -p .github/workflows && curl -fsSL https://markdownregistry.com/ci/skill-updates.yml -o .github/workflows/skill-updates.yml
It runs daily on GitHub Actions, no key and no account. Read the workflow before you add it.
Installed this file, say at .claude/skills/anchor-links/SKILL.md? Drop it here to learn which saved version you have and what changed since. Your browser works out its SHA-256 fingerprint and sends only that; the file itself never leaves your computer.
Or paste its contents
Your agent can run this same check on the agent markdown files you have installed, up to 50 in one ask. Add the registry once:
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it to check the files you have installed. No key and no account.
From the root of your project, one line hashes each installed skill's SKILL.md, your AGENTS.md and your CLAUDE.md, and asks the registry once. Only the fingerprints and paths are sent.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --data-binary @- https://markdownregistry.com/api/v1/check-copies
In CI, add --fail-with-body: the answer is 409 when any file is behind, so the step fails and still prints which files.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --fail-with-body --data-binary @- https://markdownregistry.com/api/v1/check-copies
No sha256sum on your machine? shasum -a 256 prints the same lines.
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (17896 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
mgifford/accessibility-skills · 61 stars · license AGPL-3.0 · pushed 2026-11-12 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_aay67qzv2bxj5wwa GET https://markdownregistry.com/api/v1/resolve?ref=mgifford/accessibility-skills/anchor-links GET https://markdownregistry.com/api/v1/blob/98b4998d3ac257e36381be4822233e37e28a73390275180da40d22b369b1d377
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.