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.

54

Quality

61%

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

61%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 body is a well-structured, mostly actionable instruction skill with a clear two-phase workflow and a concrete deliverable, weakened by persona padding, a duplicated When-to-Use section, and absent validation checkpoints. It does not over-explain basics Claude already knows.

Suggestions

Remove the persona/motivational padding ('Estándar de Diamante', 'sonar como un consultor con 20 años', 'despertar') and consolidate the two 'When to Use' sections into one to tighten conciseness.

Add an explicit validation/verification checkpoint in the workflow, e.g. after FASE 1 confirm the niche is concrete before generating the dossier, and after FASE 2 verify each dossier section is populated — lifting workflow_clarity above 3.

Expand the Example block with a brief sample dossier output (not just the user request) to make the deliverable copy-paste ready and push actionability toward 5.

DimensionReasoningScore

Conciseness

The body is mostly structured guidance rather than concept explanation, but it carries noticeable padding — persona fluff ('Estándar de Diamante', 'sonar como un consultor con 20 años', 'despertar') and a duplicate 'When to Use' section — that could be trimmed. It does not reach 'noticeably verbose' (2) because most of the prose is actionable.

3 / 5

Actionability

Concrete instruction-only guidance: FASE 1 lists 3 specific reasoning questions and FASE 2 specifies a 4-part dossier (Stack de Industria, Cumplimiento y Normativa, UX de Nicho, Puntos de Dolor) with real-world examples (RGPD, HIPAA, Facturación DIAN, 'Clínicas Dentales'). Minor gap: the worked Example block is only a one-line user request with no sample output.

4 / 5

Workflow Clarity

A clear two-phase sequence exists (Análisis de Dominio → Entrega del Dossier) but there are no explicit validation checkpoints; the Limitations section's 'stop and ask for clarification if inputs are missing' is the only implicit checkpoint. This fits 'steps listed but checkpoints missing or implicit' rather than 4.

3 / 5

Progressive Disclosure

The skill is a single self-contained ~60-line file with well-organized sections and no external bundle files to reference; structure is good. The duplicate 'When to Use' (one near the top, one mid-body) is a minor organization gap keeping it from 5.

4 / 5

Total

14

/

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 covers both what and when with a clear domain focus and reasonable trigger terms, but is held back by non-comprehensive action coverage and missing keyword synonyms. It is functional but could be sharper and more complete.

Suggestions

Add concrete deliverables to the description (e.g., 'genera un dossier de inteligencia de dominio con stack, normativa, UX y puntos de dolor') to lift specificity toward 5.

Expand the when-clause with natural trigger phrases users actually say, e.g. 'Actívalo cuando el nicho esté definido y necesites regulaciones, estándares o patrones UX del sector (Fintech, HealthTech, EdTech...).'

Include common synonyms ('industria', 'vertical', 'compliance', 'normativa') alongside 'nicho', 'regulaciones' and 'estándares' to improve trigger-term coverage.

DimensionReasoningScore

Specificity

Names the domain (Inteligencia de Dominio/nicho) and 1-2 concrete actions — 'Analiza el nicho específico de un proyecto' and 'inyectar conocimientos, regulaciones y estándares únicos del sector' — but coverage is not comprehensive (no specific deliverable or methods named). The imperative 'Actívalo tras definir el nicho' mirrors the accepted 'Use when...' trigger pattern, so no voice penalty applies.

3 / 5

Completeness

Clearly states what it does (analyze niche, inject knowledge/regulations/standards) and gives an explicit when ('Actívalo tras definir el nicho'), but the when is a single brief condition that could be more specific with concrete trigger phrases.

4 / 5

Trigger Term Quality

Contains relevant keywords a user might say ('nicho', 'regulaciones', 'estándares', 'sector') but misses common synonyms and variations a user would naturally use ('industria', 'vertical', 'compliance', 'normativa').

3 / 5

Distinctiveness Conflict Risk

The Andru.ia Domain Intelligence niche with a sector/regulations focus is mostly distinct, though it carries minor overlap risk with related Andru.ia skills like @00-andruia-consultant and @ui-ux-pro-max referenced in the body.

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.

Validation15 / 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.