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.
21
10%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/antigravity-awesome-skills-claude/skills/00-andruia-consultant/SKILL.mdQuality
Discovery
0%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 job title rather than a skill description. It lacks concrete actions, natural trigger terms, explicit 'when to use' guidance, and distinctiveness. It would be very difficult for Claude to correctly select this skill from a pool of available skills.
Suggestions
Replace the job title framing with specific concrete actions the skill performs, e.g., 'Evalúa requisitos técnicos, diseña arquitecturas de IA, 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 pida diseñar una arquitectura de IA, planificar un proyecto de inteligencia artificial, o evaluar tecnologías para una solución de machine learning.'
Remove the persona/brand identity ('Andru.ia', 'Arquitecto de Soluciones Principal') and focus on what the skill actually does and when it should be selected, using third-person voice.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague, abstract language like 'diagnostica y traza la hoja de ruta óptima' (diagnoses and traces the optimal roadmap) without listing any concrete actions. It reads more like a job title than a capability description. | 1 / 3 |
Completeness | The 'what' is extremely vague (diagnoses and creates roadmaps) and there is no 'when' clause or explicit trigger guidance. It fails to answer either question clearly. | 1 / 3 |
Trigger Term Quality | The description lacks natural keywords a user would say. Terms like 'Arquitecto de Soluciones Principal' and 'Consultor Tecnológico' are job titles, not trigger terms. 'Proyectos de IA' is somewhat relevant but too generic to serve as a useful trigger. | 1 / 3 |
Distinctiveness Conflict Risk | The description is very generic — 'AI projects consulting' and 'roadmap' could overlap with many other skills related to project planning, AI development, or consulting. There are no distinct triggers to differentiate it. | 1 / 3 |
Total | 4 / 12 Passed |
Implementation
20%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill reads more like a persona description and high-level process overview than an actionable technical guide. It lacks concrete examples, executable commands, output templates, and validation steps that would make it genuinely useful. The branding language and conceptual explanations consume tokens without providing the specificity Claude needs to execute the described workflows.
Suggestions
Add concrete example outputs for tareas.md and plan_implementacion.md (even abbreviated templates) so Claude knows exactly what format to produce.
Replace abstract steps like 'Escaneo Técnico' with specific commands or file inspection patterns (e.g., 'Read package.json to identify framework, check src/ structure for architecture pattern').
Remove the Description section entirely—it restates the frontmatter and adds no actionable information.
Define what 'registro raíz' means and how to actually consult it, or provide a concrete list of available expert skills with selection criteria.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill explains concepts Claude already knows (what a solutions architect does, what diagnosis means), includes a verbose description section that restates the frontmatter, and uses decorative emoji headers and branding language ('Estándar de Diamante', 'Andru.ia') that consume tokens without adding actionable value. | 1 / 3 |
Actionability | The skill provides no concrete code, commands, or executable examples. It describes abstract processes ('Escaneo Técnico', 'Mapear Skills') without specifying how to actually perform them—no file inspection commands, no template for tareas.md or plan_implementacion.md, no example outputs, and no concrete criteria for the diagnostic steps. | 1 / 3 |
Workflow Clarity | The bifurcation into Scenario A and B provides a clear branching structure, and the post-interview phase is sequenced. However, there are no validation checkpoints, no feedback loops for error recovery, and the steps within each scenario are vague (e.g., 'Escaneo Técnico' with no specifics on what to check or how to validate findings). | 2 / 3 |
Progressive Disclosure | The content is organized into logical sections with headers, which is reasonable. However, it references external concepts like 'registro raíz' and specific skill names (@ui-ux-pro, etc.) without linking to any supporting files, and there are no bundle files to support progressive disclosure. The artifact templates (tareas.md, plan_implementacion.md) are mentioned but never shown or linked. | 2 / 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 | |
- Repository
- sickn33/antigravity-awesome-skills
- Commit
43af20c
- 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.