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

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

73%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 highly actionable, well-sequenced workflow with excellent validation and rollback behavior for a destructive operation (moving changeRoot). The main weakness is token efficiency: repetitive caveat restatements and a Guardrails section that duplicates body content inflate the budget without adding guidance.

Suggestions

Cut redundant restatements: the store-selection paragraph, the instructions-archive advisory handling, and the Guardrails section each repeat rules already stated in the body — consolidate to one statement each.

Move the detailed post-sync structural verification contract (title, Purpose, heading rules) into a reference file or delegate it to the openspec-sync-specs workflow it describes, shortening step 4 substantially.

Tighten the project-check section's three branches into a compact decision list to reduce conditional prose.

DimensionReasoningScore

Conciseness

Most content is CLI-specific contract knowledge Claude would not know, but it is noticeably padded: the store-selection and project-check sections repeat the same caveats in multiple phrasings, and the Guardrails section restates rules already stated in the body. It could be tightened considerably without losing information.

3 / 5

Actionability

Nearly every step has copy-paste commands ("openspec instructions archive --change \"<name>\" --json", "openspec status --change \"<name>\" --json", "mkdir -p", "mv") with named JSON fields to parse. Minor gaps remain: the sync execution ("run the openspec-sync-specs workflow inline") and the post-sync comparison are prose-level rather than concrete invocations.

4 / 5

Workflow Clarity

A clear six-step sequence with explicit validation checkpoints at every phase — artifact status, task-count validation, pre-sync rule fetch with required zero exit, post-sync structural verification re-run across all capabilities — plus explicit failure handling, stop conditions, and rollback guarantees ("Nothing has moved... so the user can fix the blocking condition").

5 / 5

Progressive Disclosure

No bundle files exist and the content is the executable workflow itself rather than deferrable reference material, organized into well-labeled sections (Store selection, Project check, Steps 1-6, Output, Guardrails). The main gap is that step 4 inlines the ~60-line sync contract that belongs to the referenced openspec-sync-specs workflow, which a separate reference file could absorb.

4 / 5

Total

16

/

20

Passed

Description

78%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 strong single-purpose description: it clearly states what the skill does and when to use it, with exact command triggers. Its main weakness is limited action coverage — the spec-sync step, a substantial part of the workflow, is absent.

Suggestions

Mention the spec-sync capability, e.g., "syncs delta specs to main specs before archiving when needed", to improve action coverage.

Add one or two natural phrasing variants users might say, such as "archive the change" or "close out this change".

DimensionReasoningScore

Specificity

Names the domain and core action concretely ("Archive a completed OpenSpec change in the experimental workflow") but lists only 1-2 actions; the significant spec-sync capability of the skill is not mentioned, leaving coverage gaps.

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 after implementation is complete") with concrete trigger phrases.

5 / 5

Trigger Term Quality

Includes the exact natural command phrases users would say ("openspec archive", "opsx archive") plus "finalize and archive a change after implementation is complete", but misses common variations like "archive the change" or "close this change".

4 / 5

Distinctiveness Conflict Risk

"OpenSpec" and "opsx archive" carve out a clear niche with distinct command triggers, but there is minor overlap risk with sibling OpenSpec workflow skills (e.g., a non-experimental archive skill) that the description does not disambiguate beyond "experimental workflow".

4 / 5

Total

16

/

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

test/fixtures/released-output/v1.16.0-claude-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.