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.

59

Quality

68%

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

62%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content delivers a well-gated, clearly sequenced archive workflow with strong validation and feedback loops. Its weaknesses are repeated policy restatements, pseudocode/placeholder merge logic with core mechanics deferred to un-bundled references, and lack of file-based progressive disclosure.

Suggestions

Consolidate the stale-checkbox reconciliation policy into one authoritative section and reference it elsewhere instead of restating it four times.

Extract the delta-merge algorithm and the gate policies into bundled reference files (e.g., references/merge-rules.md) so SKILL.md stays a lean overview.

Replace the placeholder pseudocode merge block with concrete, copy-ready commands or a runnable script under scripts/ for the openspec/hybrid path.

DimensionReasoningScore

Conciseness

The body is mostly lean procedural instruction, but the stale-checkbox policy is restated across the Task Completion Gate, Strict-vs-OpenSpec Archive Policy, Step 4, and Rules sections, and the Language Domain Contract is tangential to the archive task.

2 / 3

Actionability

Concrete file paths and move operations are given, but the merge logic is pseudocode with placeholders and core retrieval/persistence mechanics are deferred to un-bundled shared docs (sdd-phase-common.md Sections A-D).

2 / 3

Workflow Clarity

A clear Step 1-6 sequence is gated by explicit checkpoints (Review Receipt Gate, Task Completion Gate, Action Context Guard) with a verification checklist and blocked-return feedback loops for error recovery.

3 / 3

Progressive Disclosure

References to shared docs are clearly signaled one level deep ('Follow Section B from sdd-phase-common.md'), but no bundle files exist and the ~200-line body keeps the merge algorithm and policy gates inline rather than splitting them out.

2 / 3

Total

9

/

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 is clear and complete, explicitly stating both the action and an explicit trigger, with a well-scoped niche. It is somewhat under-specified on the breadth of concrete archive actions and uses system rather than natural-user trigger language.

Suggestions

Expand the action list to reflect the full archive scope (e.g., '...sync delta specs into main specs, move the change folder to archive, and persist the archive report').

Add natural-language trigger terms a user might say (e.g., 'archive', 'finalize', 'close out an SDD change') alongside the orchestrator trigger.

DimensionReasoningScore

Specificity

Names the SDD-archiving domain and concrete actions ('Archive a completed SDD change by syncing delta specs'), but lists only sync/archive rather than the full scope (move, verify, persist report) the body later reveals.

2 / 3

Completeness

Clearly answers what ('Archive a completed SDD change by syncing delta specs') and when via an explicit 'Trigger: orchestrator launches archive after implementation and verification' clause, satisfying both halves.

3 / 3

Trigger Term Quality

The explicit 'Trigger:' clause includes the relevant term 'archive', but the trigger is framed as system/orchestrator language ('orchestrator launches archive after implementation and verification') rather than broad natural user phrasings.

2 / 3

Distinctiveness Conflict Risk

Occupies a clear niche (SDD change archiving) with a distinct system trigger, making it unlikely to fire for unrelated skills.

3 / 3

Total

10

/

12

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.