CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

openspec-bulk-archive-change

Archive multiple completed OpenSpec changes at once. Use when archiving several parallel changes. Also use for a plural archive request - "openspec bulk-archive", "opsx bulk-archive", "openspec archive all", or "openspec archive these changes".

Quality

82%

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

The canonical home for this skill is openspec-bulk-archive-change in Fission-AI/OpenSpec

SKILL.md
Quality
Evals
Security

Quality

Content

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

An operationally excellent skill body: fully executable commands, exact JSON contracts, and a batch workflow with unusually thorough validation and failure handling. Its weaknesses are length — significant duplication between the steps and the Guardrails section — and the absence of any progressive disclosure, with everything monolithically inlined in one long file.

Suggestions

Move the store-selection and project-check preamble into a shared reference file (e.g. references/store-selection.md) — it is generic OpenSpec workflow boilerplate unrelated to archiving specifically and likely duplicated across sibling skills.

Trim the Guardrails section to only rules not already stated in the steps; items like the target-date rule and 'never archive while a sync is in flight' restate step 3d/8c content nearly verbatim.

Move the conflict-resolution examples and output templates into a reference file to shorten the main body while keeping the step sequence lean.

DimensionReasoningScore

Conciseness

Mostly efficient, dense operational specifics that assume Claude's competence and never explain known concepts, but there is real tightening to do: the Guardrails section restates step 3d/8c rules nearly verbatim, and the store-selection/project-check preamble re-explains the same flag rules several times. Not 2 because the verbosity is repetition of genuinely necessary operational detail, not padding or explanations of concepts Claude already knows.

3 / 5

Actionability

Fully executable guidance throughout: exact commands with flags (`openspec list --json`, `openspec status --change "<name>" --json`), exact JSON fields to parse, copy-paste-ready bash for the archive move, concrete conflict-resolution walkthroughs, and complete output templates. Matches the 'copy-paste ready, covers common cases' anchor.

5 / 5

Workflow Clarity

Nine clearly sequenced steps with explicit validation checkpoints for a destructive batch operation: batch validation before any write (step 3), a user confirmation gate (step 7), verify-before-move of synced specs (step 8b), re-checking the archive target immediately before the move, and a post-move nesting check with recovery. Error-recovery loops and a guardrails checklist match the top anchor; the batch-operation validation cap does not apply because validation is extensive.

5 / 5

Progressive Disclosure

The in-body structure is well organized (numbered steps, bold sections, examples, guardrails), but there are no bundle files at all: store-selection and project-check boilerplate, conflict-resolution examples, and output templates that clearly belong in separate reference files are all inlined into a single ~365-line body. Not 2 because navigation within the file is good and sections are clearly signaled; not 4 because content that should be split out is inline with no references.

3 / 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 description: it clearly and explicitly states what the skill does and when to use it, with concrete, natural trigger phrases including a CLI synonym. The main gaps are minimal enumeration of the skill's specific capabilities beyond the core archive action and a few missing trigger variations.

DimensionReasoningScore

Specificity

Names the domain (OpenSpec changes) and one concrete action — "Archive multiple completed OpenSpec changes at once" — but does not list the several other actions the skill performs (conflict detection, spec syncing, batch validation), matching the '1-2 concrete actions, not comprehensive' anchor. Not 4 because coverage of the skill's capabilities is minimal beyond the single archive action.

3 / 5

Completeness

Explicitly answers both questions: what it does ("Archive multiple completed OpenSpec changes at once") and when to use it, with concrete quoted trigger phrases ("Use when archiving several parallel changes. Also use for a plural archive request - ..."). This clearly matches the top anchor and exceeds the level-4 anchor, whose 'when' is less explicit.

5 / 5

Trigger Term Quality

Includes natural trigger phrasings users would actually say — "openspec bulk-archive", "opsx bulk-archive", "openspec archive all", "openspec archive these changes" — covering a CLI-name synonym (opsx) and plural request forms. Not 5 because a few natural variations like "batch archive" or "archive everything" are missing.

4 / 5

Distinctiveness Conflict Risk

Clear niche (plural/bulk archiving of OpenSpec changes) with distinct triggers unlikely to fire for unrelated skills. Not 5 because triggers like "openspec archive all" overlap the prefix of a plausible single-change archive sibling skill, creating minor conflict risk with a closely related skill.

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-bulk-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.