validate SKILL.md skillA
validate from snapsynapse/skill-provenance is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add snapsynapse/skill-provenance/validate@git:20260924.5ab4070Pins git:20260924.5ab4070 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- snapsynapse/skill-provenance
- Path
skills/validate/SKILL.md- Versions recorded
- 4
- Latest version
- git:20260924.5ab4070, committed Sep 24, 2026
- First version recorded
- May 19, 2026
- Size
- 2,591 bytes
- Repository stars
- 7
- License
- MIT
Run a focused validation check for a skill bundle. Use when the user asks to validate, verify hashes, check MANIFEST.yaml, confirm files are present, or distinguish a canonical bundle from a derived install or registry copy without opening or closing a full editing session.
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
# Skill Provenance: Validate Run the hash and inventory check only. This is a narrow verification command, not the full open-session or close-session protocol. ## When to use Run `/skill-provenance:validate` when the user wants to know whether the current bundle matches its `MANIFEST.yaml`, whether files are missing, or whether a copy appears to be canonical or derived. ## Protocol 1. **Locate the bundle root.** Use the directory containing `MANIFEST.yaml`. If no manifest exists, report that the bundle is unversioned and suggest `/skill-provenance:bootstrap`. 2. **Run `validate.sh` when available.** Prefer: ```bash ./validate.sh ``` If the script is not present, compute SHA-256 hashes for files listed in `MANIFEST.yaml` and compare them manually. 3. **Report validation results only.** Include: - File count checked - Missing files - Unlisted files, symlinks, or special files (`UNLISTED` lines) - Hash mismatches - Explicit `hash: null` opt-outs - Structural, unsafe-path, duplicate-path, and symlink errors - Matching, stale, or malformed `validated_against` records when present - Exit code or equivalent pass/fail result …
Read the whole file at its exact version.
How to install
mdr add snapsynapse/skill-provenance/validate@sha256:f18385118862a882The line at the top of this page pins the label git:20260924.5ab4070, 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_rh3qyr2ojardwpgp)
4 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 4 versions of this file, between May 19, 2026 and Sep 24, 2026, about one every 43 days. Its first recorded version is graded B and its latest A.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260924.5ab4070 latest | 2026-09-24 | 5ab4070 | 2,591 B | A | view · diff |
| git:20260820.3ed2639 | 2026-08-20 | 3ed2639 | 2,512 B | A | view · diff |
| git:20260721.8002a07 | 2026-07-21 | 8002a07 | 2,484 B | B | view · diff |
| git:20260519.8b9bd7b | 2026-05-19 | 8b9bd7b | 2,344 B | B | view |
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 (2591 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
snapsynapse/skill-provenance · 7 stars · license MIT · pushed 2026-09-24 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_rh3qyr2ojardwpgp GET https://markdownregistry.com/api/v1/resolve?ref=snapsynapse/skill-provenance/validate GET https://markdownregistry.com/api/v1/blob/f18385118862a882eef1627e63d706107d5f2ceb91a54f07e2846d5bfcc03ec1
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 snapsynapse/skill-provenance
Every file in snapsynapse/skill-provenance