verify-outcome SKILL.md skillA
verify-outcome from kalabint/llm-tooling is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add kalabint/llm-tooling/verify-outcome@git:20260907.47ea7d2Pins git:20260907.47ea7d2 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- kalabint/llm-tooling
- Path
skills/verify-outcome/SKILL.md- Versions recorded
- 1
- Latest version
- git:20260907.47ea7d2, committed Sep 7, 2026
- Size
- 633 bytes
- Repository stars
- 6
- License
- AGPL-3.0
Verify the user-facing outcome, and verify that your metric can even see the defect class you care about.
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
# Verify the outcome A passing test or a point-wise statistic can be blind to the failure that matters. Point stats miss structure; presence gates miss absences. **Why:** "the check passed" is worthless if the check cannot perceive the bug. You confirm the wrong thing and call it done. **How to apply:** confirm the actual end-to-end result a user would experience. Separately, ask what defect class your metric is structurally unable to detect, then add a check that can see it.
Read the whole file at its exact version.
How to install
mdr add kalabint/llm-tooling/verify-outcome@sha256:36fd00c8ba51e9fbThe line at the top of this page pins the label git:20260907.47ea7d2, 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_ik55zg44z7zgydqr)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Sep 7, 2026.
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 (633 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
kalabint/llm-tooling · 6 stars · license AGPL-3.0 · pushed 2026-10-20 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_ik55zg44z7zgydqr GET https://markdownregistry.com/api/v1/resolve?ref=kalabint/llm-tooling/verify-outcome GET https://markdownregistry.com/api/v1/blob/36fd00c8ba51e9fb74c52e23aa6eb2c13a71ec6f8bbad689ad537472aa184675
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.