phase-validate SKILL.md skillA
phase-validate from yarlson/yarstack is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add yarlson/yarstack/phase-validate@git:20261017.2f2e03bPins git:20261017.2f2e03b in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- yarlson/yarstack
- Path
plugins/yarstack/skills/phase-validate/SKILL.md- Versions recorded
- 4
- Latest version
- git:20261017.2f2e03b, committed Oct 17, 2026
- First version recorded
- Jul 17, 2026
- Size
- 2,233 bytes
- Repository stars
- 3
- License
- MIT
Validate exactly one implemented phase or scoped change against its authoritative contract. Use after implementation to re-derive criterion-level conclusions from current evidence and fix only required implementation gaps.
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
# Phase Validation Own contract validation between implementation and structural review. ## Workflow 1. Read the authoritative contract and applicable repository rules unconditionally. 2. Enumerate each observable acceptance criterion, invariant, required progress, environmental assumption, and failure case, then map it to implementation and evidence. 3. Inspect changed files, tests, failure paths, cleanup, side effects, and required checks without trusting implementation claims. Evidence verifies a criterion only when it would fail if the criterion were not met: a test that passes both before and after the change does not verify new behavior. Confirm that each evidence method covers the relevant inputs, states, ordering, and failures. 4. Invoke a focused review skill only when its trigger applies. Treat its findings as claims: verify each one from evidence, and do not treat agreement between reviewers as proof. Keep any fixes within this phase's authority. 5. Use `plan-update` or `spec-update` when the contract is incorrect or incomplete. Do not invent behavior. 6. Fix only implementation gaps required by the selected contract. …
Read the whole file at its exact version.
How to install
mdr add yarlson/yarstack/phase-validate@sha256:5ea92a237b2b2db1The line at the top of this page pins the label git:20261017.2f2e03b, 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_3ac62yh6nvrp6b4v)
4 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 4 versions of this file, between Jul 17, 2026 and Oct 17, 2026, about one every 31 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261017.2f2e03b latest | 2026-10-17 | 2f2e03b | 2,233 B | A | view · diff |
| git:20260720.2e4f3b4 | 2026-07-20 | 2e4f3b4 | 2,142 B | A | view · diff |
| git:20260718.188cd11 | 2026-07-18 | 188cd11 | 1,655 B | A | view · diff |
| git:20260717.dc9a72d | 2026-07-17 | dc9a72d | 1,682 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 (2233 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
yarlson/yarstack · 3 stars · license MIT · pushed 2026-11-05 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_3ac62yh6nvrp6b4v GET https://markdownregistry.com/api/v1/resolve?ref=yarlson/yarstack/phase-validate GET https://markdownregistry.com/api/v1/blob/5ea92a237b2b2db1d4ea76f43c7555b4cecea4cec210ff24ac6b12dbf4b630a7
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.