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

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

100%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured, actionable workflow skill with concrete executable commands, explicit validation checkpoints, and clean organization. It respects token budget while remaining copy-paste ready and appropriately self-contained.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence, using exact commands and paths with no padding or explanation of concepts Claude already knows, so every token earns its place.	3 / 3
Actionability	It provides fully executable commands with exact flags and paths (e.g., `openspec status --change "<name>" --json`, `mv openspec/changes/<name> openspec/changes/archive/...`) that are copy-paste ready.	3 / 3
Workflow Clarity	A clear six-step sequence with explicit validation checkpoints (artifact status, task completion, archive-target existence) and confirm-and-proceed feedback loops for the destructive move operation.	3 / 3
Progressive Disclosure	The skill is a single self-contained SKILL.md with no bundle files, organized into clear Input, Steps, Output, and Guardrails sections, with no nested references.	3 / 3
	Total	12 / 12 Passed

Description

90%

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-constructed description that answers both what and when with natural trigger terms and a clear niche. The only minor gap is specificity, since it names a single archiving action rather than enumerating several concrete operations.

Suggestions

Consider naming one or two additional concrete actions (e.g., 'check artifact and task completion, sync specs, and move the change to archive') to lift specificity from domain-plus-action to multiple concrete actions.

Dimension	Reasoning	Score
Specificity	The description names the domain and the core action ("Archive a completed change") but does not enumerate multiple concrete actions, matching the anchor that names domain and some actions without being comprehensive.	2 / 3
Completeness	It clearly answers what ("Archive a completed change") and when (explicit "Use when the user wants to finalize and archive a change after implementation is complete"), satisfying both requirements.	3 / 3
Trigger Term Quality	"finalize and archive a change" are natural phrases a user would actually say, giving good coverage of relevant trigger terms.	3 / 3
Distinctiveness Conflict Risk	Tied to a specific experimental-workflow niche ("completed change", "archive") with distinct triggers unlikely to conflict with other skills.	3 / 3
	Total	11 / 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: arm/mlia
Commit: 053fcb5

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