sdd-archive
Sync delta specs to main specs and archive a completed change. Trigger: "archive", "archivar", "close change", "cerrar cambio", "sdd archive", "finalizar", "merge specs", "/sdd:archive".
89
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
89%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This description excels at trigger term coverage with bilingual support and explicit command triggers, making it highly discoverable. The 'when' guidance is explicit and clear. However, the 'what' portion could be more specific about the concrete actions performed during the sync and archive process.
Suggestions
Expand the capability description to explain what 'sync delta specs to main specs' means in concrete terms (e.g., 'Merges approved changes from delta specification files into the main specification documents')
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (delta specs, main specs) and some actions (sync, archive), but lacks comprehensive detail about what 'sync delta specs' or 'archive a completed change' actually entails in concrete terms. | 2 / 3 |
Completeness | Clearly answers both what ('Sync delta specs to main specs and archive a completed change') and when ('Trigger:' followed by explicit trigger terms), providing explicit guidance on when Claude should select this skill. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms including both English and Spanish variations ('archive', 'archivar', 'close change', 'cerrar cambio'), plus command-style triggers ('/sdd:archive', 'sdd archive', 'merge specs', 'finalizar'). | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with domain-specific terminology ('delta specs', 'main specs', 'sdd archive') and unique command triggers that are unlikely to conflict with other skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-crafted skill for a complex archiving workflow that handles three persistence modes. Its strengths are exceptional workflow clarity with explicit validation gates, highly actionable templates and commands, and good progressive disclosure to shared conventions. The main weakness is moderate verbosity from repeating mode-specific instructions across multiple steps, though this redundancy aids clarity for a complex multi-mode operation.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is comprehensive but includes some redundancy across modes (engram/openspec/none patterns repeated in multiple steps). Some sections like the detailed merge logic and template formats could be more condensed, though most content is necessary for the complex multi-mode workflow. | 2 / 3 |
Actionability | Provides concrete, executable guidance throughout: specific file paths, exact mem_search queries, complete markdown templates for outputs, detailed merge logic with pseudocode, and precise folder naming conventions. Copy-paste ready commands and clear output formats. | 3 / 3 |
Workflow Clarity | Excellent 10-step workflow with explicit validation checkpoints (Step 1 confirms readiness, Step 9 has verification checklist). Clear error recovery table handles edge cases. Feedback loops present (refuse if FAIL, warn on destructive merges). Proper sequencing with dependencies clearly stated. | 3 / 3 |
Progressive Disclosure | Well-structured with clear references to shared contracts (persistence-contract.md, engram-convention.md, openspec-convention.md) that are one level deep. Content is appropriately organized with collapsible-style sections, tables for quick reference, and templates separated from logic. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_field | 'metadata' should map string keys to string values | Warning |
Total | 10 / 11 Passed | |
- 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.