openspec-apply-change

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

1.06x

Quality

71%

Does it follow best practices?

Impact

87%

1.06x

Average score across 3 eval scenarios

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

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

The canonical home for this skill is openspec-apply-change in fengshao1227/ccg-workflow

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 skill provides a clear, mostly actionable workflow with concrete CLI commands, but repeats guardrail content across sections and lacks a validation checkpoint before marking batch tasks complete.

Suggestions

Add an explicit validation step in Step 6 (e.g., run tests or verify the change compiles) before flipping a task's checkbox from - [ ] to - [x], so the workflow has a feedback loop for this batch operation.

De-duplicate the Guardrails section against Step 6 — keep only guidance not already stated (e.g., remove repeated 'keep changes minimal', 'pause on ambiguity', 'update checkbox' lines) to improve conciseness.

Condense the three full output templates into one compact example plus a short note describing the completion and pause variants, reducing inline bulk.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient but the Guardrails section substantially restates Step 6 (keep changes minimal, pause on ambiguity, read context files, update checkbox) and three full output templates add length, so it could be tightened.	3 / 5
Actionability	Concrete executable commands (openspec status/instructions/list with --json), specific checkbox edits, and state handling give mostly executable guidance with only minor gaps such as no verification command before marking a task done.	4 / 5
Workflow Clarity	The 7-step sequence and state handling are clear, but this batch implementation skill marks tasks complete immediately after coding with no validate/test checkpoint before flipping the checkbox; the destructive/batch-operation cap holds workflow_clarity at 3.	3 / 5
Progressive Disclosure	The single-file body is well-organized with clear section headers and no nested references, and no bundle files are needed; minor gaps come from inlining three full output templates that could be condensed.	4 / 5
	Total	14 / 20 Passed

Description

82%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 cleanly answers both what and when with natural trigger phrasing and a distinct niche. Its main limitation is specificity, listing only a single concrete action.

Dimension	Reasoning	Score
Specificity	"Implement tasks from an OpenSpec change" names the domain and one concrete action (implementing tasks) but offers no additional specific actions, matching the anchor that names a domain with 1-2 concrete actions without comprehensive coverage.	3 / 5
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") with concrete trigger phrases, matching the top anchor.	5 / 5
Trigger Term Quality	"start implementing, continue implementation, or work through tasks" are natural phrases a user would say, giving good keyword coverage; it falls short of 5 because the synonym set is limited and no file/extension triggers apply.	4 / 5
Distinctiveness Conflict Risk	"OpenSpec change" is a clear niche with distinct triggers unlikely to be confused with other skills, matching the minimal-conflict-risk anchor.	5 / 5
	Total	17 / 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: arm/mlia
Path: .codex/skills/openspec-apply-change/SKILL.md
Commit: e91557a

Reviewed: 5 days 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.