multica-verification SKILL.md skillA
multica-verification from it235/multica-best-practices is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add it235/multica-best-practices/multica-verification@git:20260910.699a593Pins git:20260910.699a593 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- it235/multica-best-practices
- Path
templates/en_US/skills/leader/multica-verification/SKILL.md- Versions recorded
- 2
- Latest version
- git:20260910.699a593, committed Sep 10, 2026
- First version recorded
- Sep 10, 2026
- Size
- 2,598 bytes
- Repository stars
- 237
- License
- MIT
Gatekeeping function: objectively check whether an artifact satisfies the acceptance criteria. Triggered by the Leader to rerun at gate points (G1/G2/G3); members can also use it for self-check. Used for design review / implementation acceptance / test-report review.
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
# Verification (gatekeeping) ## What this is Verification is a **function**, not a role. It answers one question: > For every acceptance criterion, is there objective evidence that it is satisfied? The key: verification must be an **objectively decidable action** (run commands, read output, map item by item), not "I feel it's fine." It doesn't rely on anyone's character — it relies on the evidence itself. Whoever runs it, the result is the same. ## Who executes it - **Gatekeeping**: the **Leader** triggers this Skill at the gate points (G1 / G2 / G3) and reruns independently. The Leader produces no artifacts, so it's naturally a third party. - **Self-check**: after finishing, a producer may first run this Skill to self-verify (pasting the command output), but self-check is not gatekeeping — gatekeeping must be rerun by a non-producer. > The gate issuer must be a different party from the gated. Authors cannot stamp "PASS" on themselves. ## Process 1. Read the Issue's acceptance criteria. 2. Map every criterion to evidence (which test / which command / which output). 3. **Rerun** the verification commands; don't cite someone else's described output. …
Read the whole file at its exact version.
How to install
mdr add it235/multica-best-practices/multica-verification@sha256:f48534d4023de37bThe line at the top of this page pins the label git:20260910.699a593, 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_lvs3q3omw2rgz7ho)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, all committed on Sep 10, 2026.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260910.699a593 latest | 2026-09-10 | 699a593 | 2,598 B | A | view · diff |
| git:20260910.8db057c | 2026-09-10 | 8db057c | 2,590 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 (2598 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
it235/multica-best-practices · 237 stars · license MIT · pushed 2026-11-04 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_lvs3q3omw2rgz7ho GET https://markdownregistry.com/api/v1/resolve?ref=it235/multica-best-practices/multica-verification GET https://markdownregistry.com/api/v1/blob/f48534d4023de37bde25502c7706fcbcd2ed87c865fa7144a2e6c9bb0f02c98e
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 it235/multica-best-practices
Every file in it235/multica-best-practices