Install
$ agentstack add skill-lbk-open-super-spec-ss-show-spec ✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
About
Show OpenSpec Capability
Discover and display the authoritative spec for a capability. This is the entry point for "see what exists, then read it" — don't list or grep openspec/ blindly before calling this skill.
Inputs
Optional: a capability name (matching a directory under openspec/specs/) or a keyword to search for. Omit both to get an index of all capabilities.
Process
- No input given — enumerate every directory under
openspec/specs/. For each, read
the ## Purpose section (or the first descriptive line) of its spec.md and print a one-line index entry: capability-name — . If openspec/specs/ is empty or missing, report that this repository has no OpenSpec baseline yet — suggest running the ss-write-spec or ss-reverse-spec skill. Stop here.
- Input matches a capability directory exactly (
openspec/specs//) — read
and display that spec.md in full.
- Input is a keyword — search every
openspec/specs/*/spec.md(and, where useful,
active openspec/changes/*/specs/*/spec.md, excluding archive/) for the text. Show each match with its capability name and the matching line or excerpt. If more than one capability matches, list them and ask the user which one to display in full.
- After displaying a capability, list the 5 most recent archive entries that touched it —
e.g., by finding files matching openspec/changes/archive/*/specs//spec.md and taking the last 5 in sorted order. For each, show the archive directory name, the first proposal heading if available, and a count of delta sections (ADDED / MODIFIED / REMOVED / RENAMED).
Output
Keep the surrounding commentary concise, but always include the full current spec text. Do not edit any files.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: lbk-open
- Source: lbk-open/super-spec
- License: Apache-2.0
- Homepage: https://www.npmjs.com/package/@lbk-open/super-spec
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet — be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.