sdd-init
Bootstrap the SDD structure in any project. Detects stack, conventions, and initializes the active persistence backend. Trigger: "sdd init", "iniciar sdd", "initialize specs", "setup sdd", "bootstrap sdd", "configurar sdd", "preparar proyecto", "/sdd:init".
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 is a well-structured skill description with excellent trigger term coverage in multiple languages and a clear 'Trigger:' clause. The main weakness is that the capabilities could be more specific about what exactly gets created or configured during the bootstrap process. The description uses proper third-person voice throughout.
Suggestions
Expand the capabilities section to specify what artifacts are created (e.g., 'Creates spec files, configures persistence layer, generates project structure')
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (SDD structure) and some actions ('Detects stack, conventions, initializes the active persistence backend'), but lacks comprehensive detail about what specific outputs or artifacts are created. | 2 / 3 |
Completeness | Clearly answers both what ('Bootstrap the SDD structure, detects stack, conventions, initializes persistence backend') and when (explicit 'Trigger:' clause with multiple specific phrases). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms including variations in English and Spanish ('sdd init', 'iniciar sdd', 'initialize specs', 'setup sdd', 'bootstrap sdd', 'configurar sdd', 'preparar proyecto', '/sdd:init'). | 3 / 3 |
Distinctiveness Conflict Risk | Very specific niche with 'SDD' as a distinct identifier and unique trigger terms like '/sdd:init' 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-structured skill with clear multi-step workflows, appropriate external references, and concrete actionable guidance. The main weakness is some verbosity in the output templates and slight redundancy across mode-specific sections. The skill effectively handles edge cases and provides clear next steps.
Suggestions
Consolidate the three output templates into a single template with mode-specific variables to reduce redundancy
Show the structured envelope format (status, executive_summary, artifacts, next_recommended, risks) explicitly since it's required but not demonstrated
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some redundancy (e.g., repeating mode-specific instructions that could be consolidated, verbose output templates). The structured envelope requirement at the end is mentioned but not shown, adding ambiguity. | 2 / 3 |
Actionability | Provides concrete directory structures, specific file paths, exact config file names, and clear detection targets (package.json, go.mod, etc.). The step-by-step process with mode-specific actions is executable and specific. | 3 / 3 |
Workflow Clarity | Clear 4-step sequence with explicit handling for edge cases (existing installation, corruption, schema migration). The decision table for existing installations provides excellent validation checkpoints and error recovery paths. | 3 / 3 |
Progressive Disclosure | Appropriately references external files (persistence-contract.md, engram-convention.md, openspec-convention.md) for detailed conventions while keeping the main skill focused on the init workflow. References are one level deep and clearly signaled. | 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.