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

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/openspec-bulk-archive-change/SKILL.md

Quality

Content

82%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 a well-structured, actionable workflow with strong validation for a batch/destructive operation and good organization. Its main weakness is mild verbosity in repeated examples and a partially-specified sync sub-step.

Suggestions

Tighten the duplicated conflict-resolution examples and consolidate the three output templates into one parameterized template to reduce token usage.

Inline or reference the concrete openspec-sync-specs steps instead of deferring to 'the openspec-sync-specs approach' so the sync step is fully executable.

Consider moving the detailed guardrail edge-cases (archive target exists, preserve .openspec.yaml) into a short checklist near the execute step for quicker reference.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient, dominated by concrete commands, tables, and step lists rather than concept explanations, though the repeated conflict-resolution examples and multiple output templates add minor length that could be trimmed.	4 / 5
Actionability	It provides concrete executable commands (openspec list/status --json, mkdir/mv) and specific file paths, but the spec-sync step defers to the 'openspec-sync-specs approach' as a hint rather than fully specified, leaving a minor gap.	4 / 5
Workflow Clarity	A clear 9-step sequence with explicit validation checkpoints (status gathering, conflict detection, user confirmation, outcome tracking) for a batch/destructive operation, including feedback loops and a guardrails checklist.	5 / 5
Progressive Disclosure	A single-file skill with no external bundle needed; it is well-organized into labeled sections (Steps, Conflict Resolution Examples, Output templates, Guardrails), which is sufficient structure for a self-contained skill.	5 / 5
	Total	18 / 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 concisely states what the skill does and when to use it, with natural trigger terms and a clear niche. It is solid but could enumerate more specific actions and add richer trigger variations.

Suggestions

List 1-2 more concrete actions (e.g., 'detects spec conflicts, syncs delta specs, moves change folders to dated archive dirs') to lift specificity.

Broaden trigger terms with synonyms users might say (e.g., 'bulk archive', 'archive finished changes', 'close completed changes').

Make the 'when' clause more specific, e.g., 'Use when archiving several completed openspec changes at once or resolving spec conflicts before archive.'

Dimension	Reasoning	Score
Specificity	Names the domain (archiving changes) and one concrete action ('Archive multiple completed changes at once') but does not list several specific actions, matching the 'names domain and 1-2 concrete actions' anchor.	3 / 5
Completeness	Provides a clear 'what' and an explicit 'when' trigger ('Use when archiving several parallel changes'), but the when clause is somewhat thin and could be more specific, matching the 'both present, when could be more explicit' anchor.	4 / 5
Trigger Term Quality	Includes relevant natural terms like 'archive' and 'parallel changes' but misses common synonyms and variations, fitting 'some relevant keywords but missing common variations'.	3 / 5
Distinctiveness Conflict Risk	The batch-archive niche for completed openspec changes is mostly distinct with only minor overlap risk against a single-archive skill, fitting 'mostly distinct; minor overlap risk'.	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: fengshao1227/ccg-workflow
Path: .agents/skills/openspec-bulk-archive-change/SKILL.md
Commit: cc8cc34

Reviewed: 1 day 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.