CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

openspec-explore

Enter OpenSpec explore mode - a thinking partner for exploring ideas, investigating problems, and clarifying requirements in a project that uses OpenSpec. Use when the user wants to think through something before or during an OpenSpec change. Also use when the user says "openspec explore" or "opsx explore".

Quality

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

77%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is highly actionable and its workflows are clearly sequenced with explicit validation checkpoints and error-recovery paths. However, it is a monolithic ~345-line single file with significant repetition (especially the --store flag instructions and confirmation guardrails) that would benefit from tighter prose and splitting detailed procedure into reference files.

Suggestions

State the sticky --store <id> rule once in the Store selection section and refer back to it ('with --store when selected') in later steps, removing the ~8 verbatim repetitions.

Extract the detailed 4-step capture workflow and the artifact-creation rules (path resolution, dependency handling, conditional skips) into a reference file such as references/capture-workflow.md, keeping SKILL.md as an overview with a clearly signaled link.

Consolidate the write-confirmation guardrails into a single section - they are currently stated in the opening IMPORTANT paragraph, again under 'Don't auto-capture', and again in the capture transition.

DimensionReasoningScore

Conciseness

The body is mostly task-relevant but noticeably repetitive: the instruction to append the confirmed --store flag is stated in the Store selection section and then repeated in nearly every numbered step (~8 times), and the write-confirmation guardrails are stated three times (intro paragraph, 'Don't auto-capture', and the capture transition). Not 2 because there is no padding of concepts Claude already knows.

3 / 5

Actionability

Guidance is copy-paste ready and covers the common cases: exact commands with flags (`openspec list --json`, `openspec show "<spec-id>" --type spec --json --no-scenarios`, `openspec new change "<name>"`), named JSON fields to read (`root`, `changeRoot`, `artifactPaths`, `resolvedOutputPath`), example dialogues for four entry points, and a table mapping insight types to capture destinations.

5 / 5

Workflow Clarity

The capture workflow is explicitly sequenced with feedback loops and validation checkpoints: 'After creating each artifact, re-run openspec status', verifying chosen output paths stay inside changeRoot after resolving symlinks, verifying the concrete output exists, and explicit error-recovery handling for blocked prerequisites and conditional skips. The stance sections intentionally and clearly state there is no fixed sequence.

5 / 5

Progressive Disclosure

No bundle files exist and all ~345 lines live inline in SKILL.md. Section headers and horizontal rules make it navigable, but the dense capture-workflow steps and the store-scoping rules are exactly the kind of detailed material that belongs in one-level-deep reference files, leaving the main file an overview. This matches the 'content that should be separate is inline' anchor rather than the well-split anchor 4.

3 / 5

Total

16

/

20

Passed

Description

87%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is well-constructed: it states the skill's purpose in third person, gives an explicit 'Use when' clause with concrete trigger phrases including command aliases, and is clearly distinguishable from sibling OpenSpec skills. Its only weakness is that the listed actions are somewhat abstract for a thinking-mode skill.

DimensionReasoningScore

Specificity

Lists several domain-specific actions ("exploring ideas, investigating problems, and clarifying requirements") with minor gaps in coverage. Not 3 since more than 1-2 actions are named; not 5 because the actions are conceptual for a thinking-mode skill rather than fully concrete operations.

4 / 5

Completeness

Clearly answers both what ("a thinking partner for exploring ideas, investigating problems, and clarifying requirements") and when ("Use when the user wants to think through something before or during an OpenSpec change. Also use when the user says 'openspec explore' or 'opsx explore'") with concrete trigger phrases.

5 / 5

Trigger Term Quality

Good natural keyword coverage including command aliases ("openspec explore", "opsx explore") and the phrase "think through something". A few natural synonyms a user might say (brainstorm, investigate) are missing, keeping it below the comprehensive anchor 5.

4 / 5

Distinctiveness Conflict Risk

Scopes itself to "a project that uses OpenSpec" and to a specific explore mode with distinct command-style triggers, giving it a clear niche with minimal conflict risk against other OpenSpec workflows like propose or apply.

5 / 5

Total

18

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

Fission-AI/OpenSpec

Path

skills/openspec-explore/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.