openspec-bulk-archive-change

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

Quality

71%

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

81%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 provides a well-sequenced, validated batch workflow with concrete commands and clear status/confirmation gates. It is efficient and actionable, with only minor conciseness and organization improvements available.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient and action-oriented, but the Guardrails section restates steps already covered and the conflict-resolution examples add padding, keeping it at anchor 4 rather than 5.	4 / 5
Actionability	Concrete commands (`openspec list --json`, `openspec status --change`, mkdir/mv) and specific parsing details are provided, but a few steps like "Use the openspec-sync-specs approach" are descriptive rather than fully executable, matching anchor 4.	4 / 5
Workflow Clarity	A clear 9-step sequence includes explicit validation checkpoints (status gathering, conflict detection, AskUserQuestion confirmation gates, per-change outcome tracking) with feedback loops for a batch operation, matching anchor 5.	5 / 5
Progressive Disclosure	The skill is a single self-contained file with well-organized sections and no nested references, but at ~235 lines content such as the conflict-resolution examples could be split out, sitting at anchor 4 rather than 5.	4 / 5
	Total	17 / 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 the skill does and when to use it with an explicit trigger clause, achieving solid completeness and distinctiveness. It could be stronger with more specific action enumeration and broader natural-term coverage.

Suggestions

List 2-3 concrete actions (e.g., "detect spec conflicts, sync delta specs, move changes to archive") to raise specificity from 3 to 4-5.

Broaden trigger terms with natural synonyms users might say, such as "bulk archive", "archive completed changes", or "clean up finished changes".

Make the "when" clause more specific than "several parallel changes" by naming the openspec workflow context explicitly.

Dimension	Reasoning	Score
Specificity	"Archive multiple completed changes at once" names the domain and one concrete batch action, but does not enumerate several specific actions, matching anchor 3.	3 / 5
Completeness	Both a clear "what" ("Archive multiple completed changes at once") and an explicit "when" ("Use when archiving several parallel changes") are present, but the trigger phrasing is generic rather than comprehensive, so it sits at anchor 4.	4 / 5
Trigger Term Quality	Terms like "Archive", "changes", and "archiving several parallel changes" are relevant but lack common synonyms or variations, matching anchor 3 rather than the broader coverage of anchor 4.	3 / 5
Distinctiveness Conflict Risk	The batch-archiving niche with a "several parallel changes" trigger is mostly distinct, with only minor overlap risk against a single-change archive skill, matching anchor 4.	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: rpamis/comet
Path: eval/local/skills/benchmarks/dependency/openspec/openspec-bulk-archive-change/SKILL.md
Commit: 0c7f87b

Reviewed: ~16 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.