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.

Quality

37%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

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

Quality

Content

57%

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

The body is a clear, well-structured overview of a simple skill-creation workflow with good organization, but it lacks executable examples/templates and validation steps for its deploy actions, limiting actionability and workflow clarity.

Suggestions

Add concrete templates or examples for the README.md and the registry snippet so the output is copy-paste ready rather than described.

Insert explicit validation checkpoints in FASE 3 (e.g., verify the folder does not already exist, confirm the registry entry is well-formed before updating the master registry) and a rollback/ask step on failure.

Tighten or remove the 'Descripción' and 'Instrucciones Generales' role/persona restatements to reduce redundancy with the frontmatter and improve token efficiency.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with organized sections, but the 'Descripción' restates the persona from the frontmatter and 'Instrucciones Generales' explain role/quality expectations that add limited new instruction; it could be tightened.	2 / 3
Actionability	It provides some concrete structure (the three FASE steps, folder path, numeric prefixes) but no executable commands or templates — the README content and registry snippet are described rather than shown, leaving key details unspecified.	2 / 3
Workflow Clarity	The Flujo de Trabajo is sequenced into three numbered phases, but there are no validation checkpoints or feedback loops for the destructive/deploy steps (creating folders, overwriting the master registry), which caps clarity at 2 per the guidelines.	2 / 3
Progressive Disclosure	This is a short single-purpose skill with no bundle files and well-organized sections (When to Use, Descripción, Instrucciones, Flujo de Trabajo, Reglas de Oro, Limitations); per the simple-skill note, that warrants a 3 with no external references needed.	3 / 3
	Total	9 / 12 Passed

Description

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 is written as a first-person role persona ('Soy el Ingeniero de Sistemas de Andru.ia') with no explicit use-when triggers and no natural trigger terms, which violates several rubric guidelines. It names the domain and a few actions but is incomplete on when to invoke and weak on distinctiveness.

Suggestions

Rewrite the description in third person stating concrete capabilities (e.g., 'Designs, writes, and deploys new skills in the Antigravity repository following the Diamond Standard'), and drop the first-person persona to satisfy the third-person-voice guideline.

Add an explicit 'Use when...' clause with natural trigger terms users would say (e.g., 'Use when creating a new skill, adding a capability to the skill registry, or scaffolding a skill folder').

Specify concrete outputs (e.g., README.md, registry snippet, numbered skill folder) to raise specificity and distinctiveness above generic skill-authoring wording.

Dimension	Reasoning	Score
Specificity	The description names a domain (skill creation/deployment) and several concrete actions ('Diseña, redacta y despliega nuevas habilidades'), but the actions are high-level and lack comprehensive specific operations such as what files are produced or what registry is updated.	2 / 3
Completeness	It states what the skill does but provides no 'Use when...' clause or equivalent explicit trigger guidance, so the 'when' question is entirely unaddressed and completeness is capped at 2 per the guidelines — lowered to 1 because both what and when are weak, with the what framed as a persona rather than a capability.	1 / 3
Trigger Term Quality	There are no natural user-facing trigger terms; the wording relies on role jargon ('Ingeniero de Sistemas de Andru.ia', 'Estándar de Diamante') rather than phrases a user would actually say when needing this skill.	1 / 3
Distinctiveness Conflict Risk	The skill is framed around a niche (authoring skills for the Andru.ia/Antigravity repository), which is somewhat specific, but the description uses a role persona rather than distinct triggers, so it could still overlap with general skill-authoring tasks.	2 / 3
	Total	6 / 12 Passed

Validation

93%

Warnings & errors only

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

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: sickn33/antigravity-awesome-skills
Path: skills/10-andruia-skill-smith/SKILL.md
Commit: 3dfb633

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

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.