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

62%

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

62%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 content is highly actionable and the workflow has strong validation checkpoints, but it is padded with repetitive advisory prose and keeps everything inline rather than splitting detailed material into referenced files. Tightening the contract paragraphs and externalizing detail would lift both conciseness and progressive disclosure.

Suggestions

Compress the step-1 instructions/context/operationGuidance contract into a few terse bullets; it restates the 'advisory, never blocks' rule multiple times.

Move the lengthy runtime-context and artifact-rules contract into a referenced file (e.g. references/instructions-contract.md) and keep SKILL.md as an overview.

Trim redundant restatements in the Guardrails section that already appear inline in the steps.

Dimension	Reasoning	Score
Conciseness	The body is noticeably verbose, especially the multi-paragraph instructions archive / context / operationGuidance contract in step 1, which restates the same 'advisory and optional, never blocks' constraint several times in padded prose that Claude does not need.	2 / 5
Actionability	It provides concrete, executable commands (openspec status, instructions archive, mv, mkdir -p) with exact flags and JSON field names, with only minor gaps in copy-paste completeness.	4 / 5
Workflow Clarity	The six-step workflow is clearly sequenced with explicit validation checkpoints: completion checks with user confirmation, a sync-then-verify loop that stops on mismatch, and an existence check before moving changeRoot, satisfying the destructive-operation feedback-loop requirement.	5 / 5
Progressive Disclosure	Structure exists (Steps, Output, Guardrails) but all guidance is inlined into one monolithic file with no one-level-deep references to separate detail files; content that could live in references (e.g. the long context/guidance contract) is inline.	3 / 5
	Total	14 / 20 Passed

Description

62%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 is clear and includes both a 'what' and a 'when' clause, but it under-describes the concrete archive operations and misses some natural trigger synonyms. It is solid but not comprehensive.

Suggestions

Add 1-2 concrete actions to the description (e.g., 'check artifact and task completion, sync delta specs to main specs, then move the change into the archive').

Broaden trigger terms with natural synonyms such as 'finish', 'close out', or 'wrap up a change'.

Dimension	Reasoning	Score
Specificity	It names the domain ('archive a completed change in the experimental workflow') and one concrete action ('finalize and archive a change'), but does not enumerate the multiple concrete operations the skill performs (status check, task check, delta-spec sync, mv to archive).	3 / 5
Completeness	It clearly answers 'what' ('Archive a completed change') and 'when' ('Use when the user wants to finalize and archive a change after implementation is complete'); the trigger clause is explicit but could be slightly more specific.	4 / 5
Trigger Term Quality	It includes relevant terms like 'archive', 'completed change', and 'finalize', but lacks common user-facing synonyms such as 'done', 'finish', or 'close out a change'.	3 / 5
Distinctiveness Conflict Risk	The 'archive a completed change' niche is fairly distinct from sibling openspec skills, with minor overlap risk against related change-management skills.	4 / 5
	Total	14 / 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: Fission-AI/OpenSpec
Path: skills/openspec-archive-change/SKILL.md
Commit: 6926ccb

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