openspec-archive-change

Archive a completed change in the experimental workflow. Use when the user wants to finalize and archive a change after implementation is complete.

Quality

76%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/openspec-archive-change/SKILL.md

Quality

Content

77%

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 archive workflow with strong validation and feedback loops for a destructive operation; its main weaknesses are minor Guardrails duplication and an all-inline structure with no progressive disclosure.

Suggestions

Remove Guardrails entries that restate steps already covered (change-selection prompting, inline sync, never-archive-while-syncing) to tighten the body and lift conciseness.

Consider extracting the detailed step-4 sync-verification criteria (ADDED/MODIFIED/REMOVED/RENAMED checks) into a referenced reference file so the SKILL.md overview stays lean.

If the sync verification detail is kept inline, tighten its prose to the essential pass/fail criteria to reduce token cost.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient for a complex workflow, but the Guardrails section restates step 1 ('Always prompt for change selection') and step 4 ('If sync is requested, run the openspec-sync-specs workflow inline', 'Never archive while a spec sync is still in flight'), fitting anchor 2's 'could be tightened' rather than the fully lean anchor 3.	2 / 3
Actionability	Concrete executable commands ('openspec list --json', 'openspec status --change "<name>" --json', 'mkdir -p "<planningHome.changesDir>/archive"', 'mv "<changeRoot>" ...'), named JSON fields, and explicit routing logic make it copy-paste ready, matching anchor 3.	3 / 3
Workflow Clarity	Steps 1-6 are clearly sequenced with explicit validation checkpoints (artifact completion, task counts, sync state) and a feedback loop ('If the sync failed, or any capability does not match, report what differs and stop — do not archive') plus a pre-move existence check on a destructive mv, matching anchor 3.	3 / 3
Progressive Disclosure	With no bundle files present the body is well-sectioned (Store selection, Input, Steps, Output, Guardrails), but all content is inline and the lengthy step-4 sync-verification prose is content that could arguably be split out, fitting anchor 2 rather than the 'content appropriately split' of anchor 3.	2 / 3
	Total	10 / 12 Passed

Description

75%

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 answers both what the skill does and when to use it with an explicit trigger and a distinct niche, though its action and trigger-term coverage is somewhat narrow for a single-purpose task.

Dimension	Reasoning	Score
Specificity	Quotes 'Archive a completed change in the experimental workflow' name a concrete action and domain, but only a single action (archive/finalize) rather than multiple specific concrete actions, matching anchor 2 rather than 3.	2 / 3
Completeness	It explicitly states what it does ('Archive a completed change in the experimental workflow') and when to use it ('Use when the user wants to finalize and archive a change after implementation is complete'), clearly answering both what and when with an explicit trigger, matching anchor 3.	3 / 3
Trigger Term Quality	'finalize and archive a change after implementation is complete' provides relevant natural keywords but with limited variation coverage, fitting anchor 2 ('some relevant keywords but missing common variations') rather than the broad coverage of anchor 3.	2 / 3
Distinctiveness Conflict Risk	The 'experimental workflow' change-archiving niche with 'after implementation is complete' framing gives distinct triggers unlikely to fire for unrelated skills, matching anchor 3; it is well above the generic overlap of anchor 2.	3 / 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: Fission-AI/OpenSpec
Path: skills/openspec-archive-change/SKILL.md
Commit: 6a5171e

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.