CtrlK
BlogDocsLog inGet started
Tessl Logo

sdd-archive

Archive a completed SDD change by syncing delta specs. Trigger: orchestrator launches archive after implementation and verification.

60

Quality

70%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./internal/assets/skills/sdd-archive/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

73%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 delivers an executable, well-validated archiving workflow with strong sequencing and clear shared-doc references. Its main weakness is repetition of the mechanical-copy and readback rules across multiple sections.

Suggestions

Consolidate the Mechanical Copy Contract and diff -r readback rule into a single authoritative section; have later steps and the Rules list reference it instead of restating the full rationale.

Move the detailed delta-spec merge algorithm and the historical malformed-nesting recovery block into a reference file to keep SKILL.md a lean overview.

DimensionReasoningScore

Conciseness

The body is mostly efficient and avoids basic-concept padding, but the Mechanical Copy Contract, the diff -r readback rule, and the shell-only rule are each restated multiple times (contract section, inline code comments, Step 4, and the Rules list), which could be tightened.

3 / 5

Actionability

The bash blocks (cp -R/mktemp/diff -r/git mv with traps and status handling) are copy-paste ready and executable, but the delta-spec merge logic is presented as a structured outline ("FOR EACH SECTION...") rather than literal executable code.

4 / 5

Workflow Clarity

A clear six-step sequence with explicit validation checkpoints (Task Completion Gate, MANDATORY diff -r readback, archive readiness), feedback loops (STOP and return blocked), and a Step 4 checklist for a destructive/batch operation.

5 / 5

Progressive Disclosure

Good section structure with clearly signaled, one-level-deep references to shared docs ("Follow Section B/C from skills/_shared/sdd-phase-common.md"); no bundle files exist, and some inline blocks (merge algorithm, historical recovery) could be split into reference files.

4 / 5

Total

16

/

20

Passed

Description

66%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 clearly answers what and when for a tightly scoped, low-conflict SDD archiving niche, with an explicit trigger clause. It is slightly held back by jargon-heavy trigger phrasing and a non-exhaustive action list.

Suggestions

Add a couple of natural-language trigger synonyms (e.g., "Use when finalizing/closing an SDD change") so the trigger phrase reads less like internal orchestration jargon.

Expand the action list to surface the other concrete archive operations (merge delta specs into main specs, move the change folder to the archive, persist the archive report) for fuller capability coverage.

DimensionReasoningScore

Specificity

"Archive a completed SDD change by syncing delta specs" names the domain and two concrete actions (archiving, syncing delta specs) but does not enumerate the full set of archive operations (spec merge, folder move, report persist).

3 / 5

Completeness

It states both what ("Archive a completed SDD change by syncing delta specs") and when (explicit "Trigger:" clause tied to implementation and verification), but the trigger is framed for an orchestrator rather than a concrete user-facing invocation phrase.

4 / 5

Trigger Term Quality

"Trigger: orchestrator launches archive after implementation and verification" supplies relevant orchestration keywords but leans on technical jargon (SDD, orchestrator) rather than natural synonyms a caller would vary.

3 / 5

Distinctiveness Conflict Risk

The SDD-archive niche is narrowly scoped and delegate-only, so the description is clearly distinguishable from other skills with minimal overlap risk.

5 / 5

Total

15

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_field

'metadata' should map string keys to string values

Warning

Total

15

/

16

Passed

Repository
Gentleman-Programming/gentle-ai
Reviewed

Table of Contents

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.