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

74%

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 ./.claude/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.

A well-structured, actionable multi-step workflow with explicit validation checkpoints and clear guardrails. It is concise and executable, with only minor gaps in post-archive verification and in the concreteness of the delegated sync reference.

Suggestions

Add a post-move verification step (e.g., confirm `openspec/changes/archive/YYYY-MM-DD-<name>/` exists and `openspec/changes/<name>` no longer exists) to close the feedback loop on the destructive `mv` and lift workflow clarity.

Replace the abstract 'execute /opsx:sync logic (use the openspec-sync-specs skill)' with a concrete pointer or invocation so the delegation is unambiguous.

Tighten the repeated 'Use the AskUserQuestion tool to confirm user wants to proceed / Proceed if user confirms' phrasing in steps 2 and 3 to a single stated convention.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean with concrete commands and no padding about what openspec or archives are; a few phrases like 'Use the AskUserQuestion tool' and repeated confirmation sub-steps across steps 2-4 could be tightened slightly.	4 / 5
Actionability	Concrete, runnable commands are given (`openspec list --json`, `openspec status --change`, `mkdir -p`, `mv ...`) with parsed JSON fields, though the archive `mv` and date formatting are pseudocode-ish templates the agent must instantiate rather than fully copy-paste-ready.	4 / 5
Workflow Clarity	A clear six-step sequence with explicit validation checkpoints (artifact status, task completion, delta-sync assessment) and confirm-before-proceed prompts; it is not a 5 because the final destructive move lacks an explicit post-move verification that the archived directory exists and the source is gone.	4 / 5
Progressive Disclosure	Good sectioned structure (Input, Steps, Output On Success, Guardrails) with one-level-deep delegation ('use the openspec-sync-specs skill') rather than nested references; minor gap is that the delegated sync logic is referenced but not linked to a concrete file path.	4 / 5
	Total	16 / 20 Passed

Description

73%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.

A well-formed third-person description that cleanly answers both what and when with an explicit 'Use when' trigger. It is concise and reasonably distinct, though the action description is somewhat minimal rather than enumerating the concrete archival sub-steps.

Suggestions

Consider expanding the capability clause to name 2-3 concrete actions (e.g., 'verify completion, sync delta specs, and move a completed change to the archive') to lift specificity above the single-action anchor.

Add a natural synonym or two users might say (e.g., 'close out', 'store a finished change') to broaden trigger coverage.

Dimension	Reasoning	Score
Specificity	The description names the domain ('Archive a completed change in the experimental workflow') but lists only one concrete action ('finalize and archive a change') rather than enumerating several specific actions like prompting, status checks, syncing, and moving to archive.	3 / 5
Completeness	It explicitly answers both 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'), satisfying the highest anchor with concrete trigger phrases.	5 / 5
Trigger Term Quality	Natural user-facing terms are present ('archive', 'completed change', 'finalize', 'after implementation is complete'); a few common variations like 'save', 'store', or 'close out a change' are missing but coverage is good.	4 / 5
Distinctiveness Conflict Risk	The 'openspec experimental workflow' niche and 'completed change' scope make it mostly distinct from generic skills, though it could overlap slightly with sibling openspec skills like sync or list that also touch changes.	4 / 5
	Total	16 / 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: PBH-BTN/PeerBanHelper
Path: .claude/skills/openspec-archive-change/SKILL.md
Commit: f8e9b1b

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.