update-docs SKILL.md skillA
update-docs from aws-samples/sample-apex-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add aws-samples/sample-apex-skills/update-docs@git:20261117.222202aPins git:20261117.222202a in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- aws-samples/sample-apex-skills
- Path
skills/update-docs/SKILL.md- Versions recorded
- 6
- Latest version
- git:20261117.222202a, committed Nov 17, 2026
- First version recorded
- Oct 28, 2026
- Size
- 5,877 bytes
- Repository stars
- 103
- License
- MIT-0
Audit and update every documentation surface in the APEX repo against the current state of skills, steering workflows, README marker tables, and the Docusaurus site under misc/website/. After any change to a skill (rename, retire, add, edit description), walk the repo, re-run script-managed surfaces if their --check fails, and reason through every tracked prose *.md to catch references that need updating. Use after adding/removing/renaming a skill, after editing SKILL.md frontmatter, after…
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
# Update Docs Walk the APEX repo after any content change and bring every documentation surface back into sync. Two categories of surface exist: script-managed (deterministic, re-runnable) and prose (requires reasoning). Handle both in a single pass. ## When to use - A skill was added, removed, renamed, or had its frontmatter edited - A runbook under `skills/apex/runbooks/` (a per-skill `<skill>/*.md` or a top-level `example-*.md`) was added, removed, or renamed - README marker blocks were edited manually - Before opening a PR that touches `skills/` - The user asks to "check docs", "update docs", or "sync documentation" ## Modes **Coding-agent mode** (default in Claude Code): walk the repo, re-run scripts, propose diffs, ask before writing user-facing prose. Auto-apply mechanical fixes (script outputs, simple name substitutions in fenced code blocks). **Chat-only mode** (no file-write tools available): emit the PASS/STALE table + a fix checklist of one-line commands. No file edits. ## Step 1: Detect the change set Determine what changed. Default comparison base is `origin/main`: ```bash …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_tarfw3xjmzl52qcs/d55e2f7b65a3624a5128d5d75f1e086ed6352f187dfb002d50be0d0bd8f0aae5.json
Then /plugin install update-docs@markdownregistry-tarfw3xjmzl52qcs in Claude Code. It installs git:20261117.222202a, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add aws-samples/sample-apex-skills/update-docs@sha256:d55e2f7b65a3624aThe line at the top of this page pins the label git:20261117.222202a, 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_tarfw3xjmzl52qcs)
4 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 aws-samples/sample-apex-skills/update-docs 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 update-docs from somewhere else? Ask it: where did my update-docs 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 6 versions of this file, between Oct 28, 2026 and Nov 17, 2026, about one every 4 days.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261117.222202a latest | 2026-11-17 | 222202a | 5,877 B | A | view · diff |
| git:20261110.9fe6aa3 | 2026-11-10 | 9fe6aa3 | 5,744 B | A | view · diff |
| git:20261108.c5d0aba | 2026-11-08 | c5d0aba | 5,641 B | A | view · diff |
| git:20261108.8c904e6 | 2026-11-08 | 8c904e6 | 5,488 B | A | view · diff |
| git:20261108.0fe0045 | 2026-11-08 | 0fe0045 | 5,381 B | A | view · diff |
| git:20261028.e263a29 | 2026-10-28 | e263a29 | 5,153 B | A | 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/update-docs/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 (5877 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
aws-samples/sample-apex-skills · 103 stars · license MIT-0 · pushed 2026-11-18 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_tarfw3xjmzl52qcs GET https://markdownregistry.com/api/v1/resolve?ref=aws-samples/sample-apex-skills/update-docs GET https://markdownregistry.com/api/v1/blob/d55e2f7b65a3624a5128d5d75f1e086ed6352f187dfb002d50be0d0bd8f0aae5
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.
More from aws-samples/sample-apex-skills
Every file in aws-samples/sample-apex-skills