Spec discovery
Skill aiskillstore/marketplace/skills/consiliency/spec-discovery
Security-audited skills for Claude, Codex & Claude Code. One-click install, quality verified.
npx -y skills add aiskillstore/marketplace --skill spec-discoveryAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
What its author says it does
Copied from the file, not written here
Parse specs to extract IDs, titles, and traceability metadata (repo, path, hash).
SKILL.md
2.0 KB, as published. Nobody here has run it
Spec Discovery Skill
Locate specs and external request headers, extract IDs (e.g., REQ-NOTIFY-001), and return traceable metadata for downstream agents.
Variables
| Variable | Default | Description |
|---|---|---|
| ROOT | . | Primary repository root |
| EXTRA_REPOS | [] | Additional repo roots containing specs/ |
| INCLUDE_EXTERNAL_REQUESTS | true | Scan specs/external-requests/ |
| OUTPUT_FORMAT | json | json or toon manifest output |
Workflow (Mandatory)
- Load repositories: ROOT + EXTRA_REPOS
- Walk specs:
specs/,specs/external-requests/, skipspecs/templates/ - Parse headings: match
^#+\s*(REQ-[A-Za-z0-9_-]+)\s*:?\s*(.*)$ - Normalize: path relative to repo root, anchor from ID + title
- Traceability: compute SHA-256 of file content; record
source_repo,path,hash - Emit manifest: sorted by repo → path → ID in JSON/TOON (see Output Schema)
Red Flags (Stop & Verify)
- No IDs detected in a spec file → confirm heading format before skipping
- Duplicate spec IDs across repos → flag in the manifest
notesfield - Missing
specs/directory → report empty result rather than failing
Output Schema
{
"format": "spec-manifest/v1",
"generated_at": "<ISO-8601 UTC>",
"sources": [
{"repository": "<repo-name>", "root": "<abs-path>"}
],
"specs": [
{
"id": "REQ-NOTIFY-001",
"title": "Email Sending Endpoint",
"source_repo": "ai-dev-kit",
"path": "specs/external-requests/notify.md",
"link": "specs/external-requests/notify.md#req-notify-001-email-sending-endpoint",
"hash": "<sha256-of-file>"
}
]
}
Provider Notes
- Use this skill when other commands request
/ai-dev-kit:specs-findor spec traceability. - Prefer JSON for machine workflows; use TOON for compact prompt embedding.
- Preserve ID/title casing; anchors should be lowercase + hyphenated.