Ingeniero de Sistemas de Andru.ia. Diseña, redacta y despliega nuevas habilidades (skills) dentro del repositorio siguiendo el Estándar de Diamante.
43
30%
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 ./skills/10-andruia-skill-smith/SKILL.mdQuality
Discovery
32%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 provides a basic understanding of the skill's purpose (creating skills following a standard) but lacks explicit trigger guidance and comprehensive action details. The use of internal terminology ('Estándar de Diamante') without explanation and the absence of a 'Use when...' clause significantly weakens its effectiveness for skill selection.
Suggestions
Add an explicit 'Use when...' clause with trigger terms like 'crear skill', 'nueva habilidad', 'agregar capacidad al agente', 'skill markdown'
Expand the specific actions beyond 'diseña, redacta y despliega' to include concrete operations like 'creates YAML frontmatter', 'defines triggers', 'validates skill format'
Either explain what 'Estándar de Diamante' means or replace with user-facing terminology that would naturally appear in requests
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (skills/habilidades) and lists some actions ('Diseña, redacta y despliega'), but lacks comprehensive detail about what specific operations are performed or what the 'Estándar de Diamante' entails. | 2 / 3 |
Completeness | Describes what it does (designs, writes, deploys skills) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. Per rubric guidelines, missing explicit trigger guidance caps this at 2, but the 'what' is also weak, warranting a 1. | 1 / 3 |
Trigger Term Quality | Includes some relevant terms like 'habilidades', 'skills', and 'repositorio', but misses common variations users might say (e.g., 'crear skill', 'nueva habilidad', 'agregar capacidad'). The term 'Estándar de Diamante' is internal jargon unlikely to be used by users. | 2 / 3 |
Distinctiveness Conflict Risk | The mention of 'skills' and 'Estándar de Diamante' provides some specificity, but 'Ingeniero de Sistemas' is generic and could overlap with other system engineering or development skills. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
27%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides a high-level workflow for creating skills but lacks the concrete, executable guidance needed for actionability. It references standards and structures without providing templates, examples, or links to documentation. The workflow phases are clear but missing validation steps for file operations.
Suggestions
Add a concrete README.md template with actual markdown structure that can be copy-pasted and filled in
Include an example of a complete skill creation showing input (user requirements) and output (generated files)
Add validation steps after each phase (e.g., 'Verify README.md contains all required sections', 'Confirm folder appears in registry')
Link to or inline the 'Estándar de Diamante' requirements so Claude knows exactly what standards to follow
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill has some unnecessary padding like emoji headers and the generic 'When to Use' section that adds no value. The description section repeats information that could be inferred from the title. However, the core workflow is reasonably compact. | 2 / 3 |
Actionability | The skill lacks concrete, executable guidance. It describes what to do abstractly ('Generar el código', 'Crear la carpeta física') but provides no actual code examples, templates, or copy-paste ready content. The README.md structure mentioned is never shown. | 1 / 3 |
Workflow Clarity | The three phases provide a clear sequence, but there are no validation checkpoints. No verification step exists to confirm the skill was created correctly, the README follows the standard, or the registry was updated properly. Missing feedback loops for file operations. | 2 / 3 |
Progressive Disclosure | The skill references external standards ('Estándar de Diamante', 'anatomía de carpeta -> README.md -> Registro') without linking to them or explaining them. No references to supporting documentation. Content that should be in separate files (templates, examples) is neither inline nor referenced. | 1 / 3 |
Total | 6 / 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 |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
8692fbc
Table of Contents
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.