sb-status SKILL.md skillA
sb-status 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-status@git:20260912.14156afPins git:20260912.14156af 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-status/SKILL.md- Versions recorded
- 7
- Latest version
- git:20260912.14156af, committed Sep 12, 2026
- First version recorded
- Sep 1, 2026
- Size
- 6,203 bytes
- Repository stars
- 2
- License
- MIT
Report where a Spec or active milestone is in its lifecycle and what can happen next. Read-only; do not use to judge whether completed implementation is actually done.
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
# Report current SpecBind state ## 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. Answer "where is this work now, and what is the next thing that can happen?" using the CLI's derived read models. Change nothing. For "is this completed implementation actually done?", use `sb-verify-completion`. Use `sb-validate-implementation` only when every Task is complete and the user explicitly authorizes recording completion on `GO`. If that authority is unclear, keep the claim check consequence-free. ## Choose the scope - A named Spec, when the user asks about one, or when only one Spec is under discussion. - The active milestone otherwise, including when the user asks a general question such as what to do next. When the request is ambiguous, report the milestone first: it names the participating Specs, so the user can narrow from there. ## Follow the selected procedure …
Read the whole file at its exact version.
How to install
mdr add huruikagi/specbind/sb-status@sha256:a79f1998eff3a284The line at the top of this page pins the label git:20260912.14156af, 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_pgetvco3yg5ky5v5)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 7 versions of this file, between Sep 1, 2026 and Sep 12, 2026, about one every 2 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260912.14156af latest | 2026-09-12 | 14156af | 6,203 B | A | view · diff |
| git:20260909.f384b05 | 2026-09-09 | f384b05 | 6,160 B | A | view · diff |
| git:20260909.4c5c2b4 | 2026-09-09 | 4c5c2b4 | 6,055 B | A | view · diff |
| git:20260909.30c65db | 2026-09-09 | 30c65db | 5,748 B | A | view · diff |
| git:20260908.798e9d0 | 2026-09-08 | 798e9d0 | 5,280 B | A | view · diff |
| git:20260907.23a8548 | 2026-09-07 | 23a8548 | 3,704 B | A | view · diff |
| git:20260901.b1498fa | 2026-09-01 | b1498fa | 4,034 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 (6203 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_pgetvco3yg5ky5v5 GET https://markdownregistry.com/api/v1/resolve?ref=huruikagi/specbind/sb-status GET https://markdownregistry.com/api/v1/blob/a79f1998eff3a284c9f44d01e56d5dab33e69c33c63f853c305e0012c5c0937b
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.