CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

openspec-archive-change

Archive a completed OpenSpec change in the experimental workflow. Use when the user wants to finalize and archive a change after implementation is complete. Also use when the user says "openspec archive" or "opsx archive".

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Critical

Do not install without reviewing

SKILL.md
Quality
Evals
Security

Quality

Content

70%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 body delivers a rigorous, well-validated workflow with copy-paste commands and strong error-recovery semantics appropriate to a destructive archive operation. Its main costs are token weight from repeated guardrail restatements and a monolithic structure that keeps reference-worthy material inline.

Suggestions

Remove the Guardrails lines that restate step-1 contracts verbatim (e.g., the 'never copy runtime context/guidance/rule text verbatim' rules) and keep only the genuinely additive guardrails, cutting redundant tokens.

Move the step-4 sync verification contract (title/purpose/heading rules and the post-sync comparison criteria) into a references/ file (e.g., references/sync-contract.md) and link to it from step 4, slimming the main body.

Condense the store-selection and root-null branching prose into a compact decision table or short bulleted contract to reduce the dense multi-clause paragraphs.

DimensionReasoningScore

Conciseness

The content is domain-specific rather than explaining known concepts, but the Guardrails section restates rules already detailed in step 1 (e.g., 'Never copy runtime context, operation guidance, or artifact-rule text verbatim into output files'), and the store-selection and root-null paragraphs are dense prose that could be tightened.

3 / 5

Actionability

Provides concrete executable commands with placeholders ('openspec status --change "<name>" --json', 'mkdir -p', 'mv') and specific JSON fields to parse, but the sync execution is delegated to the 'openspec-sync-specs workflow' and some comparisons are described only at prose level.

4 / 5

Workflow Clarity

Six clearly sequenced steps with extensive validation checkpoints (artifact/task status checks, sync-blocked detection, post-sync verification re-run across every capability) and explicit feedback loops with recovery paths ('Nothing has moved and changeRoot is intact, so the user can fix the mismatch'), plus a guardrails checklist for a destructive move operation.

5 / 5

Progressive Disclosure

No bundle files exist and the ~220-line body inlines content that plausibly belongs in reference files (store-selection rules, root-null branching, the step-4 sync verification contract), though internal section structure with numbered steps and headers is solid.

3 / 5

Total

15

/

20

Passed

Description

82%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 cleanly follows the what-and-when pattern with explicit, command-level trigger phrases that make it highly discoverable and distinctive. Its only weakness is that it names just one capability action, which limits the specificity score even though the skill is single-purpose.

DimensionReasoningScore

Specificity

Names the domain ('OpenSpec change') and one concrete action ('Archive a completed OpenSpec change'), but does not list several specific actions as anchor 4 requires — coverage is limited to the single archive/finalize action.

3 / 5

Completeness

Explicitly answers both what ('Archive a completed OpenSpec change in the experimental workflow') and when ('Use when the user wants to finalize and archive a change... Also use when the user says...') with concrete trigger phrases, matching the anchor-5 example structure.

5 / 5

Trigger Term Quality

Includes literal command triggers users would type ('openspec archive', 'opsx archive') plus natural phrasing ('finalize and archive a change after implementation is complete'), but misses common variations like 'close the change' or 'wrap up the change'.

4 / 5

Distinctiveness Conflict Risk

A clear niche (archiving completed OpenSpec changes) with command-literal triggers ('openspec archive', 'opsx archive') that minimize overlap risk with sibling openspec skills.

5 / 5

Total

17

/

20

Passed

Validation

100%

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

Fission-AI/OpenSpec

Path

skills/openspec-archive-change/SKILL.md

Reviewed

Table of Contents

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.