Explore Spec
Author’s activation text, quoted as published
Interactive thinking partner that helps the user shape a spec through conversation. Maintains a structured live draft via fenced spec-draft JSON blocks. The desktop app commits the ticket — never call ticket-creation commands yourself. // ... 175 lines omitted { // ... 174 lines omitted } // ... 173 lines omitted { // ... 172 more lines (total: 178) You are a senior product engineer helping the user shape a single spec through conversation. The user has opened the Explore Spec experience inside specrails-desktop. You are their thinking partner — same stance as /opsx:explore, but the artefact you produce is a single backlog ticket (committed by the desktop app), not OpenSpec change files. …
Works with: Claude Code (native) · Cursor, Codex CLI (manual)
native: this artifact type is that client's own format
Category: Dev Tools & CI — see all ranked ›
Install (Claude Code):
cp -r explore-spec ~/.claude/skills/- Adoption: 1 repos
- Upkeep: 96.0
- Freshness: 91.0
- Evidence coverage: 84% of the inputs this score can use — the rest are unknown, and the score is discounted for it
- Health: active
- Contributors: 5
- License: MIT
Security audit
Not scanned yet. We audit npm-published capabilities for known advisories, install-time scripts and permission surface; this one has no npm package we can resolve, or has not reached the queue.
Its own instructions
Its SKILL.md says when not to, shows worked examples and states a limitation.
Read from the capability’s own SKILL.md. This is not a grade and does not compare to the instruction-depth verdict on an MCP server — a skill has no tools to document, so that rubric does not apply to it.
You searched for one. Check the rest of your stack:
npx tashan-cli doctorReads the config already on your machine and names what is dead, deprecated or running code at install time. No account, nothing uploaded.
Pro adds the history to tashan doctor, so a run over your own config says which of yours gained an advisory, started running an install script, or lost its last maintainer — and what to move to.
- Every score since we started measuring, for any capability
- The named replacement when something you run is dying — not just that it is
tashan doctorover the config you already have, on your machine
Start a 7-day trial › Everything measured on this page stays free.
source ↗ · skill:fjpulidop/explore-spec
Everything on this page is public evidence and free. What it cannot know is whether you run this — check your whole config, free, in the browser. tashan Pro adds the series behind each row and names a replacement for anything dying.
Already running this? Check your whole config — free, in your browser, nothing installed. Or npx tashan-cli doctor locally, which sends nothing at all.
Measured 2026-08-22 · scorer s5 · how · something wrong here?