openspec-bulk-archive-change

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

Quality

70%

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

65%

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

A thorough, highly actionable batch-archive workflow with concrete commands and clear sequencing, but it is monolithic (no referenced detail files) and lacks a post-archive verification loop for a destructive batch operation. Splitting the examples/templates into reference files and adding a verify step would raise the weaker dimensions.

Suggestions

Add a post-archive verification checkpoint (e.g., re-run `openspec list --json` to confirm archived changes are gone and check that synced specs landed) to close the feedback loop for this destructive batch operation.

Move the 'Conflict Resolution Examples' and 'Output' templates into a separate reference file (e.g., references/examples.md) referenced from SKILL.md to improve progressive disclosure and reduce duplication.

Replace the vague step 8a ('Use the openspec-sync-specs approach') with concrete sync commands or a direct link to the referenced skill so the core spec-sync step is executable rather than descriptive.

Dimension	Reasoning	Score
Conciseness	The body is mostly procedural instruction without explaining concepts Claude already knows, but the standalone 'Conflict Resolution Examples' and multiple 'Output' templates duplicate logic already covered in the numbered steps, so it could be tightened.	2 / 3
Actionability	It provides copy-paste-ready commands (`openspec list --json`, `openspec status --change "<name>" --json`, `mkdir -p` / `mv` archive commands) and concrete file paths throughout, with specific examples for each phase.	3 / 3
Workflow Clarity	The 9-step sequence is clear with pre-archive status and conflict checks, but this is a batch/destructive operation (moving directories) with no post-archive verification or validate-fix-retry feedback loop, capping it at 2 per the rubric note.	2 / 3
Progressive Disclosure	There are no bundle files and all ~250 lines live inline in SKILL.md; the detailed conflict-resolution examples and output templates that could be split out are inline, fitting the 'content that should be separate is inline' anchor.	2 / 3
	Total	9 / 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, third-person description that clearly covers both what the skill does and when to trigger it within a well-scoped niche. It could be improved by enumerating more concrete actions and adding a few more natural trigger variations.

Suggestions

Add one or two more concrete actions (e.g., resolving spec conflicts, syncing delta specs) to lift specificity from a single action to multiple specific capabilities.

Expand trigger terms with common phrasings like 'bulk archive' or 'batch archive completed changes' for broader natural-language coverage.

Dimension	Reasoning	Score
Specificity	"Archive multiple completed changes at once" names the domain and a concrete batch action, but lists only one action rather than multiple distinct concrete capabilities, matching the 'names domain and some actions' anchor.	2 / 3
Completeness	It 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.	3 / 3
Trigger Term Quality	"Use when archiving several parallel changes" provides natural terms (archiving, parallel changes) but misses common variations like 'bulk archive' or 'batch archive', fitting the 'some relevant keywords but missing common variations' anchor.	2 / 3
Distinctiveness Conflict Risk	The niche is narrow and specific to archiving completed openspec changes in batch, with distinct triggers 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: PBH-BTN/PeerBanHelper
Path: .claude/skills/openspec-bulk-archive-change/SKILL.md
Commit: be872c1

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.