sdd-archive

Archive an SDD change honestly by syncing delta specs and preserving its artifacts. Trigger: orchestrator launches archive.

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 ./internal/assets/skills/sdd-archive/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.

An exemplary operational skill body: highly executable shell workflows with rigorous validation and feedback loops for a destructive filesystem operation, with only moderate verbosity from repeated safety mantras.

Suggestions

Consolidate the repeated mechanical-copy / empty-diff mantra into the single Mechanical Copy Contract section and reference it from the steps and Rules instead of restating it verbatim three to five times.

Tighten the Final-State Authority section by leading with the ranked source list and trimming the philosophical framing about stale claims.

Consider extracting the long bash move/recovery scripts into a referenced script file under scripts/ so the SKILL.md body stays a lean overview.

Dimension	Reasoning	Score
Conciseness	Most content is concrete and operational, but the mechanical-copy / "NEVER Read→Write" / empty-diff-is-the-only-passing-evidence mantra is repeated verbatim across the Mechanical Copy Contract, each step, and the Rules section, and the Final-State Authority section is somewhat philosophical, so it could be tightened.	3 / 5
Actionability	Fully executable, copy-paste-ready bash with mktemp/EXIT traps, atomic compose-and-mv, git mv with guarded plain-mv fallback, destination-collision checks, and a native `sdd-archive-compose` invocation covering the main-spec-exists and main-spec-absent cases.	5 / 5
Workflow Clarity	A clear six-step sequence (Load → Sync → Move → Verify → Persist → Return) with explicit MANDATORY `diff -r` validation checkpoints, blocked-failure feedback loops (nonzero exit → STOP, no manual retry), and a Step 4 checklist; the destructive-operation validation cap does not apply because validation is present and rigorous.	5 / 5
Progressive Disclosure	Structure is good with well-signaled one-level-deep references to shared docs (sdd-phase-common.md Sections A–D, sdd-status-contract.md, openspec-convention.md); no bundle files exist locally and the operational content is appropriately inline, though nothing is split into this skill's own reference files.	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.

A focused, third-person description that states both what the skill does and an explicit trigger, but the trigger is orchestrator-internal rather than natural user language and the action list is not comprehensive.

Suggestions

Add a concrete user-facing trigger phrase (e.g., "Use when the orchestrator needs to close/archive an SDD change") alongside the internal "Trigger:" clause.

Expand the action list beyond "syncing delta specs" and "preserving artifacts" to name the full archive operation (e.g., merge deltas into main specs, move the change folder to a dated archive, emit the archive report).

Include common synonyms/extensions ("archive", "close", "sync specs") so the trigger language matches what an orchestrator would naturally say.

Dimension	Reasoning	Score
Specificity	Names the SDD-change domain and two concrete actions ("syncing delta specs", "preserving its artifacts") but does not enumerate the full set of archive operations, so it is not comprehensive enough for a 4.	3 / 5
Completeness	It gives a clear "what" (archive by syncing delta specs and preserving artifacts) and an explicit "Trigger:" clause for "when", but the trigger is mechanical/orchestrator-driven rather than concrete user-facing trigger phrases, stopping short of a 5.	4 / 5
Trigger Term Quality	Relevant keywords ("archive", "SDD change") appear, but the trigger "orchestrator launches archive" is internal/jargon rather than natural user phrasing, and common synonyms are missing.	3 / 5
Distinctiveness Conflict Risk	The SDD archive niche is clear and unlikely to fire for unrelated skills, but it shares the broader SDD-change surface with sibling phase skills (apply/verify), creating minor overlap risk rather than the minimal risk of a 5.	4 / 5
	Total	14 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_field	'metadata' should map string keys to string values	Warning

	Total	15 / 16 Passed

Repository: Gentleman-Programming/gentle-ai
Path: internal/assets/skills/sdd-archive/SKILL.md
Commit: bb38b08

Reviewed: 10 days 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.