CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

openspec-explore

Enter explore mode - a thinking partner for exploring ideas, investigating problems, and clarifying requirements. Use when the user wants to think through something before or during a change.

Quality

73%

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

Fix and improve this skill with Tessl

tessl review fix ./test/fixtures/released-output/v1.10.0-amazonq/skills/openspec-explore/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

63%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 body delivers a clear, concrete stance definition with executable OpenSpec CLI workflows and good validation loops for artifact capture. Its weaknesses are token efficiency — systematic repetition of the --store flag instruction and oversized ASCII examples — and a monolithic structure where the detailed capture procedure and dialogue examples should be split into reference files.

Suggestions

State the --store flag rule once in the store-selection paragraph and refer back to it ("apply the sticky store flag to every command that takes it") instead of repeating the parenthetical six times (conciseness).

Move the dense conditional change-capture procedure into a references/capture-workflow.md and keep a short summary in SKILL.md, so the main file stays a lean overview (progressive_disclosure).

Trim the four ASCII mock-dialogues to one or two compact examples — the pattern (diagram + open question) is clear after the first (conciseness).

DimensionReasoningScore

Conciseness

The core stance guidance is tight, but there is real padding: the parenthetical "(append the confirmed --store \"<id>\" only for a registered standalone store)" is repeated nearly verbatim six times across the store-selection and capture sections, and the four long ASCII mock-dialogues (~100 lines) illustrate points Claude could grasp from one shorter example. Mostly efficient with clear tightening opportunities — fits the 3 anchor, not 4, because the repetition is systematic rather than minor.

3 / 5

Actionability

Concrete, copy-paste-ready commands appear throughout ("openspec list --json", "openspec new change \"<name>\"", "openspec status --change \"<name>\" --json") with specific JSON fields to consume (changeRoot, artifactPaths.existingOutputPaths, resolvedOutputPath) and verify against. Not 5 because the stance/entry-point sections rely on abstract direction where a concrete decision rule would help (e.g., when to offer capture vs. keep exploring).

4 / 5

Workflow Clarity

The change-capture path is well sequenced with explicit checkpoints and feedback loops: scaffold via CLI, re-run "openspec status --json" after each artifact, process in dependency order, verify the concrete output exists, and loop until every artifact is done/skipped. Not 5 because the exploration flow itself deliberately has no checkpoints (acceptable for a stance skill), and the conditional-skip/dependency-override rules in step 4 are dense enough that a checkpoint summary would help.

4 / 5

Progressive Disclosure

The file is well-sectioned with clear headers, but it is a ~300-line monolith with zero external references: the dense conditional change-capture procedure (lines 110-117) and the long entry-point dialogue examples are exactly the kind of detail that belongs in a one-level-deep reference file, keeping SKILL.md a lean overview. This matches the 3 anchor ("content that should be separate is inline") better than 4, which expects most bulk content appropriately split out.

3 / 5

Total

14

/

20

Passed

Description

70%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 clearly answers both what the skill does and when to use it, with an explicit trigger clause and natural phrasing. Its main weakness is specificity — the capabilities are described with abstract thinking-verbs rather than concrete, distinguishable actions, leaving trigger coverage slightly generic.

Suggestions

List concrete capabilities instead of abstract framing, e.g., "Explores problem spaces, maps existing architecture, compares approaches with diagrams, and captures insights as OpenSpec change proposals" (specificity).

Add natural trigger synonyms users would say — "brainstorm", "talk through", "investigate", "clarify requirements before starting a change" (trigger_term_quality).

Make the 'when' clause more concrete, e.g., "Use when the user wants to explore or brainstorm an idea, investigate a problem, or clarify scope before or while an OpenSpec change is in flight" (completeness).

DimensionReasoningScore

Specificity

Phrases like "exploring ideas, investigating problems, and clarifying requirements" name the domain and a few actions, but they stay abstract — no concrete artifacts or operations (e.g., mapping architecture, comparing options, capturing proposals) are listed. It sits at the 'names domain and 1-2 concrete actions' anchor, not 4, because the actions are generic thinking verbs rather than specific capabilities.

3 / 5

Completeness

Both parts are present: the "what" ("a thinking partner for exploring ideas, investigating problems, and clarifying requirements") and an explicit "Use when..." clause. Not 5 because the trigger ("think through something before or during a change") is somewhat abstract compared to concrete trigger phrases like "mentions PDFs, forms".

4 / 5

Trigger Term Quality

"Use when the user wants to think through something before or during a change" plus "exploring", "investigating", "clarifying requirements" give good natural-phrase coverage a user would plausibly say. Not 5 because common synonyms like "brainstorm", "discuss", or "spike" are missing.

4 / 5

Distinctiveness Conflict Risk

The OpenSpec change-workflow framing ("before or during a change") carves out a mostly distinct niche with clear triggers. Not 5 because "think through something" could also fire for generic brainstorming or planning skills unrelated to OpenSpec.

4 / 5

Total

15

/

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

test/fixtures/released-output/v1.10.0-amazonq/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.