sb-contract-review SKILL.md skillA
sb-contract-review from huruikagi/specbind is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add huruikagi/specbind/sb-contract-review@git:20261021.06bd198Pins git:20261021.06bd198 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- huruikagi/specbind
- Path
tools/specbind/assets/skills/sb-contract-review/SKILL.md- Versions recorded
- 9
- Latest version
- git:20261021.06bd198, committed Oct 21, 2026
- First version recorded
- Sep 1, 2026
- Size
- 17,703 bytes
- Repository stars
- 2
- License
- MIT
Judge whether the milestone's changes leave every persistent seam in the project coherent, and accept the one contract review that Tasks authoring waits on.
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
# Review the contract graph ## Apply project language style Before authoring any artifact or user-facing prose, read: ```sh specbind rule read language-style --for consume ``` Apply returned policy only to natural-language prose. `NO_CHANGE RULE_ABSENT` means no additional project preference; any `ERROR` line stops the workflow. One review per milestone, between design approval and any new or revised Tasks gate, or between reverse Design approval and adoption finalization. The question is **not** "do the Specs in this milestone agree with each other." It is: > Does this milestone leave **every** persistent seam in the project coherent — > including seams owned by Specs it never touched? A Spec outside the milestone is the consumer most likely to break, precisely because nobody is looking at it. You accept one artifact. You author no Spec artifact and change no Spec's state. ## 1. Check that the review can run ```sh specbind milestone review status specbind milestone status specbind milestone scope ``` Stop and report, rather than fixing, in these cases: - **`Status: not_applicable`** — a Direct-only milestone without shared agreement changes has no …
Read the whole file at its exact version.
How to install
mdr add huruikagi/specbind/sb-contract-review@sha256:bfaf848b47dd8c23The line at the top of this page pins the label git:20261021.06bd198, 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_ngvmrhqbuaf4o3x6)
4 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 9 versions of this file, between Sep 1, 2026 and Oct 21, 2026, about one every 6 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261021.06bd198 latest | 2026-10-21 | 06bd198 | 17,703 B | A | view · diff |
| git:20260910.144adf8 | 2026-09-10 | 144adf8 | 16,870 B | A | view · diff |
| git:20260908.c08fc8f | 2026-09-08 | c08fc8f | 15,859 B | A | view · diff |
| git:20260908.ad88786 | 2026-09-08 | ad88786 | 14,451 B | A | view · diff |
| git:20260908.a81ba78 | 2026-09-08 | a81ba78 | 13,901 B | A | view · diff |
| git:20260907.878b149 | 2026-09-07 | 878b149 | 13,644 B | A | view · diff |
| git:20260903.711d787 | 2026-09-03 | 711d787 | 13,006 B | A | view · diff |
| git:20260903.7954083 | 2026-09-03 | 7954083 | 12,825 B | A | view · diff |
| git:20260901.b1498fa | 2026-09-01 | b1498fa | 13,066 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 (17703 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
huruikagi/specbind · 2 stars · license MIT · pushed 2026-11-04 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_ngvmrhqbuaf4o3x6 GET https://markdownregistry.com/api/v1/resolve?ref=huruikagi/specbind/sb-contract-review GET https://markdownregistry.com/api/v1/blob/bfaf848b47dd8c23522478c0130ce5082985882466702923f3475a98986d30ef
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.