validate SKILL.md skillA
validate from ronaknnathani/relay is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add ronaknnathani/relay/validate@git:20260629.7380310Pins git:20260629.7380310 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- ronaknnathani/relay
- Path
skills/validate/SKILL.md- Versions recorded
- 3
- Latest version
- git:20260629.7380310, committed Jun 29, 2026
- First version recorded
- Jun 29, 2026
- Size
- 5,266 bytes
- Repository stars
- 43
- License
- MIT
Verify a change is ready to ship by checking it against its acceptance criteria and running the repo's own quality gates in order, then report a pass/fail verdict with the exact failures. Use to decide go/no-go right before shipping — when you want a pass/fail verdict against acceptance criteria and the repo's quality gates (lint/build/test), not a code critique (use `review` for that). It reports — it does not fix (route failures to `pr-fix`/`implement`) and does not ship.
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
# Validate Decide whether a change is ready to ship and report the verdict — pass, or fail with the exact failures someone else can act on. The bar: every acceptance criterion from `clarify`/`plan` is demonstrably met, and every quality gate the repo defines is green, each shown by a command or observation rather than asserted. This skill is a gate, not a fixer: on failure it hands precise error-feedback to `pr-fix` or `implement` and stops. It does **not** edit code and does **not** ship. ## Process 1. **Gather the acceptance criteria.** Read the Success criteria from the `clarify`/`plan` artifacts. These are the goal-backward targets — what must be TRUE about the codebase. If no artifact exists, reconstruct the criteria from the task description and list them, so the verdict is checkable. 2. **Discover the repo's own gate commands.** Find how *this* repo lints, type-checks, tests, builds, and audits — from its scripts/manifest/CI config (`explore` when it isn't obvious). Use the repo's actual commands; never substitute a generic command or invent a gate the repo doesn't define. A gate the repo doesn't have is skipped as not-applicable (and noted), not faked. …
Read the whole file at its exact version.
How to install
mdr add ronaknnathani/relay/validate@sha256:6d894fe22d4bf3c9The line at the top of this page pins the label git:20260629.7380310, 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_zxhcefvbbs623sir)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 3 versions of this file, all committed on Jun 29, 2026.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260629.7380310 latest | 2026-06-29 | 7380310 | 5,266 B | A | view · diff |
| git:20260629.9a6d3b4 | 2026-06-29 | 9a6d3b4 | 5,150 B | A | view · diff |
| git:20260629.99be5fe | 2026-06-29 | 99be5fe | 3,242 B | A | 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 (5266 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
ronaknnathani/relay · 43 stars · license MIT · pushed 2026-11-06 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_zxhcefvbbs623sir GET https://markdownregistry.com/api/v1/resolve?ref=ronaknnathani/relay/validate GET https://markdownregistry.com/api/v1/blob/6d894fe22d4bf3c9a086e66fcc00727d2f99a6b3cc74eb1b8d00e49d36ad9f64
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 ronaknnathani/relay
Every file in ronaknnathani/relay