CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

00-andruia-consultant

Usar al iniciar o mejorar un proyecto de IA: diagnostica código y restricciones, propone skills existentes y redacta tareas y un plan de implementación en español.

59

Quality

74%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/antigravity-00-andruia-consultant/SKILL.md

The canonical home for this skill is 00-andruia-consultant in sickn33/agentic-awesome-skills

SKILL.md
Quality
Evals
Security

Quality

Content

67%Weight 40%Scale 1-5

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

A well-structured consulting skill with a clear bifurcated workflow, concrete interview questions, field-level artifact specifications, explicit error handling, and a genuine validation step before delivery. The main weaknesses are redundant restatements of its purpose, an inline provenance section that adds tokens without guiding action, and the absence of a fix-and-re-verify loop after the verification step.

Suggestions

Collapse the 'When to Use' and '## Description' sections into a single purpose statement — the workflow itself already communicates when each scenario applies, so the triple restatement costs tokens without adding guidance.

Move or trim the 'Proveniencia' section (e.g., keep only the source URL and one-line caveat) — its licensing discussion does not guide execution and the key non-misrepresentation point can be one sentence.

Add a fix-and-re-verify loop to the 'Verificar Entrega' step, e.g., 'Si una skill citada no existe o una fase carece de comprobación, corregir el artefacto y repetir la verificación antes de entregar.'

DimensionReasoningScore

Conciseness

The body is mostly efficient — it teaches no basic concepts and stays instruction-focused — but the skill's purpose is restated three times (the 'When to Use' section, the '## Description' section, and implicitly in the workflow), and the 'Proveniencia' section is meta-commentary that does not guide execution. This matches anchor 3 ('mostly efficient but includes some unnecessary explanation') rather than anchor 2, since the padding is limited rather than pervasive.

3 / 5

Actionability

Concrete, specific guidance throughout: literal interview questions (QUÉ / PARA QUIÉN / QUÉ RESULTADO), field-level artifact specs for 'tareas.md' and 'plan_implementacion.md', and explicit error handling ('Si falta una competencia, declaro el hueco en vez de inventar un ID'). It falls short of anchor 5 because there are no copy-paste-ready artifact templates and the worked example is brief; it exceeds anchor 3 because the guidance is executable as written, not pseudocode.

4 / 5

Workflow Clarity

A clearly sequenced bifurcated workflow (environment scan → scenario A/B → interview → map skills → generate artifacts → 'Verificar Entrega') with an explicit validation checkpoint that lists concrete confirmations (skills cited exist, phases have concrete checks, verified observations separated from hypotheses). It does not reach anchor 5 because there is no fix-and-re-verify feedback loop after the verification step — the closest anchor is 4 ('clear sequence with most checkpoints present; minor validation gaps').

4 / 5

Progressive Disclosure

The 75-line body is well organized into clearly headed sections (instructions, scenario workflow, generation, verification, example, limitations) with no external references needed for a consulting skill of this size. Minor gaps — the duplicated purpose statements and the provenance block inline rather than in frontmatter or a separate file — keep it at anchor 4 rather than 5.

4 / 5

Total

15

/

20

Passed

Description

71%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A well-formed description that states what the skill does and when to use it in third-person-capable, natural phrasing, with several concrete capabilities. Its main weaknesses are a single trigger scenario without synonyms, and a broad project-start/improve trigger that risks overlap with generic planning skills.

DimensionReasoningScore

Specificity

The description lists several concrete actions — 'diagnostica código y restricciones, propone skills existentes y redacta tareas y un plan de implementación' — all stated as specific capabilities. It falls short of anchor 5 because coverage is incomplete (the interview, squad-mapping, and verification steps of the workflow are absent), but exceeds anchor 3 by naming more than 1-2 concrete actions.

4 / 5

Completeness

Both 'what' (diagnose code and constraints, propose existing skills, draft tasks and implementation plan) and 'when' ('Usar al iniciar o mejorar un proyecto de IA') are explicitly present. It does not reach anchor 5 because only a single trigger scenario is given, without the multiple concrete trigger phrases the top anchor requires.

4 / 5

Trigger Term Quality

'al iniciar o mejorar un proyecto de IA' is phrasing a user would naturally say, reinforced by capability keywords like 'diagnostica', 'skills', and 'plan de implementación'. It misses anchor 5 because common synonyms users might say ('crear', 'diseñar', 'roadmap', 'arquitectura') are absent.

4 / 5

Distinctiveness Conflict Risk

The Spanish-language deliverables and skill-registry proposing give it a recognizable niche, but the trigger 'iniciar o mejorar un proyecto de IA' is broad and would overlap with general project-init, planning, or architecture skills. This matches anchor 3 (somewhat specific, but overlap risk with similar skills) rather than anchor 4's 'minor overlap risk only with closely related skills'.

3 / 5

Total

15

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

boisenoise/skills-collections

Path

skills/antigravity-00-andruia-consultant/SKILL.md

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.