openspec-apply-change

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

Quality

67%

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

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/openspec-apply-change/SKILL.md

Quality

Content

61%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 an actionable, well-sequenced workflow with concrete CLI commands and clear state handling. Its main weaknesses are redundant output templates/guardrails and a missing proactive verification checkpoint in the batch task loop.

Suggestions

Add an explicit verification step (e.g., run tests or re-run 'openspec status' to confirm) before flipping a task's checkbox to '- [x]', satisfying the batch-operation validation requirement.

Consolidate the three Output templates and the Guardrails section with the Steps to remove repeated guidance (keep changes minimal, pause on blockers) and tighten conciseness.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with concrete CLI commands and numbered steps, but the three output templates and the Guardrails section substantially restate guidance already in the Steps (e.g., keep changes minimal, pause on blockers), so it could be tightened, fitting 3 over 4.	3 / 5
Actionability	Provides concrete, executable commands ('openspec status --change "<name>" --json', 'openspec instructions apply', checkbox flipping) and specific JSON fields to parse, with only minor gaps such as an example task-line format, landing at 4 rather than 5.	4 / 5
Workflow Clarity	The 7-step sequence is clear with state handling and pause conditions, but for a batch code-implementation loop there is no explicit verification/test checkpoint before marking each task complete (- [ ] -> - [x]); the rubric caps batch-operation skills lacking validation at 3, and the pause conditions are reactive rather than proactive validation.	3 / 5
Progressive Disclosure	No bundle files exist and the content is well-organized into clearly headed sections (Steps, Output templates, Guardrails, Fluid Workflow Integration) with no nested references; at 156 lines some template content could be trimmed, keeping it at 4 rather than 5.	4 / 5
	Total	14 / 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 clearly states both the skill's purpose and its triggers, scoped to a distinct OpenSpec niche with low conflict risk. It is held back only by slightly thin 'what' specificity and a few missing natural synonyms.

Suggestions

Expand the 'what' clause with a couple more concrete capabilities (e.g., 'reads context files, implements pending tasks, marks progress') to lift specificity from 3 to 4.

Add common natural synonyms such as 'build', 'code', or 'finish the change' to broaden trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Names the domain ('OpenSpec change') and concrete actions ('start implementing, continue implementation, or work through tasks'), but the actions are variations of one theme rather than a comprehensive list of distinct capabilities, fitting the 3 anchor better than 4.	3 / 5
Completeness	Clearly answers both 'what' ('Implement tasks from an OpenSpec change') and 'when' ('Use when the user wants to start implementing...') with concrete triggers; the 'what' is slightly thin so it sits at 4 rather than 5.	4 / 5
Trigger Term Quality	Includes natural phrases users would say ('start implementing', 'continue implementation', 'work through tasks') with good coverage, though a few common synonyms like 'build' or 'code' are missing, placing it just below a 5.	4 / 5
Distinctiveness Conflict Risk	Scoped to a specific niche ('OpenSpec change') with distinct triggers and minimal overlap risk with other skills, matching the 5 anchor.	5 / 5
	Total	16 / 20 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: KunAgent/Kun
Path: .claude/skills/openspec-apply-change/SKILL.md
Commit: 7538cc9

Reviewed: 1 day 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.