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.
32
27%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/antigravity-awesome-skills-claude/skills/20-andruia-niche-intelligence/SKILL.mdQuality
Discovery
35%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 provides a moderate level of specificity about what the skill does (analyzing niches, injecting sector-specific knowledge and regulations) but falls short on trigger term quality and completeness. It uses branded/internal terminology ('Andru.ia') and lacks natural user-facing keywords that would help Claude reliably select this skill from a large pool. The 'when' clause is present but too vague to serve as effective trigger guidance.
Suggestions
Add natural trigger terms users would actually say, such as 'industry regulations', 'sector standards', 'compliance requirements', 'market niche analysis', 'domain expertise'.
Expand the 'Use when...' clause with explicit scenarios, e.g., 'Use when the user asks about industry-specific regulations, sector standards, compliance requirements, or needs domain knowledge injected into their project.'
List more concrete actions the skill performs, such as 'identifies applicable regulations, maps industry standards, provides sector-specific terminology and best practices'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain ('Domain Intelligence Strategist') and describes some actions ('analyzes the specific niche', 'inject knowledge, regulations, and standards'), but lacks concrete, enumerable actions like listing specific deliverables or outputs. | 2 / 3 |
Completeness | The 'what' is partially addressed (analyzes niche, injects sector knowledge/regulations/standards), and there is a brief 'when' clause ('Actívalo tras definir el nicho'), but the trigger guidance is vague and not tied to explicit user-facing scenarios or keywords. | 2 / 3 |
Trigger Term Quality | The description lacks natural keywords a user would say. Terms like 'estratega de inteligencia de dominio' and 'inyectar conocimientos' are not phrases users would naturally use when seeking this skill. Missing common trigger terms like 'industry analysis', 'sector regulations', 'compliance', 'market research', etc. | 1 / 3 |
Distinctiveness Conflict Risk | The description is somewhat specific to domain/niche analysis and sector standards, which narrows its scope, but terms like 'analyzes the specific niche' and 'inject knowledge' are broad enough to potentially overlap with other research or strategy skills. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
20%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is essentially a persona description and abstract process outline rather than actionable guidance. It lacks any concrete examples, output templates, or executable steps that would help Claude actually produce domain intelligence dossiers. The content is verbose with motivational language and redundant sections while providing minimal practical value.
Suggestions
Replace abstract descriptions with a concrete example: show a complete sample 'Dossier de Inteligencia' for one niche (e.g., Fintech) with the exact output format/schema Claude should produce.
Remove the self-description paragraph and duplicate 'When to Use' sections to reduce verbosity by ~30%.
Add a concrete output template or JSON/markdown schema for the dossier deliverable so Claude knows exactly what structure to produce.
Add validation criteria: how should Claude verify the accuracy of regulatory information, and what should it do when uncertain about a specific regulation?
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is verbose and explains concepts Claude already knows. It includes unnecessary self-description ('Soy el Estratega de Inteligencia de Dominio'), redundant 'When to Use' sections (appears twice), motivational language ('Estándar de Diamante', 'Expertise Real'), and persona-building fluff that wastes tokens without adding actionable value. | 1 / 3 |
Actionability | The skill provides no concrete code, commands, templates, or executable examples. It describes what to analyze and what to deliver at a high level ('Generar un informe especializado') but never shows a concrete output format, schema, or example dossier. Everything remains abstract and descriptive rather than instructive. | 1 / 3 |
Workflow Clarity | There is a two-phase workflow (Analysis → Dossier delivery) with listed sub-steps, providing some sequence. However, there are no validation checkpoints, no feedback loops, no concrete criteria for when each phase is complete, and no error recovery guidance. | 2 / 3 |
Progressive Disclosure | The content references other skills (@00-andruia-consultant, @ui-ux-pro-max, @security-review) showing awareness of a broader system, but there are no bundle files, no linked detailed references, and the content is somewhat monolithic with redundant sections (duplicate 'When to Use') rather than being cleanly organized. | 2 / 3 |
Total | 6 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- sickn33/antigravity-awesome-skills
- Commit
22710e9
- 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.