openspec-bulk-archive-change

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

Quality

72%

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

Quality

Content

77%

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

The content is highly actionable and clearly sequenced with strong validation checkpoints for a batch/destructive operation, earning top marks on actionability and workflow clarity. It loses ground on conciseness due to redundant output/example sections and on progressive disclosure because everything is inline with no split-out reference files.

Suggestions

Collapse the Output On Success / Partial / When No Changes sections into a single compact template with inline conditionals, and trim the Conflict Resolution Examples since step 5 already covers the same logic.

Consider extracting the large worked examples and output templates into a reference file under references/ (e.g., examples.md) to shorten the SKILL.md body and improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient and well-structured but includes redundancy: the Output On Success / Partial / When No Changes sections and the Conflict Resolution Examples restate logic already covered in the numbered steps, so it could be tightened to the level 3 'every token earns its place' bar.	2 / 3
Actionability	It provides fully concrete, executable guidance — `openspec list --json`, `openspec status --change "<name>" --json`, specific task-file parsing rules, and copy-ready bash (mkdir -p / mv to dated archive dirs) — matching the level 3 'fully executable, copy-paste ready' anchor.	3 / 3
Workflow Clarity	For this batch/destructive operation it lays out a clear numbered sequence with explicit validation checkpoints (batch status gathering, conflict detection, consolidated status table, a single confirmation) plus error-recovery feedback (fail that change but continue with others), satisfying the level 3 anchor.	3 / 3
Progressive Disclosure	No bundle files exist (references/, scripts/, assets/ are absent) and the skill is a single ~240-line inline document with worked examples and output templates that could be split out, fitting the level 2 'some structure but content that should be separate is inline' anchor rather than a cleanly split, well-signaled level 3.	2 / 3
	Total	10 / 12 Passed

Description

67%

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 clearly pairs a single concrete action with an explicit 'Use when' trigger, satisfying completeness, but it names only one action and uses a narrow set of trigger terms, leaving specificity, trigger coverage, and distinctiveness at the mid-level. It is competent but could name more actions and broader trigger phrasing.

Suggestions

Name additional concrete actions (e.g., detect spec conflicts, sync specs, resolve conflicts by checking the codebase) to raise specificity beyond the single 'archive' action.

Broaden trigger terms to natural phrasings users might actually say, such as 'bulk archive', 'batch archive', or 'archive several changes at once'.

Sharpen distinctiveness by referencing the openspec/change workflow context so it is clearly distinguished from a generic single-archive skill.

Dimension	Reasoning	Score
Specificity	The phrase 'Archive multiple completed changes at once' names one concrete action (batch archive) but does not list multiple distinct concrete actions, matching the 'names domain and some actions but not comprehensive' anchor rather than the 'multiple specific concrete actions' level 3.	2 / 3
Completeness	It explicitly states what it does ('Archive multiple completed changes at once') and gives an explicit 'Use when...' trigger ('Use when archiving several parallel changes'), satisfying the level 3 anchor for answering both what and when.	3 / 3
Trigger Term Quality	'Use when archiving several parallel changes' provides a natural trigger word (archiving) but misses common variations a user might say like 'bulk archive' or 'batch archive', fitting the 'some relevant keywords but missing common variations' anchor.	2 / 3
Distinctiveness Conflict Risk	'Archive... changes' is a specific niche but the description alone is generic enough to overlap with a single-change archive skill, matching the 'somewhat specific but could still overlap' anchor rather than a clearly distinct level 3.	2 / 3
	Total	9 / 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: Draculabo/AntigravityManager
Path: .agent/skills/openspec-bulk-archive-change/SKILL.md
Commit: de8d68d

Reviewed: about 11 hours 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.