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.

Quality

87%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

85%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured, actionable CLI workflow skill with clear sequencing, a verification checkpoint, and clean section organization. Its only drag is mild redundancy between the Steps and Guardrails sections.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient and free of generic concept explanation, but the 'context/rules are constraints not content' note and the 'create ONE artifact' rule are each restated across Steps and Guardrails, so it could be tightened.	2 / 3
Actionability	It provides concrete, copy-pasteable CLI commands (openspec list/status/instructions with --json) and enumerates the exact JSON fields to parse, meeting the 'fully executable, specific examples' anchor.	3 / 3
Workflow Clarity	Steps are explicitly sequenced with status-based branching and a Guardrails checklist that includes an explicit verification checkpoint ('Verify the artifact file exists after writing before marking progress').	3 / 3
Progressive Disclosure	No bundle files exist, so content is self-contained; it is organized into clearly headed sections (Input, Steps, Output, Artifact Creation Guidelines, Guardrails) with easy navigation and no nested references.	3 / 3
	Total	11 / 12 Passed

Description

90%

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, third-person description with an explicit 'Use when' trigger and a clear niche. The only weak spot is specificity, which describes a single focused action rather than enumerating multiple concrete capabilities.

Dimension	Reasoning	Score
Specificity	It names the domain ('OpenSpec change') and a concrete action ('creating the next artifact'), but does not list multiple distinct concrete actions, matching the 'names domain and some actions' anchor rather than the 'lists multiple specific concrete actions' anchor.	2 / 3
Completeness	It explicitly answers both 'what' ('Continue working on an OpenSpec change by creating the next artifact') and 'when' via an explicit 'Use when...' clause, satisfying the top anchor.	3 / 3
Trigger Term Quality	It offers several natural phrasings a user would say ('progress their change', 'create the next artifact', 'continue their workflow'), giving good coverage of natural trigger terms.	3 / 3
Distinctiveness Conflict Risk	The OpenSpec/change/artifact niche with CLI-specific triggers is clearly distinct and unlikely to fire for unrelated skills.	3 / 3
	Total	11 / 12 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: Draculabo/AntigravityManager
Path: .agent/skills/openspec-continue-change/SKILL.md
Commit: de8d68d

Reviewed: about 11 hours 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.