openspec-bulk-archive-change

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

Quality

66%

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 ./.claude/skills/openspec-bulk-archive-change/SKILL.md

Quality

Content

70%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 clearly sequenced, validation-rich batch workflow with concrete commands and strong error recovery, weakened by redundant output templates and inlined example walkthroughs that progressive disclosure would move to separate reference files.

Suggestions

Collapse the three standalone "Output On..." templates into a single canonical example referenced from Step 9 to remove duplication.

Move the detailed "Conflict Resolution Examples" walkthroughs into a references/ file and link to them from Step 5, keeping only the resolution rules inline.

Replace the "Use the openspec-sync-specs approach" pointer in Step 8a with a concrete, self-contained sync procedure or an explicit link so the archive step is fully executable without another skill.

Dimension	Reasoning	Score
Conciseness	Mostly substantive workflow detail, but the standalone "Output On Success / Partial Success / No Changes" templates duplicate Step 9's example and the "Conflict Resolution Examples" restate Step 5's logic, adding padding that could be trimmed.	3 / 5
Actionability	Provides concrete executable commands (openspec list/status --json, mkdir -p, mv) and specific parse rules, but the core spec-sync step defers to "the openspec-sync-specs approach" rather than giving copy-paste-ready code.	4 / 5
Workflow Clarity	Nine well-sequenced steps with explicit validation checkpoints (status gathering in Step 3, warnings in Step 6, user confirmation gate in Step 7), per-change outcome tracking, a Guardrails checklist, and a fail-one-continue-others recovery loop; the batch/destructive cap does not apply because validation is present.	5 / 5
Progressive Disclosure	The body is organized with clear section headers but no bundle files or external references are used, and the full worked conflict-resolution examples plus three redundant output templates are inlined rather than split into a reference file.	3 / 5
	Total	15 / 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 what and when in third person and is reasonably distinct, but it is thin on specificity and trigger coverage, naming one action and one trigger scenario rather than the skill's full batch-archive capability.

Suggestions

Expand the what clause to list the key actions performed, e.g. "Archive multiple completed changes at once, syncing delta specs and resolving capability conflicts before moving each change to the archive."

Broaden the when clause with additional natural triggers, e.g. "Use when archiving several parallel changes, batch-archiving completed changes, or cleaning up multiple finished openspec changes."

Dimension	Reasoning	Score
Specificity	Names the domain and one concrete action ("Archive multiple completed changes at once") but does not enumerate the several specific actions the skill actually performs (sync specs, resolve conflicts, move to archive).	3 / 5
Completeness	Explicitly answers both what ("Archive multiple completed changes at once") and when ("Use when archiving several parallel changes"), though the when clause covers only one trigger situation rather than multiple concrete ones.	4 / 5
Trigger Term Quality	Contains the natural phrase "Use when archiving several parallel changes" but offers only a single trigger scenario, missing common variations like "batch archive" or "completed changes."	3 / 5
Distinctiveness Conflict Risk	The "multiple/parallel/batch" framing carves a distinct niche away from a single-change archive skill, with only minor overlap risk against closely related openspec 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: PBH-BTN/PeerBanHelper
Path: .claude/skills/openspec-bulk-archive-change/SKILL.md
Commit: f8e9b1b

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