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

Critical

Do not install without reviewing

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 exceptionally rigorous operational workflow: fully executable commands, exact JSON contracts, and validation checkpoints at every destructive boundary of the batch archive. The weaknesses are redundancy (duplicated output templates and a guardrails section that restates the steps) and a monolithic 377-line body with no progressive disclosure of examples or templates into reference files.

Suggestions

Move the conflict-resolution examples and the 'Output On Success/Partial/No Changes' templates into a references/ file (e.g., references/examples.md) and keep a single canonical output format in the body, cutting the duplicated step-9 examples.

Trim the guardrails section to only rules not already stated in steps 3d/8c (e.g., the target-name computation and archive-collision rules appear three times) to reduce token cost without losing constraints.

Tighten the store-selection paragraph by replacing the repeated per-command flag instructions with one short rule ('append --store <id> to every command that reads or writes specs/changes') plus the command list.

DimensionReasoningScore

Conciseness

The body is dense and purely operational with no explanations of concepts Claude already knows, but there is noticeable redundancy: output templates are duplicated (step 9 examples vs. the 'Output On Success/Partial Success' sections), roughly 28 guardrail bullets restate earlier steps verbatim (e.g., the target-name rule appears in steps 3d, 8c, and the guardrails), and the store-selection paragraph is convoluted. This fits anchor 3 (mostly efficient but could be tightened) better than 2, since the padding is repetition rather than unnecessary explanation.

3 / 5

Actionability

Fully executable throughout: exact commands (`openspec list --json`, `openspec status --change "<name>" --json`, `mkdir -p`/`mv`), exact JSON fields to parse (`schemaName`, `planningHome`, `artifactPaths`), the literal match pattern `### Requirement: <name>`, concrete table and output templates, and worked conflict-resolution examples. This matches anchor 5 (copy-paste ready commands covering common cases), one level above anchor 4's 'minor gaps'.

5 / 5

Workflow Clarity

Nine clearly sequenced steps with explicit validation checkpoints and feedback loops for this batch/destructive operation: archive-target collision check before any spec write (3d), specs-rule snapshots fetched before the first write (7), main-spec verification before moving `changeRoot` (8b), a re-check immediately before the move plus a post-move nest check (8c), and atomic stop conditions with per-change outcome tracking. The batch-operation cap does not apply and this matches anchor 5, including the guardrails checklist; anchor 4 would require missing checkpoints, which is not the case.

5 / 5

Progressive Disclosure

No bundle files exist, so the 377-line body is monolithic. Internal structure is good (numbered steps, headers, examples), but content that would naturally live in separate reference files — conflict-resolution examples and output templates — is inlined, and there is no overview-to-detail split. This fits anchor 3 (some structure, content that should be separate is inline) rather than 2, since the file is well organized and navigable.

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: concrete third-person statement of what the skill does, explicit 'Use when' guidance, and natural quoted trigger phrases including the CLI alias. The only gaps are single-action coverage and a few missing colloquial variations of the trigger terms.

DimensionReasoningScore

Specificity

"Archive multiple completed OpenSpec changes at once" names the domain and one concrete action, but the plural-request clause restates the same capability rather than listing several distinct actions (e.g., conflict detection or spec sync). This matches anchor 3 (domain plus 1-2 concrete actions) rather than 4, which requires a list of several specific actions.

3 / 5

Completeness

It explicitly answers both what ("Archive multiple completed OpenSpec changes at once") and when ("Use when archiving several parallel changes. Also use for a plural archive request - ...") with concrete trigger phrases, in third-person voice, matching anchor 5 exactly. Anchor 4 would require the 'when' to be less explicit, which is not the case here.

5 / 5

Trigger Term Quality

Natural quoted triggers "openspec bulk-archive", "opsx bulk-archive", "openspec archive all", and "openspec archive these changes" include the CLI alias and plural phrasings users would say. A few common variations (e.g., "batch archive", "archive all my changes") are missing, so it fits anchor 4 rather than the comprehensive coverage of anchor 5.

4 / 5

Distinctiveness Conflict Risk

A clear niche (bulk archiving of OpenSpec changes) with plural-scoped triggers, though "openspec archive all" and "openspec archive these changes" create minor overlap risk with a single-change archive skill. This is anchor 4 (mostly distinct, minor overlap with closely related skills) rather than 5.

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

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.