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

Quality

Content

85%

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

The body is a highly actionable, well-sequenced workflow with concrete commands and explicit validation before the destructive archive operation. The main weakness is redundancy between the Guardrails section and the step bodies, which inflates token cost without adding new information.

Suggestions

Trim the Guardrails section to only non-obvious constraints not already stated in the steps (e.g., "Preserve .openspec.yaml when moving"), removing restatements of selection prompting, sync assessment, and summary display.

Consider a brief note on recovering from the target-exists failure (e.g., how to choose a different date or rename) to strengthen the feedback loop around the destructive move.

Make the date source for YYYY-MM-DD explicit (e.g., current local date) so the generated archive name is unambiguous.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean operational guidance with no concept explanations, but the Guardrails section substantially restates steps already detailed above (prompt selection, sync assessment, warning handling, summary), adding redundancy that could be tightened.	2 / 3
Actionability	Provides concrete, executable commands ("openspec list --json", "openspec status --change \"<name>\" --json", "mkdir -p openspec/changes/archive", "mv openspec/changes/<name> openspec/changes/archive/YYYY-MM-DD-<name>") plus a copy-paste-ready output template and specific tool calls.	3 / 3
Workflow Clarity	Six steps are clearly sequenced with explicit validation checkpoints (artifact completion, task completion, delta-spec sync state, target-existence check) and confirmation prompts before the destructive move, satisfying the destructive-operation validation requirement.	3 / 3
Progressive Disclosure	Well-organized into Input, numbered Steps, Output, and Guardrails sections with easy navigation, and it appropriately defers sync logic to the openspec-sync-specs skill rather than inlining it; no bundle files are needed for this self-contained procedure.	3 / 3
	Total	11 / 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 cleanly answers both what the skill does and when to use it with an explicit trigger, but it names only a single action and uses a narrow set of trigger terms. Naming openspec and adding one or two more concrete sub-actions would lift specificity and distinctiveness.

Suggestions

Add openspec to the description (e.g., "Archive a completed openspec change") to sharpen distinctiveness and reduce conflict with generic archival skills.

Enumerate the concrete sub-actions the archive performs (e.g., checks artifact/task completion, syncs delta specs, moves the change to a dated archive folder) to reach the specificity top anchor.

Broaden trigger coverage with natural variations users might say, such as "close out", "wrap up", or "move a finished change to the archive".

Dimension	Reasoning	Score
Specificity	Names a concrete action ("Archive a completed change") and domain ("experimental workflow"), but lists only one primary action rather than multiple specific concrete actions, so it stops short of the top anchor.	2 / 3
Completeness	Explicitly answers what it does ("Archive a completed change in the experimental workflow") and when to use it via a clear "Use when the user wants to finalize and archive a change after implementation is complete" trigger.	3 / 3
Trigger Term Quality	Includes natural terms like "finalize", "archive", "completed change", and "after implementation is complete", but the vocabulary is narrow without common variations users might also say.	2 / 3
Distinctiveness Conflict Risk	The "experimental workflow" / "completed change" niche is somewhat specific, but "archive a change" could overlap with general archival or version-control skills, and the description does not name openspec to lock in the niche.	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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: fengshao1227/ccg-workflow
Path: .agents/skills/openspec-archive-change/SKILL.md
Commit: 9eaff79

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