CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

openspec-continue-change

Continue working on an OpenSpec change by creating the next artifact. Use when the user wants to progress their change, create the next artifact, or continue their workflow. Also use when the user says "openspec continue" or "opsx continue".

Quality

88%

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

88%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-engineered workflow skill: fully executable commands, explicit validation and error-recovery branches, and disciplined guardrails (one artifact per invocation, re-read dependencies from disk). The body is efficient and specific throughout, with only minor organizational and conciseness refinements available.

DimensionReasoningScore

Conciseness

The body is dense with operational specifics and avoids explaining concepts Claude already knows, but has minor trim opportunities: "stop and tell the user" is repeated across sections, the changeRoot symlink check is explained twice (in the partly-written-artifact section and again in the ready-artifact branch), and several long parentheticals could be tightened. Anchor 4 (efficient with minor over-explanation) fits better than 3, since nearly every sentence carries non-obvious CLI-specific information.

4 / 5

Actionability

Commands are copy-paste ready (`openspec status --change "<name>" --json`, `openspec instructions <artifact-id> --change "<name>" --json`, `openspec list --json`, `openspec store list --json`), the JSON fields to parse are enumerated by name, and each status branch ends in a concrete action. This matches anchor 5 for an instruction-only skill; per the scoring notes, absence of code is not penalized when guidance is this actionable.

5 / 5

Workflow Clarity

The four-step sequence is explicit with validation checkpoints throughout: verify expected files against `artifactPaths`, verify output paths remain inside `changeRoot` after resolving symlinks, verify the artifact file exists after writing, and re-run `openspec status` to show progress. Error-recovery feedback loops are present for the failure modes (root:null branching, unresolvable store declarations, interrupted glob artifacts, ambiguous change selection). This matches anchor 5; anchor 4 would require missing checkpoints, and none are missing for this non-destructive, single-artifact workflow.

5 / 5

Progressive Disclosure

As a single-file skill with no bundle files, all runtime-needed content is appropriately inline and organized under clear sections (Store selection, Project check, Input, Steps, Output, Artifact Creation Guidelines, Guardrails). It scores 4 rather than 5 because at ~125 lines it exceeds the under-50-line simple-skill exception, and the `---`-separated decision branches nested inside step 3, along with multi-paragraph prose in Store selection and Project check, create minor navigation friction that clearer headers or a trimmed structure would resolve.

4 / 5

Total

18

/

20

Passed

Description

82%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 and explicitly states both capability and trigger conditions, including exact command phrases for reliable activation. Its only weakness is that it undersells the skill's concrete capabilities, summarizing everything into a single action.

Suggestions

Mention one or two more concrete capabilities (e.g., selecting from active changes, checking artifact status) to raise specificity without adding length.

Add a common natural variation such as "resume" or "next step" to the trigger phrases to broaden keyword coverage.

DimensionReasoningScore

Specificity

The description names the domain ("OpenSpec change") and one concrete action ("creating the next artifact"), but does not list the several specific operations the skill actually performs (status checks, change selection, prompting for ambiguous input). It matches anchor 3 (domain plus 1-2 concrete actions) rather than anchor 4, which requires several listed actions; it is well above anchor 2 since the action given is concrete, not generic.

3 / 5

Completeness

It explicitly answers both questions: what ("Continue working on an OpenSpec change by creating the next artifact") and when ("Use when the user wants to progress their change... Also use when the user says 'openspec continue' or 'opsx continue'") with concrete trigger phrases, matching the anchor-5 example pattern exactly.

5 / 5

Trigger Term Quality

It includes natural phrases users would say — "progress their change", "create the next artifact", "continue their workflow" — plus exact command triggers "openspec continue" and "opsx continue". This is good keyword coverage but not the comprehensive synonym-and-extension coverage of anchor 5 (e.g., no "resume" or "keep going" variations), and clearly above anchor 3's partial coverage.

4 / 5

Distinctiveness Conflict Risk

It occupies a clear niche (continuing OpenSpec changes) with distinct, unambiguous triggers ("openspec continue", "opsx continue") that no other skill would claim, matching anchor 5. It is above anchor 4 because the command-name triggers eliminate even minor overlap with related OpenSpec skills.

5 / 5

Total

17

/

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.16.0-claude-skills/openspec-continue-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.