Ingeniero de Sistemas de Andru.ia. Diseña, redacta y despliega nuevas habilidades (skills) dentro del repositorio siguiendo el Estándar de Diamante.
40
26%
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
17%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 identifies a specific domain (skill creation within a repository) and names some actions, but relies heavily on proprietary jargon ('Estándar de Diamante', 'Andru.ia') without explanation. It completely lacks a 'Use when...' clause and natural trigger terms that would help Claude select this skill appropriately from a pool of many skills.
Suggestions
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks to create a new skill, add a skill file, write a SKILL.md, or scaffold a new capability.'
Replace or supplement jargon like 'Estándar de Diamante' with a brief plain-language explanation of what it entails (e.g., 'following the Diamond Standard template with YAML frontmatter, description, and structured sections').
Include natural keywords users would say, such as 'new skill', 'skill template', 'SKILL.md', 'add capability', 'skill file' to improve trigger term coverage.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (skills/habilidades within a repository) and some actions ('Diseña, redacta y despliega nuevas habilidades'), but the actions are somewhat generic and not deeply concrete—'designs, writes, and deploys' are broad verbs. The mention of 'Estándar de Diamante' adds some specificity but is jargon without explanation. | 2 / 3 |
Completeness | While it partially answers 'what' (designs, writes, deploys skills), there is no explicit 'Use when...' clause or equivalent trigger guidance. The 'when' is entirely missing, which per the rubric caps completeness at 2, but the 'what' is also weak enough that a score of 1 is appropriate. | 1 / 3 |
Trigger Term Quality | The description uses specialized jargon ('Estándar de Diamante', 'Andru.ia', 'Ingeniero de Sistemas') that users would not naturally say. It lacks natural trigger terms a user might use like 'create a new skill', 'add skill', 'skill template', or 'SKILL.md'. | 1 / 3 |
Distinctiveness Conflict Risk | The mention of 'Estándar de Diamante' and 'Andru.ia' provides some distinctiveness, but 'diseña, redacta y despliega nuevas habilidades' could overlap with general coding or documentation skills. The niche is somewhat defined but not sharply delineated. | 2 / 3 |
Total | 6 / 12 Passed |
Implementation
35%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill outlines a workflow for creating new skills but lacks the concrete, executable guidance needed to be truly actionable. It references standards and structures (Estándar de Diamante, Antigravity structure) without providing templates, examples, or links to their definitions. The workflow phases are logically sequenced but missing validation steps and concrete output examples.
Suggestions
Add a concrete README.md template with actual markdown content showing the expected structure, sections, and formatting for a generated skill.
Include a concrete example of a registry snippet showing the exact format and fields required for the 'Full skill registry' table.
Add a validation step after FASE 3 (e.g., verify the folder was created, confirm the README.md matches the Diamond Standard, test that the orchestrator can discover the new skill).
Link to or inline the 'Estándar de Diamante' specification so Claude knows exactly what structural requirements to follow, rather than referencing it abstractly.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill includes some unnecessary filler (e.g., 'Esta habilidad es aplicable para ejecutar el flujo de trabajo o las acciones descritas en la descripción general' adds nothing, and the description repeats the frontmatter). The 'Soy el Ingeniero de Sistemas' persona framing is unnecessary context Claude doesn't need. However, the core workflow sections are reasonably tight. | 2 / 3 |
Actionability | The skill provides no concrete code, no executable commands, no template examples, and no actual README.md template or registry snippet format. It describes what to do abstractly ('Generar el código para los siguientes archivos') without showing what those files should look like. There are no copy-paste ready artifacts or concrete examples of output. | 1 / 3 |
Workflow Clarity | The three phases provide a clear sequence, but there are no validation checkpoints. After creating files and updating the registry, there's no verification step (e.g., validate the README structure, confirm the registry entry is correct, test that the orchestrator recognizes the new skill). For file creation and registry modification operations, this lack of validation caps the score at 2. | 2 / 3 |
Progressive Disclosure | The content is organized into logical sections with clear headers, which is good. However, it references an 'Estándar de Diamante' and 'anatomía de carpeta -> README.md -> Registro' without linking to any reference documents that define these standards. The skill would benefit from explicit links to the Diamond Standard specification and example skills. | 2 / 3 |
Total | 7 / 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 | |
1a9f5ac
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.