CtrlK
BlogDocsLog inGet started
Tessl Logo

10-andruia-skill-smith

Ingeniero de Sistemas de Andru.ia. Diseña, redacta y despliega nuevas habilidades (skills) dentro del repositorio siguiendo el Estándar de Diamante.

50

Quality

55%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/10-andruia-skill-smith/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

65%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is well-structured and concise with a clear three-phase workflow, but it is not fully actionable — the README and registry-snippet templates are never shown — and the workflow lacks the validation checkpoint that a file-writing, registry-mutating operation should have.

Suggestions

Provide a concrete README.md template and an example 'Snippet de Registro' line so the output is copy-paste ready rather than invented.

Add an explicit validation step in FASE 3 (e.g. 'verify the new README follows the Estándar de Diamante and the registry line parses before committing').

Replace the circular 'When to Use' sentence with concrete trigger conditions instead of pointing back to 'la descripción general'.

DimensionReasoningScore

Conciseness

The body is lean (~46 lines) and mostly assumes Claude's competence, with only minor redundancy — the circular 'When to Use' line ('aplicable para ejecutar el flujo de trabajo descrito en la descripción general') and the 'Descripción' section restate the frontmatter.

4 / 5

Actionability

It names concrete artifacts (README.md, 'Snippet de Registro', the skills folder path, numeric prefixes) but never shows the actual README template or registry-snippet format the agent must produce, and the 'Example' block only gives a user request with no example output.

3 / 5

Workflow Clarity

The three phases (ADN → Materialización → Despliegue) are clearly sequenced, but the workflow writes files and updates the master registry without any validation/verification checkpoint, so it is capped at 3 per the destructive/batch-operations guideline.

3 / 5

Progressive Disclosure

The skill is under 50 lines, single-purpose, needs no external references (none exist in references/scripts/assets), and is organized into clearly labeled sections (When to Use, Instrucciones, Flujo de Trabajo, Reglas de Oro, Example, Limitations).

5 / 5

Total

15

/

20

Passed

Description

46%Weight 40%Scale 1-5

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 names a specific niche and three high-level actions but stays generic and lacks any 'Use when...' trigger guidance. It is distinguishable but would be hard for a user to invoke from natural phrasing alone.

Suggestions

Add an explicit 'Use when...' clause naming natural user phrasings (e.g. 'Úsala cuando el usuario pida crear, diseñar o desplegar una nueva skill en el repositorio').

Replace the generic verbs 'Diseña, redacta y despliega' with concrete deliverables (e.g. 'genera el README.md de la skill, el snippet de registro y la carpeta numerada').

Surface the natural trigger terms users would say ('nueva skill', 'crear habilidad', 'agregar skill al registro') to improve trigger-term coverage.

DimensionReasoningScore

Specificity

It names the domain (skill creation in a repo) and three actions — 'Diseña, redacta y despliega' (designs, drafts, deploys) — but these are high-level generic verbs rather than concrete operations, and coverage is not comprehensive.

3 / 5

Completeness

It clearly states what the skill does (design/draft/deploy skills in the repo) but has no 'Use when...' clause or equivalent trigger guidance, which caps completeness at 3 per the rubric guideline.

3 / 5

Trigger Term Quality

It contains a couple of generic terms ('habilidades (skills)', 'repositorio') plus the jargon 'Estándar de Diamante', but lacks the natural phrases a user would actually say to invoke this skill (e.g. 'crea una nueva skill', 'diseña una habilidad').

2 / 5

Distinctiveness Conflict Risk

It carves a clear niche (creating skills for the Andru.ia repo under the 'Estándar de Diamante') with only minor overlap risk against closely related meta-skill tooling; not a 5 because the trigger phrasing is not distinct enough to prevent accidental invocation.

4 / 5

Total

12

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
sickn33/agentic-awesome-skills
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.