openspec-bulk-archive-change

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

Quality

63%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

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

Quality

Content

63%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 content is a well-sequenced, actionable batch-archive workflow with strong validation and guardrails for a destructive operation. Its main weaknesses are redundant output templates, an under-specified spec-sync step, and no progressive disclosure to separate reference files despite the length.

Suggestions

Replace the vague 'openspec-sync-specs approach' reference in step 8a with concrete, executable sync commands or link to a dedicated reference file.

De-duplicate the step-9 summary example and the 'Output On Success/Partial/No Changes' templates into a single canonical output section.

Move the conflict-resolution worked examples and output templates into a references file (e.g., CONFLICTS.md) referenced one level deep from SKILL.md to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The body is mostly instructions and examples rather than concept-padding, but the step-9 summary overlaps with the 'Output On Success/Partial' templates and the two conflict examples restate step 5, so it could be tightened.	3 / 5
Actionability	It gives concrete commands (`openspec list --json`, `openspec status --change --json`, `mkdir -p`, `mv`), file paths, and parsing rules, but the spec-sync step defers to a vague 'openspec-sync-specs approach (agent-driven intelligent merge)' without executable commands.	4 / 5
Workflow Clarity	Nine well-sequenced steps include validation checkpoints (no-active-changes stop, conflict detection, user confirmation, per-change outcome tracking, guardrails), but it lacks an explicit validate->fix->retry loop and post-archive verification.	4 / 5
Progressive Disclosure	The body is well-structured with section headers and numbered steps, but at ~235 lines all content is inlined with no reference files or navigation, and the examples/output templates that could be split out remain inline.	3 / 5
	Total	14 / 20 Passed

Description

62%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 states both what and when with an explicit 'Use when' trigger, and targets a distinct niche. It is held back by single-action specificity, jargon-heavy trigger terms, and a 'when' clause that echoes the 'what' rather than broadening the trigger surface.

Suggestions

Add concrete synonyms/variations to the trigger (e.g., 'Use when archiving several parallel changes, cleaning up completed specs, or batching change archival').

Name the openspec context explicitly (e.g., 'Archive multiple completed openspec changes') to reduce overlap risk with generic archive skills.

Expand the 'what' with a second concrete action the skill performs (e.g., 'resolving spec conflicts and syncing deltas') to lift specificity.

Dimension	Reasoning	Score
Specificity	The phrase 'Archive multiple completed changes at once' names the domain (completed changes) and one concrete action (archive), but does not list several specific actions needed for a 4.	3 / 5
Completeness	It explicitly states both what ('Archive multiple completed changes at once') and when ('Use when archiving several parallel changes'), but the 'when' largely restates the 'what' rather than adding distinct trigger scenarios.	4 / 5
Trigger Term Quality	'Archive'/'archiving' are natural user terms, but 'parallel changes' and 'completed changes' are openspec jargon and no synonyms or variations are offered.	3 / 5
Distinctiveness Conflict Risk	Bulk archiving of changes is a clear niche with minimal conflict risk, though omitting 'openspec' leaves minor overlap risk with generic archive skills.	4 / 5
	Total	14 / 20 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: dwmkerr/livedown
Path: .claude/skills/openspec-bulk-archive-change/SKILL.md
Commit: db0bd53

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