CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

20-andruia-niche-intelligence

Usar tras definir el sector de un proyecto: prepara un dossier en español con contexto, normas aplicables, patrones UX y riesgos, distinguiendo fuentes verificadas de hipótesis.

68

Quality

85%

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

SKILL.md
Quality
Evals
Security

Quality

Content

81%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 with a clear three-phase workflow, explicit source-verification checkpoints, and a concrete output template that distinguishes confirmed from pending compliance. The main weaknesses are mild redundancy of verification guidance across sections and an illustrative example that describes the dossier rather than demonstrating it.

Suggestions

Consolidate the overlapping verification guidance from FASE 3, 'Método y formato de fuentes', 'Reglas de Oro' #3, and Limitations into a single verification section to remove repetition.

Replace the abstract Example with one filled dossier row (e.g., RGPD for a Spanish dental clinic: source URL + date, aplicabilidad 'posible', comprobación 'pendiente') so the output format is demonstrated, not just described.

Trim the persona preamble ('Soy el Estratega...') to a single line, since it adds framing but no actionable guidance.

DimensionReasoningScore

Conciseness

The body is dense and instructive with no explanations of concepts Claude already knows, but the persona preamble ('Soy el Estratega de Inteligencia de Dominio...') and verification guidance repeated across FASE 3, 'Método y formato de fuentes', 'Reglas de Oro' #3, and Limitations could be consolidated. It sits above 'mostly efficient with some unnecessary explanation' (3) but short of 'every token earns its place' (5) due to this repetition.

4 / 5

Actionability

Provides a concrete dossier template with explicit columns (requisito, fuente primaria + fecha, aplicabilidad, comprobación) and status values (confirmada/posible/pendiente), plus a worked trigger example. Some analysis steps remain abstract ('analizo los siguientes aspectos y entrego conclusiones breves') and the Example section describes the dossier rather than showing a filled row, keeping it below fully copy-paste-ready guidance (5) but above pseudocode-level gaps (3).

4 / 5

Workflow Clarity

Three clearly sequenced phases with a dedicated verification phase: check each requirement against sector and jurisdiction, open the primary source and check date/version/scope, mark unverifiable norms 'pendiente' instead of inventing them, and correct contradictions before delivering. This is an explicit validate-and-fix-before-deliver feedback loop with the dossier format acting as a checklist — the top anchor for an instruction-only skill; no destructive/batch-operation cap applies.

5 / 5

Progressive Disclosure

A self-contained single-file skill with clear section headers, no nested references, and no content that clearly belongs in a separate bundle file. It falls short of the top anchor only through mild redundancy: verification guidance is spread across four sections (FASE 3, Método, Reglas de Oro, Limitations), which slightly hurts navigation.

4 / 5

Total

17

/

20

Passed

Description

83%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 strong description with an explicit when-clause tied to a distinct pipeline stage and a concrete list of dossier components including the verified-versus-hypothesis distinction. Trigger coverage falls just short of comprehensive because common synonyms like 'nicho' and 'industria' — used elsewhere in the skill itself — are absent.

Suggestions

Add the synonyms 'nicho' or 'industria' to the trigger phrasing, since the body and skill name use 'nicho' but the description only says 'sector'.

Mention the tech-stack recommendation ('stack de industria') alongside contexto, normas, UX y riesgos to fully cover the dossier's deliverables.

DimensionReasoningScore

Specificity

Lists several specific deliverable components — 'dossier en español con contexto, normas aplicables, patrones UX y riesgos' — plus the concrete practice of 'distinguiendo fuentes verificadas de hipótesis'. It stops short of comprehensive coverage because the body's 'Stack de Industria' component is absent, matching 'several specific actions; minor gaps' (4) rather than the top anchor (5).

4 / 5

Completeness

Both what and when are explicit: 'Usar tras definir el sector de un proyecto' is a concrete when-clause, and 'prepara un dossier en español con contexto, normas aplicables, patrones UX y riesgos' states the what with specifics. This matches the top anchor — clearly and explicitly answers both with a concrete trigger condition — rather than anchor 4 where the 'when' is only weakly implied.

5 / 5

Trigger Term Quality

Natural trigger terms are present: 'sector', 'proyecto', 'normas aplicables', 'patrones UX', 'riesgos'. A few common variations are missing — 'nicho' and 'industria' (both used by the skill body itself) and 'cumplimiento/regulación' — which fits 'good keyword coverage; a few natural terms missing' (4) rather than comprehensive synonym coverage (5).

4 / 5

Distinctiveness Conflict Risk

The trigger point (immediately after the project's sector is defined) and the deliverable (a Spanish-language dossier covering norms, UX, and risks with verified-vs-hypothesis distinction) form a clear niche with minimal overlap risk. Minor overlap remains with generic research/analysis skills, matching 'mostly distinct; minor overlap risk' (4).

4 / 5

Total

17

/

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

Path

skills/20-andruia-niche-intelligence/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.