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

72%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./.github/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.

This is a well-crafted workflow skill with strong actionability and excellent workflow clarity, featuring concrete commands, explicit validation checkpoints, and user confirmation gates at each critical decision point. The main weaknesses are minor verbosity (some redundancy between steps and guardrails) and the lack of bundle files to support progressive disclosure for what is a fairly detailed procedure.

Suggestions

Remove redundant guardrails that restate instructions already covered in the steps (e.g., 'Always prompt for change selection if not provided' duplicates Step 1).

Trim explanatory phrases Claude doesn't need, such as 'Parse the JSON to understand' — just list the relevant fields directly.

Dimension	Reasoning	Score
Conciseness	The skill is reasonably efficient but includes some redundant phrasing and could be tightened. For example, the guardrails section partially repeats instructions already given in the steps. Some explanations like 'Parse the JSON to understand' are unnecessary for Claude.	2 / 3
Actionability	Provides concrete CLI commands (openspec list --json, openspec status --change, mkdir -p, mv), specific file paths, exact bash commands, and clear tool invocations (AskUserQuestion, Task tool with subagent_type). The output template is copy-paste ready with clear placeholders.	3 / 3
Workflow Clarity	Excellent multi-step workflow with clear sequencing (6 numbered steps), explicit validation checkpoints at each stage (artifact completion, task completion, delta spec sync), feedback loops with user confirmation via AskUserQuestion before proceeding past warnings, and error handling (e.g., archive target already exists).	3 / 3
Progressive Disclosure	The content is well-structured with clear sections and headers, but it's a fairly long monolithic document with no references to supporting files. The delta spec sync step delegates to another skill (openspec-sync-specs) which is good, but the overall content could benefit from splitting detailed sub-procedures into referenced files.	2 / 3
	Total	10 / 12 Passed

Description

67%

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 has a clear structure with both 'what' and 'when' clauses, which is good for completeness. However, it lacks specificity about what concrete actions archiving involves and uses somewhat generic terminology that could overlap with other workflow-related skills. The trigger terms are adequate but could be expanded with more natural user language variations.

Suggestions

Add specific concrete actions involved in archiving (e.g., 'moves change files to archive directory, updates status tracking, generates completion summary').

Include more natural trigger term variations users might say, such as 'close out', 'mark as done', 'wrap up', 'finish change', or 'complete workflow step'.

Clarify what 'experimental workflow' refers to more precisely to reduce potential overlap with other workflow or archival skills.

Dimension	Reasoning	Score
Specificity	Names the domain ('archive a completed change in the experimental workflow') and one action ('finalize and archive'), but doesn't list multiple concrete actions or describe what archiving entails (e.g., moving files, updating status, creating records).	2 / 3
Completeness	Clearly answers both 'what' (archive a completed change in the experimental workflow) and 'when' (when the user wants to finalize and archive a change after implementation is complete) with an explicit 'Use when' clause.	3 / 3
Trigger Term Quality	Includes some relevant terms like 'archive', 'finalize', 'completed change', and 'implementation is complete', but misses common variations users might say such as 'close out', 'mark done', 'finish', 'wrap up', or 'complete a task'.	2 / 3
Distinctiveness Conflict Risk	The phrase 'experimental workflow' provides some specificity, but 'archive a completed change' is somewhat generic and could overlap with other archival, completion, or workflow management skills. The scope of what constitutes a 'change' is unclear.	2 / 3
	Total	9 / 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 — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository: arm/mlia
Commit: 3e21e30

Reviewed: 3 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.