spec-probe SKILL.md skillA
spec-probe from ucsandman/claude-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add ucsandman/claude-skills/spec-probe@git:20260915.fbf6a77Pins git:20260915.fbf6a77 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- ucsandman/claude-skills
- Path
spec-probe/SKILL.md- Versions recorded
- 1
- Latest version
- git:20260915.fbf6a77, committed Sep 15, 2026
- Size
- 7,415 bytes
- Repository stars
- 5
- License
- MIT
Run before implementing anything non-trivial: surface omitted edge cases and must-NOT constraints into a verification-tiered TASK_CONTRACT.md, so the verifier has something to check against. Use when starting a feature, a bugfix with unclear intended behavior, or any task where a reviewer would have to guess what correct means. Also use when asked to spec-probe, write a task contract, or check what the spec left out.
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
# Spec probe A verifier catches only what the spec named. When an obligation was never stated and no convention determines it, the comparison is vacuous — any behavior is "consistent with the spec," and the verifier passes the defect at ~93% confidence. Measured: 100% confident false pass with the edge omitted, 98% catch once the same edge is written into the spec (n=210, Wilson 95% CI). Re-running a bigger model never closes that gap; a ~30x cost increase buys no additional recovery. So do not strengthen the reader. Widen the artifact, before code exists. Output is one file: `TASK_CONTRACT.md` at the repo root (or beside the feature's plan). Schema and worked example: `references/contract-schema.md`. Read it before writing one. ## Steps 1. **Enumerate requirements.** One line each, from the request plus whatever spec exists. Terse prose is the failure mode here — a requirement with no discernible shape yields no edges. Expand a one-liner into its actual obligation before classifying it. 2. **Shape-classify each requirement** as one or more of: `numeric-range`, `collection`, `text`, `stateful`, `io`. Do this yourself as a reading task. Do NOT delegate it to a …
Read the whole file at its exact version.
How to install
mdr add ucsandman/claude-skills/spec-probe@sha256:ae870d97de1c5d2fThe line at the top of this page pins the label git:20260915.fbf6a77, 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_v6gzvwdrgwrcs4mh)
4 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Sep 15, 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 (7415 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
ucsandman/claude-skills · 5 stars · license MIT · pushed 2026-09-19 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_v6gzvwdrgwrcs4mh GET https://markdownregistry.com/api/v1/resolve?ref=ucsandman/claude-skills/spec-probe GET https://markdownregistry.com/api/v1/blob/ae870d97de1c5d2fd8a48d76a252c6b92e58773412ee4c66466409455d9bb973
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.