CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

openspec-new-change

Start a new OpenSpec change using the experimental artifact workflow. Use when the user wants to create a new feature, fix, or modification with a structured step-by-step approach. Also use when the user says "openspec new change" or "opsx new".

Quality

81%

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

75%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.

A well-structured, highly actionable CLI workflow skill with copy-paste-ready commands, explicit validation before writes, and clear stopping points. The main cost is token weight in the long store-selection and project-check prose, which could be compressed or moved to a reference file.

Suggestions

Tighten the store-selection paragraph: instead of enumerating all eleven commands that take --store and re-explaining the shorthand convention, state the rule once ('append --store <id> to any command that reads or writes specs/changes') and list the exceptions only if needed.

Compress the project-check edge cases (the 'Declared in' / 'Invalid store declaration in' branch) into a short bullet or move them to a reference file, keeping only the core instruction to run 'openspec list --json' and read 'root' inline.

Add a brief fallback in step 5 for when no artifact has status 'ready' in the status output, so the sequence is fully closed under errors.

DimensionReasoningScore

Conciseness

The body is operational rather than padded with concepts Claude already knows, but the store-selection paragraph enumerates all eleven flag-taking commands and re-explains the shorthand convention, and the project-check section spends multiple paragraphs on error-message edge cases. Mostly efficient but these sections could be tightened.

3 / 5

Actionability

Provides copy-paste-ready commands ('openspec new change "<name>"', 'openspec status --change "<name>" --json'), a verbatim question to ask the user, and explicit JSON fields to read (planningHome, changeRoot, nextSteps). For an instruction-only skill, the guidance is fully executable and covers the common cases.

5 / 5

Workflow Clarity

A clear 1-6 sequence with an explicit STOP checkpoint, a pre-write validation gate ('openspec list --json', read root) with error-recovery branches for non-zero exits, and a guardrails section. Not a 5 because step 5's instruction to find the first artifact with status 'ready' has no fallback if none is ready.

4 / 5

Progressive Disclosure

Well-organized labeled sections (Store selection, Project check, Input, Steps, Output, Guardrails) with no nested references and appropriately inline steps. At ~75 lines, the dense store-selection and project-check prose blocks arguably belong in a reference file, which keeps it below the top anchor.

4 / 5

Total

16

/

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.

A strong description that clearly states what the skill does and provides explicit, natural trigger phrases including exact command invocations. Its main weaknesses are limited enumeration of concrete actions and a broad 'new feature/fix/modification' trigger that slightly raises overlap risk with generic development skills.

DimensionReasoningScore

Specificity

The description names the domain ('Start a new OpenSpec change using the experimental artifact workflow') and only one concrete action, without enumerating what the workflow actually does. It matches the anchor for naming the domain with 1-2 concrete actions rather than listing several specific actions.

3 / 5

Completeness

Explicitly answers both 'what' (start a new OpenSpec change using the experimental artifact workflow) and 'when' (two 'Use when' clauses with concrete trigger phrases including quoted user commands). This matches the top anchor pattern exactly.

5 / 5

Trigger Term Quality

Includes natural phrases ('create a new feature, fix, or modification') plus exact invocation strings ('openspec new change', 'opsx new'), giving good coverage. Common synonyms like 'spec change' or 'openspec change' are missing, so it does not reach comprehensive coverage.

4 / 5

Distinctiveness Conflict Risk

'OpenSpec change' is a clear niche with distinct CLI-name triggers, but 'wants to create a new feature, fix, or modification' is broad enough to overlap with generic feature-request skills. Mostly distinct with minor overlap risk rather than minimal conflict risk.

4 / 5

Total

16

/

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-new-change/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.