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

83%

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 highly actionable, well-sequenced workflow with strong validation checkpoints and unambiguous commands. Its main weakness is token efficiency: several guardrails are stated two or three times and key sections are written as hard-to-parse run-on sentences that a single tightened pass would fix.

Suggestions

State the "instruction field delegates to a skill or command" rule once (e.g., in the Artifact Creation Guidelines section) and reference it from the two workflow steps instead of repeating the full caveat three times.

Split the store-selection paragraph and the 'finish a partly written artifact' section into short imperative bullets; each is currently a single 80+ word sentence that buries the path-safety check and ONE-artifact rule.

Merge the duplicate symlink/changeRoot path-verification instructions (step 3's partly-written-artifact branch and the create-artifact branch) into one shared 'path safety' checklist item, and fold the repeated 're-read dependencies from disk' guidance into the Guardrails section only.

DimensionReasoningScore

Conciseness

The body is densely operational with no concept explanations Claude already knows, but it is noticeably repetitive and could be tightened: the "instruction field delegates to a skill or command" rule appears three times, the symlink/changeRoot path check twice, and "re-read dependencies from disk" twice, while the store-selection paragraph and the partly-written-artifact section are single run-on sentences of 80+ words. It is above anchor 2 because the verbosity is redundant guardrails rather than padded explanation.

3 / 5

Actionability

Commands are copy-paste ready (`openspec status --change "<name>" --json`, `openspec instructions <artifact-id> --change "<name>" --json`, `openspec list --json`), with field-by-field JSON parsing guidance and explicit branch handling covering the common cases, matching the 'fully executable' anchor for an instruction-only skill.

5 / 5

Workflow Clarity

The four-step sequence is clear with status-based branching, explicit validation checkpoints (verify the file exists after writing, check `root` before any write, path-inside-changeRoot checks), and error-recovery loops (stop and tell the user, ask when uncertain). It falls short of anchor 5 because the partly-written-artifact branch's convoluted nested prose makes its checkpoints hard to follow in order.

4 / 5

Progressive Disclosure

With no bundle files, all content is appropriately inline for a self-contained CLI workflow, organized under clear section headers (Store selection, Project check, Input, Steps, Output, Guardrails). It is below anchor 5 because at ~125 lines the long store-selection and error-branch prose could be split or trimmed, leaving minor organization gaps rather than a clean overview.

4 / 5

Total

16

/

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 explicitly states what the skill does and when to use it, with distinctive command-alias triggers that make collision with other skills unlikely. The only weakness is that the capability description stays at one level of abstraction rather than listing the concrete artifact types it can create.

DimensionReasoningScore

Specificity

"Continue working on an OpenSpec change by creating the next artifact" names the domain and one concrete action, but does not enumerate what progressing a change involves (e.g., proposal, specs, tasks), matching the '1-2 concrete actions, not comprehensive' anchor rather than the 'several specific actions' anchor.

3 / 5

Completeness

It clearly answers both what ("creating the next artifact" of an OpenSpec change) and when ("Use when the user wants to progress their change... or says 'openspec continue' or 'opsx continue'") with concrete trigger phrases, matching the top anchor.

5 / 5

Trigger Term Quality

Triggers include natural phrases ("progress their change", "continue their workflow") plus literal command invocations ("openspec continue", "opsx continue"), giving good coverage; a few natural variations (e.g., mentioning "OpenSpec" alone or "next step") are missing, so it sits at the 'good coverage, a few terms missing' anchor rather than comprehensive.

4 / 5

Distinctiveness Conflict Risk

"OpenSpec change" plus distinct command-style triggers ("openspec continue", "opsx continue") carve out a clear niche with minimal conflict risk against generic workflow skills; it is not below this anchor since the trigger phrases are unique to this workflow.

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

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.