Skip to content
Skills Library
Programming · Review & audit

validate

/validate

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.

Licence
MIT
Last repository change
23.09.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 23.09.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

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.

Original author description

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.

How it works

  1. When to use
  2. Protocol
  3. Output
Original SKILL.md headings · 59 lines, 326 words
SKILL.md preview
---
name: validate
description: >
  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.
license: MIT
---

# 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
4. **Identify copy type.** Use `MANIFEST.yaml` and local contents to say
   whether the copy appears to be:
   - a canonical source bundle
   - a strict-platform install copy
   - a registry or `.skill` package
   - incomplete or ambiguous
   A derived copy is valid if its own manifest describes exactly the files
   present. Do not treat missing development-only files as corruption unless
   the copy's manifest lists them.
5. **Do not mutate files.** Do not update hashes, bump versions, edit the
   changelog, create a handoff note, or run the close protocol. If the user
   asks to fix mismatches, recommend `/skill-provenance:close` or an explicit
   `validate.sh --update` workflow.

## Output

Keep the response concise:
```text
Bundle: my-skill 1.2.0
Copy type: canonical source bundle
Files: 7 checked, 0 missing, 0 unlisted, 0 mismatched, 0 explicit opt-outs
Result: pass
```
If validation fails, name the specific files and explain that a mismatch
means the file no longer matches the recorded manifest state. This is an
integrity check, not a trust anchor.

Versions

RepositoryScoreLicence
This page · snapsynapse/skill-provenance100MIT
DiogoHSM/driver100MIT
boshu2/agentops100Apache-2.0
RemiPelloux/kill-my-idea100MIT
lalitmaganti/syntaqlite100Apache-2.0
zanderadam/engy100MIT
hirogakatageri/hirokata-claude-marketplace100MIT
fabricio21x/fbs100MIT
Kiran-980/1ml100MIT

Database snapshot: 13.11.2026 · package version 579bf8b06564 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 90open
    Verify a skill bundle's integrity when opening a project. Use when loading a skill project directory and you need to check file completeness, verify SHA-256 hashes against MANIFEST.yaml, detect stale files, review recent changes, or understand what state the bundle is in before…
  • 100skill-provenance
    Version, validate, package, verify, recover, and hand off Agent Skill bundles across local folders, registries, platform uploads, and agent sessions. Use for MANIFEST.yaml, CHANGELOG.md, bundle hashes, stale evals, frontmatter portability, derived skill packages, or version…
  • 95okf-validate-bundle
    OKF — Check that an Open Knowledge Format (OKF) bundle is conformant with the v0.2 spec (§11). Use when asked to validate, lint, or check an OKF bundle, or before committing changes to one. Also migrates a v0.1 bundle to v0.2 with `--migrate`.
  • 100web-app-manifest
    Use when reviewing templates, rendered HTML, or shared components related to Link a Web App Manifest for installability. Validate the final browser-facing markup, not just the source framework abstraction.
  • 95wp-manifest-gate
    The single source for what a command does with each exit code of wp-config.mjs validate, and the named policy that decides what exit 3 (no manifest) means for each command — stop, adopt-or-stop, adopt-or-bare-wp, bare-wp-fallback, scaffold or register. Use when writing or…
  • 95harness-validate
    Use when user invokes /harness-validate or wants to check whether a harness.yaml file is valid according to the Harness Protocol v1 JSON Schema. Reports validation errors with field paths and helpful fix suggestions.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.