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.
55
44%
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.
The description covers a clear product analytics instrumentation domain with an explicit 'Use quando' trigger clause, which is a strength. However, the capabilities listed are somewhat categorical rather than concretely actionable, and the trigger terms could be broader to capture more natural user phrasings. The description is functional but could be more specific in its actions and more distinctive in its niche.
Suggestions
Replace category labels with concrete actions, e.g., 'Define event schemas, create tracking naming conventions, design conversion funnels, specify product KPIs, and generate instrumentation plans'.
Add more natural trigger terms and variations users might say, such as 'analytics plan', 'event taxonomy', 'tracking plan', 'Mixpanel', 'Amplitude', 'GA4', or 'product KPIs'.
| 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 more category labels than concrete specific actions (e.g., doesn't say 'create event schemas' or 'generate tracking plans'). | 2 / 3 |
Completeness | Clearly answers both 'what' (event definition, tracking naming, funnels, product metrics, analytical instrumentation) and 'when' with an explicit 'Use quando' clause specifying triggers like measuring delivered value, activation, conversion, retention, and user behavior. | 3 / 3 |
Trigger Term Quality | Includes relevant keywords like 'eventos', 'tracking', 'funis', 'metricas de produto', 'ativacao', 'conversao', 'retencao', but misses common variations users might say such as 'analytics plan', 'event taxonomy', 'KPIs', 'product metrics', 'Mixpanel', 'Amplitude', or English equivalents that could broaden matching. | 2 / 3 |
Distinctiveness Conflict Risk | The domain of product analytics instrumentation is fairly specific, but terms like 'metricas de produto' and 'comportamento do usuario' could overlap with general product management or UX research skills. The focus on tracking naming and event definition helps narrow it, but it's not fully distinct. | 2 / 3 |
Total | 9 / 12 Passed |
Implementation
22%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill reads more like a meta-template or checklist stub than an actionable skill. It lacks concrete examples of event naming conventions, funnel definitions, or tracking plans that would make it immediately useful. The content tells Claude what categories of things to produce but never shows how to produce them, severely limiting its practical value.
Suggestions
Add a concrete example of an event naming convention with at least 2-3 sample events (e.g., `user_signed_up`, `checkout_completed`) including their properties and expected values.
Include a worked example of a funnel definition tied to a business objective, showing the step-by-step mapping from user flow to tracked events to success metric.
Define a clear sequential workflow: e.g., 1) Identify business objective → 2) Map user flow → 3) Define events with naming schema → 4) Validate against checklist → 5) Produce handoff document.
Add a concrete analytics plan template inline (or a meaningful snippet) rather than only referencing `templates/analytics-plan.md`, so the skill is usable even without the external file.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Reasonably concise with bullet-point structure, but includes some sections that are somewhat generic (e.g., 'Quando Usar' / 'Quando Nao Usar' lists are fairly obvious). The governance references add overhead without actionable detail. | 2 / 3 |
Actionability | The skill provides no concrete code, commands, naming conventions, event schemas, or executable examples. It describes what should be done at a high level ('evento nomeado com verbo + objeto') but never shows a concrete event definition, naming pattern, or funnel mapping example. | 1 / 3 |
Workflow Clarity | There is no sequenced workflow or multi-step process described. The checklist and evidence sections list outcomes but don't define a clear order of operations, validation checkpoints, or feedback loops for the analytics instrumentation process. | 1 / 3 |
Progressive Disclosure | References to external files like `policies/handoffs.md` and `templates/analytics-plan.md` are present and one-level deep, which is good. However, the main content is thin and doesn't provide enough substance in the overview itself to make the references meaningful — the skill essentially defers all real content to external files without giving a usable quick-start. | 2 / 3 |
Total | 6 / 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
e9f6648
- 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.