CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

63

Quality

74%

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 ./.agents/skills/openspec-continue-change/SKILL.md
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.

The body is a well-structured, actionable workflow with concrete CLI commands, status branching, and guardrails. Minor room to tighten repeated reminders and to offload schema-specific artifact patterns into a reference file.

Suggestions

Deduplicate the context/rules constraint guidance (stated in step 3 and again in Guardrails) to tighten conciseness.

Consider moving the spec-driven artifact-pattern details into a referenced reference file to improve progressive disclosure.

Add an explicit validate-then-fix retry loop for artifact content to strengthen workflow clarity's feedback checkpoint.

DimensionReasoningScore

Conciseness

Largely efficient with concrete CLI commands and no concept over-explanation, but has minor repetition (the context/rules constraint is restated in both step 3 and Guardrails).

4 / 5

Actionability

Provides concrete executable commands with field-by-field parsing guidance and explicit output paths, though artifact content relies on runtime-resolved template/instruction fields rather than fully copy-paste examples.

4 / 5

Workflow Clarity

Clear numbered sequence with status branching, explicit STOP points, and a 'verify the artifact file exists after writing' checkpoint; lacks an explicit validate-fix-retry loop on artifact content.

4 / 5

Progressive Disclosure

Well-organized with clear section headers and no nested references, but all content (including inlined spec-driven artifact patterns) lives in SKILL.md with no external files to offload detail.

4 / 5

Total

16

/

20

Passed

Description

73%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 well-scoped to a clear niche with an explicit 'Use when' clause covering both what and when. It is slightly generic in naming the concrete actions and could add more natural synonyms/artifact names.

Suggestions

List specific artifact types (e.g., proposal, specs, design, tasks) in the description to raise specificity and trigger-term coverage.

Add natural synonyms users might say (e.g., 'spec', 'proposal', 'tasks') alongside 'change' and 'artifact'.

DimensionReasoningScore

Specificity

Names the OpenSpec-change domain and a concrete action ("creating the next artifact") but does not enumerate specific artifact types, matching the anchor for 1-2 concrete actions without comprehensive coverage.

3 / 5

Completeness

Explicitly answers both what ("Continue working on an OpenSpec change by creating the next artifact") and when ("Use when the user wants to progress their change..."), with the 'when' slightly generic rather than fully concrete.

4 / 5

Trigger Term Quality

Includes natural trigger phrases users would say ("progress their change", "create the next artifact", "continue their workflow") with good coverage, though a few synonyms (e.g., spec, proposal, tasks) are missing.

4 / 5

Distinctiveness Conflict Risk

Scoped to a clear named niche ("OpenSpec change") with distinct triggers and minimal conflict risk against other skills.

5 / 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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
fengshao1227/ccg-workflow
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.