openspec-bulk-archive-change

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

Quality

80%

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

77%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 highly actionable with executable commands and strong workflow clarity including validation checkpoints for a destructive batch operation. Its main weaknesses are verbosity from a redundant Guardrails section and a monolithic inline structure with no progressive disclosure.

Suggestions

Collapse the Guardrails section into the relevant steps or trim it to non-duplicative items to remove repetition and recover token budget.

Move the Conflict Resolution Examples and detailed archive-input/context-handling rules into reference files linked from the main steps to introduce one-level-deep progressive disclosure.

Dimension	Reasoning	Score
Conciseness	Mostly efficient procedural prose, but the ~330-line body repeats itself via a long Guardrails section that restates earlier steps, adding padding that could be trimmed.	3 / 5
Actionability	Provides fully executable commands with concrete flags, explicit JSON field names, and copy-paste-ready shell snippets (openspec list/status/instructions, mkdir -p, mv).	5 / 5
Workflow Clarity	For this destructive batch operation the steps are clearly sequenced with explicit validation (verify main specs before moving changeRoot), atomic stop conditions, and feedback loops for error recovery.	5 / 5
Progressive Disclosure	No bundle/reference files exist, so the entire ~330-line procedure is inlined; numbered steps and headers give some structure, but content that could be split out (e.g., conflict-resolution examples, archive input handling) has no one-level-deep references.	3 / 5
	Total	16 / 20 Passed

Description

82%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 is clear and complete, explicitly stating both what the skill does and when to use it with a concrete trigger phrase. It is slightly thin on enumerating multiple concrete actions and could use a couple more natural synonyms.

Suggestions

Add one or two more concrete actions (e.g., 'detect and resolve spec conflicts, then move change directories to archive') to raise specificity.

Include natural synonyms users might say, such as 'bulk' or 'clean up completed changes'.

Dimension	Reasoning	Score
Specificity	Names the domain and one concrete action ('Archive multiple completed changes at once') but offers only a single action rather than several specific concrete actions.	3 / 5
Completeness	Explicitly answers both what ('Archive multiple completed changes at once') and when ('Use when archiving several parallel changes') with a concrete trigger phrase.	5 / 5
Trigger Term Quality	Natural terms 'archive', 'parallel changes', and 'completed changes' give good keyword coverage, though common synonyms like 'bulk' or 'clean up' are absent.	4 / 5
Distinctiveness Conflict Risk	Targets a clear niche (bulk archiving of several parallel OpenSpec changes) with distinct triggers and minimal overlap with single-archive skills.	5 / 5
	Total	17 / 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: Fission-AI/OpenSpec
Path: skills/openspec-bulk-archive-change/SKILL.md
Commit: 6926ccb

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