openspec-bulk-archive-change

Archive multiple completed changes at once. Use when archiving several parallel changes.

Quality

62%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/openspec-bulk-archive-change/SKILL.md

Quality

Content

50%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A detailed, well-sequenced batch workflow with genuinely concrete commands, but it is held at mid-tier across the board by redundancy, a vaguely specified spec-sync step, and a lack of validation feedback loops or file-level progressive disclosure.

Suggestions

Replace the vague 'Use the openspec-sync-specs approach' in step 8a with the concrete commands or exact merge procedure so the core sync action is executable as written.

Add an explicit validation checkpoint around the destructive archive move (e.g. check the archive target does not pre-exist, then verify the move succeeded before marking Success) to satisfy the batch/destructive feedback-loop bar.

De-duplicate the conflict-resolution material (step 5 vs the 'Conflict Resolution Examples' section) and consolidate the four overlapping output templates into one parameterized template to tighten conciseness.

Dimension	Reasoning	Score
Conciseness	It avoids explaining concepts Claude already knows, but the conflict-resolution logic is restated in step 5 and again in 'Conflict Resolution Examples', and four overlapping output templates (step 9, On Success, Partial Success, No Changes) plus a repeated date-prefix rule add redundancy that could be tightened.	2 / 3
Actionability	Concrete openspec commands, exact JSON field paths, and a real mkdir/mv archive step are strong, but the core spec-sync action is delegated vaguely ('Use the openspec-sync-specs approach (agent-driven intelligent merge)') rather than given as an executable command, leaving a key detail incomplete.	2 / 3
Workflow Clarity	Nine steps are clearly sequenced with a confirmation checkpoint and outcome tracking, but the destructive batch mv-to-archive has no explicit pre-existence check or post-move verification feedback loop, so the batch/destructive validation cap applies.	2 / 3
Progressive Disclosure	The body is well-sectioned (numbered steps, Guardrails, examples, templates) rather than a disorganized wall, but it is a monolithic ~250-line file with no bundle references and content (conflict examples, output templates) that could be split out is kept inline.	2 / 3
	Total	8 / 12 Passed

Description

75%

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 concise, complete description with an explicit 'Use when' trigger and a clear niche. It is held back from the top tier only by jargon-leaning trigger terms and a single-action specificity profile.

Dimension	Reasoning	Score
Specificity	Names a concrete action ('Archive multiple completed changes at once') over a clear domain, but it is a single repeated action rather than the multiple distinct concrete actions (e.g. extract/fill/merge) that anchor a 3.	2 / 3
Completeness	Explicitly states what it does ('Archive multiple completed changes at once') and when to use it ('Use when archiving several parallel changes'), satisfying both halves with an explicit trigger clause.	3 / 3
Trigger Term Quality	'archive'/'archiving' are natural user terms, but 'parallel changes' is OpenSpec-internal jargon and common variations (e.g. 'clean up', 'completed changes') are thin, so it matches 'some relevant keywords but missing common variations'.	2 / 3
Distinctiveness Conflict Risk	The bulk/parallel framing carves a clear niche distinct from a singular archive skill, and the trigger is specific enough to be unlikely to fire for unrelated skills.	3 / 3
	Total	10 / 12 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: Fission-AI/OpenSpec
Path: skills/openspec-bulk-archive-change/SKILL.md
Commit: 6a5171e

Reviewed: 5 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.