clarify SKILL.md skillA
clarify from ramboz/jig is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add ramboz/jig/clarify@git:20261006.e3fb128Pins git:20261006.e3fb128 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- ramboz/jig
- Path
hosts/codex/plugins/jig/skills/clarify/SKILL.md- Versions recorded
- 4
- Latest version
- git:20261006.e3fb128, committed Oct 6, 2026
- First version recorded
- Jun 22, 2026
- Size
- 18,831 bytes
- Repository stars
- 7
- License
- MIT
Lightweight spec clarification scan for jig projects — a six-category ambiguity audit that asks up to five prioritized questions and appends them to the spec's `## Clarifications` section. Auto-triggers when you say clarify this spec, audit this spec for ambiguities, is this spec ready for review, find unknowns in this scope, surface what's still unclear or unspecified, scan for unanswered questions, or what's missing from this spec. Do not use for: spec-compliance review of a finished slice…
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 023 introduces this skill as jig's **pre-spec ambiguity scan**. It > is the sixth non-stub active jig skill that ships without a `.py` > helper — clarify is fundamentally a judgment skill, and the > determinism it needs (locate the target doc, find an existing > `## Clarifications` section if any, append new entries) Codex can > run inline via Read + Edit. The skill slots between > `workflow.py new <slug>` (stub reservation) and the > `READY_FOR_REVIEW` transition (spec body ready for first review). > > Per user direction on 2026-05-18, jig's clarify ships as a > **standalone baseline**, not a deferral surface. Power users who > want spec-kit's `/speckit.clarify` install spec-kit and invoke it > explicitly under `/speckit.*`. There is no category-based deferral > hint in this skill's description. ## What this skill does Runs a structured ambiguity scan against a DRAFT-state spec document across **six categories** aligned with jig's slice template (Scope & Boundaries / Acceptance Criteria Testability / Dependencies & Blockers / Non-functional Requirements / Edge Cases & Failure Modes / Terminology Consistency). The skill rates each category Clear / Partial / Missing, …
Read the whole file at its exact version.
How to install
mdr add ramboz/jig/clarify@sha256:2e9409828b8d4e72The line at the top of this page pins the label git:20261006.e3fb128, 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_gbfxvzabqvlkoxnf)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 4 versions of this file, between Jun 22, 2026 and Oct 6, 2026, about one every 36 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261006.e3fb128 latest | 2026-10-06 | e3fb128 | 18,831 B | A | view · diff |
| git:20260708.fbee6a7 | 2026-07-08 | fbee6a7 | 17,950 B | A | view · diff |
| git:20260704.5c31da0 | 2026-07-04 | 5c31da0 | 17,903 B | A | view · diff |
| git:20260622.59b4e31 | 2026-06-22 | 59b4e31 | 17,122 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 (18831 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
ramboz/jig · 7 stars · license MIT · pushed 2026-10-27 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_gbfxvzabqvlkoxnf GET https://markdownregistry.com/api/v1/resolve?ref=ramboz/jig/clarify GET https://markdownregistry.com/api/v1/blob/2e9409828b8d4e72091dc8fde65df7a65b01a990ed5ea867243097fdc9f80959
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.