data-analytics
Skill para definicao de eventos, naming de tracking, funis, metricas de produto e instrumentacao analitica. Use quando precisar medir valor entregue, ativacao, conversao, retencao e comportamento do usuario.
67
Quality
58%
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/21-data-analytics/SKILL.mdQuality
Discovery
67%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This description has a solid structure with both 'what' and 'when' clauses, demonstrating good completeness. However, it relies on somewhat abstract category names rather than concrete actions, and the trigger terms could be expanded to include more natural user language variations and common analytics tool names.
Suggestions
Add more concrete actions like 'define event schemas', 'create tracking plans', 'design funnel specifications', 'generate instrumentation documentation' to improve specificity.
Expand trigger terms to include common variations users might say: 'analytics', 'product metrics', 'user behavior tracking', 'event tracking', and potentially tool names like 'Amplitude', 'Mixpanel', 'Segment'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (product analytics/tracking) and lists some actions like 'definicao de eventos, naming de tracking, funis, metricas de produto e instrumentacao analitica', but these are somewhat abstract categories rather than concrete specific actions like 'create event schemas' or 'generate tracking code'. | 2 / 3 |
Completeness | Clearly answers both what (event definition, tracking naming, funnels, product metrics, analytical instrumentation) AND when ('Use quando precisar medir valor entregue, ativacao, conversao, retencao e comportamento do usuario') with explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes relevant domain terms like 'tracking', 'funis', 'metricas', 'ativacao', 'conversao', 'retencao', but misses common variations users might say such as 'analytics', 'product metrics', 'user tracking', 'event tracking', or tool-specific terms like 'Amplitude', 'Mixpanel'. | 2 / 3 |
Distinctiveness Conflict Risk | Focuses on product analytics which is a specific niche, but terms like 'metricas' and 'comportamento do usuario' could overlap with general data analysis or UX research skills. The focus on 'instrumentacao analitica' helps distinguish it somewhat. | 2 / 3 |
Total | 9 / 12 Passed |
Implementation
50%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is well-structured and concise but lacks actionable content. It reads more like a checklist of considerations than a skill that teaches Claude how to actually define events, create tracking plans, or design funnels. The absence of concrete examples (event naming conventions, sample tracking plans, funnel templates) significantly limits its utility.
Suggestions
Add concrete event naming examples: 'button_clicked', 'form_submitted', 'checkout_completed' with property schemas showing required vs optional fields
Include a sample analytics plan or funnel definition showing the expected output format
Add a step-by-step workflow: 1. Identify user journey → 2. Map decision points → 3. Define events → 4. Validate with stakeholder → 5. Document in template
Provide specific examples of good vs bad event naming to make the 'verbo + objeto' guideline actionable
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, using bullet points and short phrases. No unnecessary explanations of concepts Claude would already know. Every section serves a clear purpose. | 3 / 3 |
Actionability | The skill provides abstract guidance without concrete examples. No executable code, no specific event naming patterns, no example tracking plans or event schemas. Phrases like 'evento nomeado com verbo + objeto' describe rather than demonstrate. | 1 / 3 |
Workflow Clarity | The checklist provides a sequence of considerations, but lacks explicit step-by-step workflow with validation checkpoints. No clear process for how to go from inputs to outputs, no feedback loops for verifying the analytics plan is correct. | 2 / 3 |
Progressive Disclosure | References external policies and templates appropriately, but the skill itself lacks concrete content to warrant the references. The main content is too thin - it points to other files without providing sufficient standalone value in the overview. | 2 / 3 |
Total | 8 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- felvieira/claude-skills-fv
- Commit
524725e
- 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.