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.

50

Quality

55%

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 ./plugins/agentic-awesome-skills-claude/skills/20-andruia-niche-intelligence/SKILL.md

The canonical home for this skill is 20-andruia-niche-intelligence in sickn33/agentic-awesome-skills

SKILL.md
Quality
Evals
Security

Quality

Content

53%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, instruction-only skill that organizes a domain-intelligence dossier workflow clearly, but it relies on persona language and abstract direction rather than concrete, executable output guidance and validation steps.

Suggestions

Trim persona/branding prose ("Soy el Estratega", "despertar", "inyecto sabiduría") and merge the two 'When to Use' sections into one to improve token efficiency.

Add a concrete sample 'Dossier de Inteligencia' output (with section headings and one filled example for a niche like Fintech) so Claude has a copy-ready template rather than category labels alone.

Insert a validation/quality checkpoint in FASE 2 (e.g., verify each named regulation applies to the identified niche before delivering the dossier) to lift workflow clarity above 3.

DimensionReasoningScore

Conciseness

The body is mostly efficient but carries persona fluff ("Soy el Estratega", "Mi propósito es 'despertar'", "inyecto sabiduría específica") and a duplicated 'When to Use' section that could be tightened without losing meaning.

3 / 5

Actionability

It lists concrete dossier categories (Stack de Industria, Cumplimiento y Normativa, UX de Nicho) and names real regulations (RGPD, HIPAA, DIAN), but gives no concrete output structure or sample dossier; the Example section shows only the user request with no model output.

3 / 5

Workflow Clarity

A two-phase flow (Análisis de Dominio → Entrega del Dossier) with reasoning questions is sequenced, but there are no validation or quality-check checkpoints; this caps at 3 even though the task is non-destructive.

3 / 5

Progressive Disclosure

A single ~75-line file is well-sectioned into Descripción, Instrucciones, Flujo de Trabajo, Reglas de Oro, Relaciones, and Limitations with no external references needed; the only gap is the duplicated When-to-Use content.

4 / 5

Total

13

/

20

Passed

Description

57%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 reasonably clear, domain-specific description that states both capability and activation timing, but it leans on abstract phrasing and a second-person imperative rather than crisp third-person action verbs and concrete trigger terms.

Suggestions

Rewrite in third person (e.g., "Analyzes the project niche and injects sector-specific regulations and standards") and drop the imperative "Actívalo" to avoid the voice penalty.

Add concrete trigger phrases a user would naturally say, e.g., "Use when the project's market niche is defined and you need sector regulations, standards, or UX patterns (Fintech, HealthTech, EdTech)."

Replace abstract wording like "inyectar conocimientos" with specific deliverables (e.g., "produces a domain dossier covering regulatory compliance, industry stack, and niche UX patterns").

DimensionReasoningScore

Specificity

The description names the domain and a few actions ("Analiza el nicho específico... para inyectar conocimientos, regulaciones y estándares"), but the actions are abstract ('inject knowledge'). The closing "Actívalo" is second-person imperative, triggering the −1 voice penalty from a base of 3.

2 / 5

Completeness

It answers both 'what' (analyze niche, inject sector knowledge/regulations/standards) and 'when' ("Actívalo tras definir el nicho"), but the 'when' lacks concrete trigger phrases, keeping it below a 5.

4 / 5

Trigger Term Quality

"Actívalo tras definir el nicho" plus terms like nicho, regulaciones, and estándares give some relevant keywords, but common natural variations or synonyms a user would actually say are missing.

3 / 5

Distinctiveness Conflict Risk

The Andru.ia domain-intelligence strategist role is a clear, distinct niche with specific triggers; only minor overlap risk with adjacent consulting skills.

4 / 5

Total

13

/

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.