How do I install the Ss Show Spec skill?

Run npx skillmds@latest add lbk-open/ss-show-spec in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Ss Show Spec safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Ss Show Spec?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Ss Show Spec free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Ss Show Spec?

lbk-open (@lbk-open) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Ss Show Spec by lbk-open — Agent Skill

Name: Ss Show Spec
Author: lbk-open

Ss Show Spec

Displays the current source-of-truth OpenSpec for a capability, or lists all capabilities when called without one, and summarizes recent archived changes that touched it. Use this as the entry point before reading or editing anything under openspec/ — do not grep or browse the directory manually first.

lbk-open 8e541dc 2.1 KB Updated Sep 17, 2026

File contents

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 — <purpose>. 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/<capability>/) — 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/<capability>/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.

---name: ss-show-specdescription: Displays the current source-of-truth OpenSpec for a capability, or lists all capabilities when called without one, and summarizes recent archived changes that touched it. Use this as the entry point before reading or editing anything under openspec/ — do not grep or browse the directory manually first.---# Show OpenSpec CapabilityDiscover 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 callingthis skill.## InputsOptional: a capability name (matching a directory under `openspec/specs/`) or a keyword tosearch for. Omit both to get an index of all capabilities.## Process1. **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 — <purpose>`. 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.2. **Input matches a capability directory exactly** (`openspec/specs/<capability>/`) — read and display that `spec.md` in full.3. **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.4. After displaying a capability, list the 5 most recent archive entries that touched it — e.g., by finding files matching `openspec/changes/archive/*/specs/<capability>/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).## OutputKeep the surrounding commentary concise, but always include the full current spec text.Do not edit any files.

Frequently asked questions