openspec-bulk-archive-change

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

Quality

76%

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 ./eval/local/skills/benchmarks/dependency/openspec/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.

This is a highly actionable, well-sequenced batch workflow with strong validation gates and concrete commands. Its weaknesses are token redundancy from repeated templates and a monolithic structure with no progressive disclosure to supporting files.

Suggestions

Collapse the "Output On Success", "Output On Partial Success", and step-9 summary into a single parameterized template to remove redundancy and improve conciseness.

Move the "Conflict Resolution Examples" block and the output templates into a reference file (e.g. references/examples.md) referenced one level deep, reducing the main body toward an overview.

Tighten the Guardrails list by dropping items that merely restate instructions already embedded in the numbered steps.

Dimension	Reasoning	Score
Conciseness	The body is procedural without concept-padding, but the success/partial/no-changes output templates and the Guardrails section restate content already shown in the step-by-step examples, leaving room to tighten.	2 / 3
Actionability	It provides concrete executable commands (openspec list/status --json, mkdir -p, mv), exact file paths, and copy-paste-ready examples for the archive operation and conflict resolution.	3 / 3
Workflow Clarity	The nine steps are clearly sequenced with explicit validation checkpoints (artifact/task status, conflict detection, codebase verification) and a user-confirmation gate before the destructive move, plus per-change success/skip/fail tracking.	3 / 3
Progressive Disclosure	The skill is well-organized into sections but is a ~235-line monolithic SKILL.md with no bundle files and no one-level-deep references; conflict-resolution examples and output templates are inline material that could live in separate reference files.	2 / 3
	Total	10 / 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.

The description cleanly answers both what it does and when to use it with an explicit trigger and a distinctive niche. It is held back from the top by a single-action scope and narrow trigger-term coverage.

Suggestions

Broaden trigger coverage with natural variations a user might say, e.g. "Use when archiving several parallel changes, cleaning up completed changes in bulk, or batching change archives."

Consider naming one or two additional concrete capabilities (e.g. detecting and resolving spec conflicts across archived changes) to lift specificity to the top anchor.

Dimension	Reasoning	Score
Specificity	"Archive multiple completed changes at once" names a concrete action and domain, but lists only a single action rather than multiple specific concrete actions, so it falls short of the top anchor.	2 / 3
Completeness	It explicitly states what ("Archive multiple completed changes at once") and an explicit "Use when" trigger, satisfying both halves of the completeness anchor.	3 / 3
Trigger Term Quality	"Use when archiving several parallel changes" gives a natural trigger phrase, but coverage is narrow with limited common variation rather than broad keyword coverage.	2 / 3
Distinctiveness Conflict Risk	The bulk/"several parallel changes" framing carves a clear niche distinct from single-change archiving, making accidental triggering of the wrong skill unlikely.	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: rpamis/comet
Path: eval/local/skills/benchmarks/dependency/openspec/openspec-bulk-archive-change/SKILL.md
Commit: 2945693

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