openspec-apply-change

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

Quality

83%

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.

The body is a highly actionable, well-sequenced workflow with concrete commands and validation checkpoints, organized cleanly into a single self-contained file. The only weakness is mild verbosity from redundant output templates and guardrails that restate the steps.

Suggestions

Collapse the three 'Output During/On Completion/On Pause' templates into a single compact format with conditional variants, or move them to a reference file, to reduce token cost.

Trim the Guardrails list to items not already stated in the numbered Steps to avoid repetition.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient procedural guidance that assumes Claude's competence, but the three prescriptive output templates and the Guardrails section (which restate the step instructions) could be tightened, matching 'mostly efficient but includes some unnecessary explanation or could be tightened'.	2 / 3
Actionability	It gives fully executable commands (e.g., 'openspec status --change "<name>" --json', 'openspec instructions apply --change "<name>" --json'), concrete file-path handling, and a literal '- [ ] to - [x]' checkbox update, matching the 'fully executable, copy-paste ready' anchor.	3 / 3
Workflow Clarity	A clear 7-step sequence with explicit state handling (blocked, all_done) and pause-on-error/blocker checkpoints provides the validation feedback loops the rubric rewards, matching the 'clear sequence with explicit validation steps' anchor.	3 / 3
Progressive Disclosure	No bundle files exist and none are needed; the single SKILL.md is well-organized into Steps, Output, Guardrails, and Fluid Workflow sections, which the rubric allows to score 3 for skills with no need for external references.	3 / 3
	Total	11 / 12 Passed

Description

82%

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 an explicit trigger clause and natural language, but it is light on specific actions and its triggers are generic verbs that lean on the OpenSpec noun for distinctiveness.

Suggestions

Add one or two more concrete actions (e.g., 'mark tasks complete, run status checks') to lift specificity from 2 to 3.

Tighten trigger terms to include OpenSpec-specific phrasing users would actually say (e.g., 'apply an OpenSpec change', 'resume a paused change') to reduce overlap with generic implementation skills.

Dimension	Reasoning	Score
Specificity	The description names the domain ("OpenSpec change") and one concrete action ("Implement tasks"), but does not enumerate multiple specific actions, matching the 'names domain and some actions, but not comprehensive' anchor rather than the multi-action level 3.	2 / 3
Completeness	It states what the skill does ('Implement tasks from an OpenSpec change') and gives an explicit 'Use when...' trigger, satisfying the 'clearly answers both what AND when' anchor.	3 / 3
Trigger Term Quality	The 'Use when the user wants to start implementing, continue implementation, or work through tasks' clause covers several natural phrases a user would say, aligning with the 'good coverage of natural terms' anchor.	3 / 3
Distinctiveness Conflict Risk	The OpenSpec niche is specific, but the trigger verbs ('start implementing', 'work through tasks') are generic and could overlap with other implementation skills; distinction relies almost entirely on the 'OpenSpec' proper noun, matching 'somewhat specific but could still overlap'.	2 / 3
	Total	10 / 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: rpamis/comet
Path: eval/local/skills/benchmarks/dependency/openspec/openspec-apply-change/SKILL.md
Commit: 2945693

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