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.
26
17%
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 professional title or role description rather than a functional skill description. It lacks concrete actions, natural trigger terms, explicit 'when to use' guidance, and distinctiveness. The use of first/third person is acceptable (third person), but the content is too abstract and buzzword-heavy to be useful for skill selection.
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, y genera hojas de ruta para implementación de modelos de machine learning.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Usar cuando el usuario necesite planificar un proyecto de inteligencia artificial, evaluar tecnologías de IA, o diseñar una arquitectura de solución.'
Include specific file types, deliverables, or domains to increase distinctiveness, e.g., 'Genera documentos de arquitectura, diagramas de flujo de datos, y planes de implementación para proyectos de NLP, visión por computadora, o automatización con IA.'
| 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 'solution architecture' could overlap with numerous other skills. There are no distinct triggers or a clear niche that would prevent conflicts. | 1 / 3 |
Total | 4 / 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 high-level conceptual framework for project diagnosis but lacks the concrete, actionable guidance needed for Claude to execute it reliably. The workflow bifurcation is a good structural idea, but without templates for output artifacts, concrete inspection commands, or examples of expected outputs, Claude would have to improvise most of the actual work. The persona-style framing adds tokens without adding value.
Suggestions
Add concrete templates or examples for the output artifacts (tareas.md and plan_implementacion.md) so Claude knows exactly what format and content to produce.
Replace vague instructions like 'Analizo el Stack actual' with specific commands or file inspection patterns (e.g., 'Read package.json to identify framework, check src/ directory structure').
Define what 'registro raíz' means and how to consult it—provide the actual skill registry path or list of available expert skills.
Remove the persona description ('Soy el Arquitecto...') and the redundant Description section to improve conciseness.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill includes some unnecessary framing ('Soy el Arquitecto de Soluciones Principal...') and redundant descriptions that Claude doesn't need. The 'Description' section largely repeats the 'When to Use' section. However, the workflow sections are reasonably concise. | 2 / 3 |
Actionability | The skill provides no concrete code, commands, or executable examples. It describes a process at a high level ('Analizo el Stack actual', 'Consulto el registro raíz') without specifying how to actually perform these actions—no file inspection commands, no template for the output artifacts, no example of what tareas.md or plan_implementacion.md should look like. | 1 / 3 |
Workflow Clarity | The bifurcation into Scenario A and B is a clear structural choice, and the steps are sequenced. However, there are no validation checkpoints, no criteria for how to determine if the folder is 'empty' vs has code, and no feedback loops for error recovery. The 'Mapear Skills' step references a 'registro raíz' without explaining what it is or how to consult it. | 2 / 3 |
Progressive Disclosure | The content is organized into logical sections with headers, which is good. However, there are no bundle files or external references despite mentioning output artifacts (tareas.md, plan_implementacion.md) that would benefit from templates in separate files. The skill is somewhat monolithic for its complexity level. | 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 | |
- Repository
- sickn33/antigravity-awesome-skills
- Commit
22710e9
- 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.