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

10%

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/00-andruia-consultant/SKILL.md

Quality

Content

20%Scale 1-3

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

This skill is primarily a high-level persona description rather than actionable technical guidance. It lacks concrete commands, tool usage patterns, or executable examples that would enable Claude to actually perform the described diagnostic and roadmap tasks. The branding language ('Estándar de Diamante', 'Pure Engine') adds tokens without adding clarity.

Suggestions

Replace abstract steps like 'Analizo el Stack actual' with concrete tool calls (e.g., `list_files`, `read_file('package.json')`) and specific analysis patterns to follow.

Add a concrete example of what `tareas.md` and `plan_implementacion.md` should look like, including a template or schema for each artifact.

Specify how to 'consult the root registry' to find expert skills—provide the actual path or mechanism for discovering available skills.

Remove the self-description paragraph and branding terms ('Estándar de Diamante') that don't translate into actionable instructions.

Dimension	Reasoning	Score
Conciseness	The skill explains concepts Claude already knows (what a solutions architect does, what scanning code means), includes a verbose self-description section, and pads with unnecessary branding/emoji. The 'Description' section repeats the 'When to Use' section. Phrases like 'Estándar de Diamante' and 'Estándar Maestro' are vague branding rather than actionable content.	1 / 3
Actionability	No concrete code, commands, or executable examples are provided. The workflow describes abstract steps ('Analizo el Stack actual', 'Consulto el registro raíz') without specifying how to actually perform them—no tool calls, no file reading commands, no specific analysis techniques. 'Propose a Squad of 3-5 experts' references skills like @ui-ux-pro without explaining how to discover or invoke them.	1 / 3
Workflow Clarity	The bifurcation into Scenario A (empty folder) and Scenario B (existing project) provides a clear branching structure, and the steps are sequenced. However, there are no validation checkpoints—no step to verify the diagnosis is correct before proceeding, no feedback loops if the generated artifacts are incomplete or wrong, and no concrete criteria for determining which scenario applies beyond vague 'detect files.'	2 / 3
Progressive Disclosure	The content has some structural organization with clear sections and headers. However, it references external concepts ('registro raíz', specific expert skills) without providing links or paths to them. No bundle files exist to support the references. The content is relatively short so a monolithic structure isn't terrible, but the references to external resources are unresolved.	2 / 3
	Total	6 / 12 Passed

Description

0%Scale 1-3

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 more like a job title or persona definition than a skill description. It lacks concrete actions, natural trigger terms, and explicit 'use when' guidance. The vague language ('diagnostica', 'hoja de ruta óptima') and role-based framing make it nearly impossible for Claude to reliably select this skill over others.

Suggestions

Replace the role/persona framing with specific concrete actions the skill performs, e.g., 'Evaluates AI project feasibility, designs system architectures, recommends tech stacks, and creates implementation roadmaps.'

Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks about AI project planning, architecture decisions, technology selection, or implementation strategy in Spanish.'

Remove the brand identity ('Andru.ia') and consultant title from the description — focus on what the skill does functionally rather than who it represents.

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 vague (diagnoses and creates roadmaps) and there is no explicit 'when' clause or trigger guidance. Both components are weak or missing.	1 / 3
Trigger Term Quality	The description lacks natural keywords users would say. Terms like 'Arquitecto de Soluciones Principal' and 'Consultor Tecnológico' are role titles, not task-oriented trigger terms. 'Proyectos de IA' is somewhat relevant but too broad.	1 / 3
Distinctiveness Conflict Risk	The description is very generic — 'AI projects consulting' and 'solution architecture' could overlap with many other skills. The brand name 'Andru.ia' adds some distinctiveness but doesn't clarify the skill's unique functional niche.	1 / 3
	Total	4 / 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: popey/claude-code-skills
Path: skills/00-andruia-consultant/SKILL.md
Commit: a5a6601

Reviewed: 5 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.