00-andruia-consultant

Arquitecto de Soluciones Principal y Consultor Tecnológico de Andru.ia. Diagnostica y traza la hoja de ruta óptima para proyectos de IA en español.

Quality

28%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/00-andruia-consultant/SKILL.md

Quality

Discovery

22%

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 description reads like a persona or role definition rather than a functional skill description. It lacks concrete actions, explicit trigger conditions, and natural user-facing keywords. The use of first/third person is acceptable (third person), but the content is too abstract and role-oriented to effectively guide skill selection.

Suggestions

Replace the role/persona framing with specific concrete actions the skill performs, e.g., 'Evalúa viabilidad técnica de proyectos de IA, diseña arquitecturas de solución, genera hojas de ruta con hitos y tecnologías recomendadas.'

Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Usar cuando el usuario necesite planificar un proyecto de IA, evaluar tecnologías, definir arquitectura de solución, o crear un roadmap técnico.'

Remove the persona/title framing ('Arquitecto de Soluciones Principal y Consultor Tecnológico de Andru.ia') and focus on what the skill does and when to use it.

Dimension	Reasoning	Score
Specificity	The description uses vague, abstract language like 'diagnostica y traza la hoja de ruta óptima' without listing concrete actions. It describes a role/persona ('Arquitecto de Soluciones Principal') rather than specific capabilities.	1 / 3
Completeness	The 'what' is vaguely stated (diagnose and create roadmaps for AI projects) and there is no explicit 'when' clause or trigger guidance. The description reads more like a job title than a skill description.	1 / 3
Trigger Term Quality	Contains some relevant keywords like 'IA' (AI), 'proyectos de IA', and 'hoja de ruta' that users might mention, but lacks common variations and natural trigger terms. 'Arquitecto de Soluciones' and 'Consultor Tecnológico' are role titles, not terms users would naturally use when requesting help.	2 / 3
Distinctiveness Conflict Risk	The mention of 'Andru.ia' and Spanish-language AI project consulting provides some distinctiveness, but 'proyectos de IA' is broad enough to overlap with many AI-related skills. The branding to a specific company helps somewhat.	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 provides a reasonable high-level framework for project diagnosis and roadmap creation, with a clear bifurcation between new and existing projects. However, it is fundamentally lacking in actionability—there are no concrete commands, templates, file formats, or executable examples that would allow Claude to reliably produce consistent outputs. The skill reads more like a persona description than an operational guide.

Suggestions

Add concrete templates or schemas for the output artifacts (tareas.md and plan_implementacion.md) so Claude knows exactly what format to produce.

Replace vague instructions like 'Consulto el registro raíz' with specific file paths or tool commands that Claude can actually execute.

Include a concrete example of a complete diagnostic flow (input scenario → questions asked → output artifacts generated) to make the workflow fully actionable.

Remove the self-referential 'Description' section that repeats the 'When to Use' content and adds no operational value.

Dimension	Reasoning	Score
Conciseness	The skill includes some unnecessary self-description ('Soy el Arquitecto de Soluciones Principal...') and redundant framing that Claude doesn't need. The 'Description' section repeats the 'When to Use' section. However, the workflow sections are reasonably concise.	2 / 3
Actionability	The skill is almost entirely abstract and descriptive rather than actionable. There are no concrete commands, code examples, file templates, or specific tool invocations. Instructions like 'Consulto el registro raíz y propongo un Squad' and 'Analizo el Stack actual' are vague with no executable steps or concrete output formats.	1 / 3
Workflow Clarity	The bifurcation into Scenario A and B is a clear structural choice, and steps are numbered. However, there are no validation checkpoints, no feedback loops for error recovery, and the 'Fase de Sincronización' lacks detail on how to actually execute each step (e.g., how to 'consult the root registry' or what the artifact templates look like).	2 / 3
Progressive Disclosure	The content is organized into logical sections with headers, which is good. However, it references external concepts like 'registro raíz' and expert skills (@ui-ux-pro, etc.) without linking to them or explaining where to find them. The artifact outputs (tareas.md, plan_implementacion.md) are mentioned but no templates or references to template files are provided.	2 / 3
	Total	7 / 12 Passed

Validation

90%

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 — 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

Repository: sickn33/antigravity-awesome-skills
Commit: 1a9f5ac

Reviewed: 2 days 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.