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

70%

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 ./.github/skills/openspec-archive-change/SKILL.md

Quality

Content

75%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 a clear, actionable, well-sequenced workflow with explicit validation checkpoints for a destructive archive operation. It is concise and well-structured, with only minor gaps around date generation and a touch of step/guardrail repetition.

Suggestions

Specify how to generate the YYYY-MM-DD date (e.g. via the current date tool or `date +%F`) so the archive target is unambiguous and executable.

Trim the overlap between the step descriptions and the Guardrails bullets (e.g. 'Always prompt for change selection' restates step 1) to tighten the token budget.

Dimension	Reasoning	Score
Conciseness	The body is efficient and assumes Claude's competence: it lists commands and decisions without explaining what archiving or specs are, with only minor repetition between the steps and the Guardrails section.	4 / 5
Actionability	Provides concrete, executable commands (openspec list --json, openspec status --change, mkdir -p, mv with a dated target) and clear AskUserQuestion/Task tool usage, with only minor gaps (no exact date command is specified).	4 / 5
Workflow Clarity	Six steps are clearly sequenced with explicit validation checkpoints (artifact completion, task completion, delta spec sync state) and confirm-via-AskUserQuestion loops; the destructive mv step has a pre-check for an existing target, though error-recovery feedback for the mv itself is light.	4 / 5
Progressive Disclosure	Well-organized into numbered steps plus Input, Output, and Guardrails sections with no bundle files; the single SKILL.md is appropriately scoped for this skill, with only minor inline detail that could remain.	4 / 5
	Total	16 / 20 Passed

Description

65%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 clearly states both what the skill does and when to use it, with a distinct openspec-workflow niche. It is slightly generic on the concrete actions involved and could use more natural trigger-term variants.

Suggestions

Enumerate one or two concrete actions (e.g. 'checks artifact and task completion, optionally syncs delta specs, then moves the change to the archive') to raise specificity.

Add natural synonyms a user might say such as 'close out', 'wrap up', or 'mark a change done' to broaden trigger-term coverage.

Dimension	Reasoning	Score
Specificity	States the domain ('archive a completed change in the experimental workflow') and one concrete action (finalize/archive), but does not enumerate the discrete steps like checking artifacts, checking tasks, assessing delta spec sync, and moving the directory.	3 / 5
Completeness	Explicitly answers what ('Archive a completed change in the experimental workflow') and when ('Use when the user wants to finalize and archive a change after implementation is complete') with a concrete trigger clause.	5 / 5
Trigger Term Quality	Includes 'finalize and archive a change' and 'after implementation is complete', which are reasonable trigger phrases, but lacks synonyms or variants users would naturally say (e.g. 'close out', 'wrap up', 'mark done').	3 / 5
Distinctiveness Conflict Risk	The 'openspec' experimental-workflow archive niche is fairly distinct and unlikely to trigger for unrelated skills, though it could overlap slightly with a sibling openspec sync/cleanup skill.	4 / 5
	Total	15 / 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: arm/mlia
Path: .github/skills/openspec-archive-change/SKILL.md
Commit: e91557a

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.