CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

openspec-apply-change

Implement tasks from an OpenSpec change. Use when the user wants to start implementing, continue implementation, or work through tasks. Also use when the user says "openspec apply", "opsx apply", or "openspec implement".

Quality

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

70%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 delivers a highly actionable, well-sequenced CLI workflow with strong validation feedback loops, but it is noticeably redundant - the same rules on pausing, context/guidance handling, and completion are repeated across steps, guardrails, and output templates. It is also a long monolithic file with no reference files despite clearly splittable content like the output templates.

Suggestions

Deduplicate the guardrails section against the pause conditions in step 6 and the context/operationGuidance rules in steps 3-4 - each rule is currently stated two to three times; state each once in the step where it applies and keep the guardrails to non-duplicated invariants.

Tighten the store-selection paragraph: lead with the single rule (pass --store <id> on reads/writes once selected, keep it sticky) and trim the restated examples and command enumerations.

Move the three full output templates (Implementing / Complete / Paused) into a references/output-templates.md file and reference it one level deep, keeping SKILL.md to the workflow itself.

DimensionReasoningScore

Conciseness

The pause conditions, the context/operationGuidance handling rules, and the 'review before archiving' note are each stated two to three times across steps 3-4, the guardrails, and the output templates, and the store-selection paragraph is a dense padded wall of conditionals. This matches anchor 2 ('several unnecessary explanations or padded sections') rather than 3, since the duplication is systematic rather than occasional over-explanation.

2 / 5

Actionability

Copy-paste-ready commands (`openspec status --change "<name>" --json`, `openspec instructions apply --change "<name>" --json`), specific JSON fields to parse (schemaName, contextFiles, sourcePath, line), and an exact edit instruction (`- [ ]` to `- [x]`) make the guidance fully executable. Not 4 because the concrete commands and field-level parsing cover the common cases without gaps.

5 / 5

Workflow Clarity

A clear 7-step sequence with explicit validation checkpoints and feedback loops: confirm the checkbox at sourcePath/line before editing, rerun apply instructions after marking, and confirm progress changed; pause conditions and blocked/all_done state handling are enumerated. This matches anchor 5; anchor 4 would require missing checkpoints, which are present.

5 / 5

Progressive Disclosure

The steps are organized with headers, but this is a ~195-line single file with no bundle references at all, and content that could be split out is inlined (three full output templates, the store-selection and project-check prose). This fits anchor 3 ('could be better organized; content that should be separate is inline'); it is not 2 because structure is real and coherent, and not 4 because nothing is offloaded and the file is well over the simple-skill threshold.

3 / 5

Total

15

/

20

Passed

Description

86%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.

A concise, well-formed description with an explicit 'Use when' clause and comprehensive natural trigger phrasing including CLI command synonyms. Its only weakness is that the 'what' states a single action rather than enumerating the workflow's concrete capabilities, and one trigger phrase is generic enough to create minor overlap risk.

DimensionReasoningScore

Specificity

"Implement tasks from an OpenSpec change" names the domain and one concrete action, but does not enumerate the several specific actions the workflow performs (check status, fetch apply instructions, read context files, update task checkboxes). This matches anchor 3; it is not 4 because no list of several specific actions is present, and not 2 because the action stated is concrete rather than generic.

3 / 5

Completeness

It explicitly answers both what ("Implement tasks from an OpenSpec change") and when ("Use when the user wants to start implementing... Also use when the user says 'openspec apply'...") with concrete trigger phrases. This clearly matches anchor 5 rather than 4, whose 'when' is less explicit.

5 / 5

Trigger Term Quality

Natural phrases users would say ("start implementing", "continue implementation", "work through tasks") plus command-form synonyms ("openspec apply", "opsx apply", "openspec implement") give comprehensive coverage of how this need is expressed. Not 4 because no meaningful natural variant of the request is missing for this niche.

5 / 5

Distinctiveness Conflict Risk

The OpenSpec niche and CLI command triggers make it mostly distinct, but "work through tasks" is generic and could fire for non-OpenSpec task work, a minor overlap risk. This fits anchor 4; it is not 5 because of that generic phrase, and clearly not 3 since the dominant triggers are highly specific.

4 / 5

Total

17

/

20

Passed

Validation

100%

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

Fission-AI/OpenSpec

Path

skills/openspec-apply-change/SKILL.md

Reviewed

Table of Contents

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.