CtrlK
BlogDocsLog inGet started
Tessl Logo

20-andruia-niche-intelligence

Estratega de Inteligencia de Dominio de Andru.ia. Analiza el nicho específico de un proyecto para inyectar conocimientos, regulaciones y estándares únicos del sector. Actívalo tras definir el nicho.

52

Quality

59%

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/20-andruia-niche-intelligence/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

56%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.

The skill presents a clear two-phase instructional workflow with a well-defined dossier deliverable, and as an instruction-only skill it does not suffer from missing code. Its main weaknesses are padding (duplicated sections, persona fluff), the absence of a sample dossier or output template in the Example section, and inconsistent structure that keeps it from reading as a tight, well-organized single-file skill.

Suggestions

Remove the duplicated "When to Use" section and the persona preamble; keep one trigger section and lead with the two-phase protocol to cut roughly a quarter of the body's tokens.

Replace the bare user-request Example with a short sample "Dossier de Inteligencia" (even a skeleton with the four required sections filled for one example niche) so the expected output format is unambiguous.

Normalize the structure: single H1 at the top, consistent heading hierarchy, and one language convention for section headers to remove the current organizational roughness.

DimensionReasoningScore

Conciseness

The body is mostly efficient, but contains padding: a duplicated "When to Use" section (one before the H1 title, one near the end), persona framing ("Soy el Estratega… No Programo código genérico"), and platitudes like "Estándar de Diamante". It is not a 2 because it never explains concepts Claude already knows and is reasonably short overall.

3 / 5

Actionability

There is concrete guidance for an instruction-only skill: a two-phase protocol and a four-part dossier structure (Stack de Industria, Cumplimiento y Normativa, UX de Nicho, Puntos de Dolor Ocultos) plus a specific rule example (dental clinics → turnos, odontogramas, historias clínicas). It is not a 4 because the "## Example" section shows only a user request with no sample output, and no dossier template or output format is provided.

3 / 5

Workflow Clarity

The workflow is clearly sequenced: FASE 1 domain analysis with three numbered reasoning questions, then FASE 2 dossier delivery with four named sections. Validation checkpoints are absent but the skill performs analysis/instruction only — no destructive or batch operations — so the workflow-clarity cap does not apply; it stays below 5 because checkpoints and error-recovery guidance are still missing.

4 / 5

Progressive Disclosure

This is a single-file skill with no bundle files (references/, scripts/, assets/ are absent) and no external references, so nothing is nested or buried. However, organization is uneven: the duplicate "When to Use" section, an H1 appearing after an H2, and mixed English/Spanish section conventions match "some structure but could be better organized" rather than the well-organized anchor 4.

3 / 5

Total

13

/

20

Passed

Description

62%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.

The description answers both 'what' and 'when' in third person with a clear, distinct niche, but the capability statement stays fairly abstract ('inyectar conocimientos, regulaciones y estándares') and trigger-term coverage is thin. Adding the concrete deliverable (a domain intelligence dossier) and the natural phrases users would say would lift specificity and trigger quality toward anchor 5.

Suggestions

Name the concrete deliverable in the description, e.g. "Genera un dossier de inteligencia de dominio (stack de industria, normativa, patrones UX y puntos de dolor)" instead of the abstract "inyectar conocimientos".

Broaden natural trigger terms to include the phrases users actually say — "regulaciones del sector", "estándares de la industria", "compliance", "conocimiento del dominio" — alongside the existing "nicho" and "sector".

DimensionReasoningScore

Specificity

"Analiza el nicho específico de un proyecto para inyectar conocimientos, regulaciones y estándares únicos del sector" names the domain and 1-2 actions (analyze the niche, inject regulations/standards), but "inyectar conocimientos" is abstract and no concrete deliverable is named. It is not a 4 because the actions listed are not several distinct, concrete operations like "extracts text, fills forms, converts pages".

3 / 5

Completeness

Both parts are present: what — "Analiza el nicho específico de un proyecto para inyectar conocimientos, regulaciones y estándares únicos del sector"; when — "Actívalo tras definir el nicho". The 'when' is explicit but terse and lacks concrete user-side trigger phrases, matching anchor 4 rather than the fully explicit anchor 5.

4 / 5

Trigger Term Quality

Relevant keywords are present ("nicho", "sector", "regulaciones", "estándares") and the trigger "Actívalo tras definir el nicho" is natural, but common variations users would say ("industry standards", "compliance", "regulatory requirements", "domain knowledge") are missing. It matches "some relevant keywords but missing common variations or synonyms" rather than the good coverage of anchor 4.

3 / 5

Distinctiveness Conflict Risk

The skill occupies a clear niche (domain/industry intelligence injection within the Andru.ia workflow, activated only after the niche is defined), with only minor overlap risk against the closely related consultant skill it references. It is not a 5 because the description does not fully distinguish it from a general research/compliance-analysis skill.

4 / 5

Total

14

/

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
sickn33/agentic-awesome-skills
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.