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.
41
27%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./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 communicates a general idea of domain-specific intelligence analysis but relies on abstract, jargon-heavy language that lacks concrete actions and natural trigger terms. The 'when' clause is present but procedural rather than intent-based, and the description uses second person voice ('Actívalo') which is penalized. It would benefit significantly from concrete examples of outputs and natural language trigger terms.
Suggestions
Replace abstract language like 'inyectar conocimientos' with concrete actions such as 'identifica regulaciones aplicables, estándares de la industria, y mejores prácticas del sector'.
Add natural trigger terms users would actually say, e.g., 'Use when the user mentions industry regulations, sector standards, compliance requirements, domain expertise, or market-specific knowledge'.
Rewrite the 'when' clause from procedural second person ('Actívalo tras definir el nicho') to third person with explicit triggers, e.g., 'Se activa cuando el proyecto tiene un nicho definido y se necesita análisis de regulaciones, normativas o estándares sectoriales'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain ('Estratega de Inteligencia de Dominio') and describes some actions ('Analiza el nicho específico', 'inyectar conocimientos, regulaciones y estándares'), but the actions remain somewhat abstract—what does 'inyectar conocimientos' concretely produce? It lacks specific deliverables or concrete outputs. | 2 / 3 |
Completeness | It answers 'what' (analyzes the specific niche to inject domain knowledge, regulations, and standards) and has a brief 'when' ('Actívalo tras definir el nicho'), but the trigger guidance is procedural rather than based on user intent or natural language triggers. The 'when' clause uses second person ('Actívalo') which is more of an instruction than a selection criterion. | 2 / 3 |
Trigger Term Quality | The description uses specialized jargon like 'Inteligencia de Dominio' and 'nicho específico' which are not natural terms a user would say. There are no common user-facing trigger terms like 'industry analysis', 'regulations', 'compliance', or 'sector research' that would help match user queries. | 1 / 3 |
Distinctiveness Conflict Risk | The concept of 'domain intelligence' is somewhat distinctive, but the description is broad enough ('analiza el nicho', 'conocimientos del sector') that it could overlap with any skill related to research, industry analysis, or compliance. The branding ('Andru.ia') helps slightly but doesn't clarify the functional niche. | 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 role-playing prompt rather than actionable technical guidance. It lacks any concrete examples, output templates, or executable steps—it tells Claude to 'sound like a consultant with 20 years of experience' and 'generate a specialized report' without showing what that report looks like. The content is verbose with motivational language and duplicate sections that waste tokens.
Suggestions
Add a concrete example dossier output (even abbreviated) showing the exact structure and level of detail expected for a specific niche like 'Clínicas Dentales', so Claude knows the target format.
Remove the duplicate 'When to Use' sections and the 'Descripción' identity paragraph—these waste tokens on information Claude doesn't need to perform the task.
Replace abstract instructions like 'Generar un informe especializado' with a specific template or schema (e.g., markdown headings with expected content types and lengths for each section).
Add validation steps: how should Claude verify that identified regulations are current and applicable, and what should happen if the niche is ambiguous or spans multiple sectors?
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is verbose and repetitive, with two separate 'When to Use' sections, unnecessary emoji decoration, and extensive explanation of concepts Claude already understands (what Chain of Thought is, what niches are). The 'Descripción' section explains the skill's identity in a way that wastes tokens. Phrases like 'Estándar de Diamante' and 'Expertise Real' are motivational fluff rather than actionable guidance. | 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. The guidance is entirely 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 for verifying the quality or accuracy of the generated intelligence, and no concrete criteria for when each phase is complete. | 2 / 3 |
Progressive Disclosure | The content references other skills (@00-andruia-consultant, @ui-ux-pro-max, @security-review) which shows some awareness of cross-referencing, but the main content is a monolithic block with no links to detailed reference files. The duplicate 'When to Use' sections and inline 'Reglas de Oro' could be better 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
1a9f5ac
- 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.