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".
79
74%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./ywai/skills/sdd-archive/SKILL.mdQuality
Discovery
72%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 excels at trigger term coverage with bilingual support and command patterns, making it highly discoverable. However, it lacks specificity about what the skill actually does - terms like 'delta specs' and 'main specs' are domain-specific jargon that aren't explained. The description would benefit from clarifying the concrete actions and outcomes.
Suggestions
Expand the capability description to explain what 'delta specs' and 'main specs' are, e.g., 'Merges incremental specification changes into the primary specification document and archives the completed change record.'
Add concrete actions beyond 'sync' and 'archive', such as what files are modified, what validation occurs, or what the end state looks like.
| 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 | Has a 'Trigger:' clause which serves as explicit trigger guidance, but the 'what' portion is weak - it doesn't clearly explain what syncing delta specs means or what a 'completed change' represents in this context. | 2 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms including English and Spanish variations ('archive', 'archivar', 'close change', 'cerrar cambio'), command patterns ('/sdd:archive'), and contextual terms ('merge specs', 'finalizar'). | 3 / 3 |
Distinctiveness Conflict Risk | Very distinct niche with specific terminology ('delta specs', 'sdd archive') and unique command patterns that are unlikely to conflict with other skills. The domain-specific language creates clear boundaries. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
77%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-structured archiving skill with excellent workflow clarity and actionability. The 10-step process with explicit validation gates and comprehensive error recovery makes it highly reliable for complex operations. However, the content is somewhat verbose with repeated mode-specific patterns and inline templates that could be extracted for better token efficiency.
Suggestions
Extract the markdown templates (lessons learned, changelog entry, archive summary) to a separate TEMPLATES.md file and reference them, reducing inline verbosity
Consider consolidating the mode-specific instructions (engram/openspec/none) into a single table or decision tree at the start rather than repeating the pattern in each step
| 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 structures could be more compact while maintaining clarity. | 2 / 3 |
Actionability | Provides concrete, executable guidance throughout: specific file paths, exact commands (mem_search, mem_save), complete markdown templates, and precise folder structures. The merge logic and verification checklists are copy-paste ready. | 3 / 3 |
Workflow Clarity | Excellent 10-step workflow with explicit validation checkpoints (Step 1 confirms readiness, Step 9 verification checklist). Includes clear error recovery table with specific actions for each failure scenario, and explicit blocking conditions for CRITICAL issues. | 3 / 3 |
Progressive Disclosure | References external files appropriately (persistence-contract.md, engram-convention.md, openspec-convention.md), but the main content is quite long with detailed templates inline. Some templates (lessons learned, changelog, archive summary) could be extracted to separate reference files. | 2 / 3 |
Total | 10 / 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 | |
- Repository
- Yoizen/dev-ai-workflow
- Commit
d9bf9a4
- 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.