openspec-apply-change

Implement tasks from an OpenSpec change. Use when the user wants to start implementing, continue implementation, or work through tasks.

Quality

87%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

85%

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-sequenced, actionable workflow with executable CLI commands and explicit pause/checkpoint logic. Its main weakness is moderate redundancy across the output templates and guardrails that restates earlier guidance.

Suggestions

Collapse the three output template blocks into one parameterized template, or reference the shared structure, to remove repeated schema/progress scaffolding.

Trim the Guardrails section to only items not already stated in Step 6's "Pause if" and implementation notes to reduce duplication.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands, but three full output template blocks plus a Guardrails section restate pause/error conditions already covered in Step 6, so it could be tightened.	2 / 3
Actionability	It gives executable commands ("openspec status --change ... --json", "openspec instructions apply ... --json", "openspec list --json"), specific JSON fields to parse, and a concrete checkbox toggle ("- [ ]" → "- [x]"), making guidance copy-paste ready.	3 / 3
Workflow Clarity	A clear 7-step sequence with explicit checkpoints: state handling ("blocked", "all_done") and a "Pause if" block covering unclear tasks, design issues, errors, and user interrupts form a feedback loop for recovery.	3 / 3
Progressive Disclosure	The skill is a single self-contained SKILL.md with well-organized sections (Steps, Output templates, Guardrails, Fluid Workflow Integration) and no nested references, which fits the simple-skill allowance for well-structured single-file content.	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.

The description cleanly answers both what and when with explicit, natural trigger phrases and a distinct OpenSpec niche. It is slightly held back by action variants that restate one capability rather than listing distinct concrete actions.

Dimension	Reasoning	Score
Specificity	"Implement tasks from an OpenSpec change" names the domain and several action variants ("start implementing, continue implementation, or work through tasks"), but these are phases of one action rather than distinct concrete capabilities, so it falls short of the multi-action anchor.	2 / 3
Completeness	It explicitly states both what ("Implement tasks from an OpenSpec change") and when ("Use when the user wants to start implementing, continue implementation, or work through tasks"), matching the explicit-trigger anchor.	3 / 3
Trigger Term Quality	The "Use when" clause supplies natural phrases a user would say ("start implementing", "continue implementation", "work through tasks"), giving good coverage of likely phrasings.	3 / 3
Distinctiveness Conflict Risk	The "OpenSpec change" niche is specific and paired with workflow-specific triggers, making it 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-apply-change/SKILL.md
Commit: de8d68d

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