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

69%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/openspec-explore/SKILL.md

Quality

Content

60%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 well-structured and actionable with concrete OpenSpec commands and a sequenced, checkpointed workflow. Its main weakness is significant repetition of guardrails and the --store rule, which inflates token cost without adding clarity.

Suggestions

Consolidate the write-confirmation guardrail into a single authoritative statement; remove the near-verbatim repetitions in the opening note, Planning a Change, and Guardrails sections.

State the '--store <id>' stickiness rule once and reference it from each command example instead of repeating the full append-'--store' instruction inside step 2 and every sub-step.

Break the monolithic step-2 paragraph into a short numbered sub-list so the dependency/skip logic is scannable instead of buried in prose.

Dimension	Reasoning	Score
Conciseness	The body is noticeably verbose: the write-confirmation guardrail is restated near-verbatim in the opening note, the Planning section, and the Guardrails section, and the '--store' stickiness rule is repeated roughly eight times, including inside a single dense paragraph for step 2.	2 / 5
Actionability	Provides concrete executable commands with specific flags (e.g. 'openspec list --json', 'openspec show "<spec-id>" --type spec --json --no-scenarios', 'openspec new change "<name>"') and a sequenced capture workflow; minor gaps keep it from a 5.	4 / 5
Workflow Clarity	The capture workflow is a clear numbered sequence with a feedback loop ('After creating each artifact, re-run openspec status') and a verification checkpoint ('Verify that the selected concrete output exists'), but the steps are embedded in oversized paragraphs that obscure the sequence.	4 / 5
Progressive Disclosure	No bundle files exist and the content is organized into clearly headed sections with no nested references; some long inline sections (detailed capture steps, entry-point examples) could arguably be split out, preventing a 5.	4 / 5
	Total	14 / 20 Passed

Description

78%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 strong: it states a clear purpose and an explicit 'Use when' trigger with natural phrasing. Its only weakness is that the named actions are conceptual rather than concrete, slightly limiting specificity.

Dimension	Reasoning	Score
Specificity	Names the domain and three actions ('exploring ideas, investigating problems, and clarifying requirements'), but these are conceptual stances rather than concrete mechanical actions, matching the anchor for naming a domain with 1-2 actions that are not comprehensive.	3 / 5
Completeness	Explicitly 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 a change') with a concrete trigger phrase.	5 / 5
Trigger Term Quality	Natural user-facing phrases like 'think through something before or during a change' and 'exploring ideas' give good keyword coverage; not a 5 because the abstract domain lacks synonym/extension breadth.	4 / 5
Distinctiveness Conflict Risk	'Explore mode' is a clear niche with distinct triggers, but 'think through something' carries minor overlap risk with generic brainstorming skills, so it is not a 5.	4 / 5
	Total	16 / 20 Passed

Validation

100%

Warnings & errors only

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
Commit: 9d4e597

Reviewed: 4 days ago

Table of Contents

Discovery Implementation Validation

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.