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. Trigger em: "tracking", "analytics", "eventos de produto", "funil de conversao", "instrumentar evento", "metrica de produto", "ativacao", "retencao", "naming de evento", "tracking plan", "data analytics", "PostHog", "Amplitude", "Mixpanel".

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

71%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, actionable instruction skill with concrete templates, naming rules, and a real validation checkpoint. The main gaps are inlined content that could live in reference files and references to bundle files that do not exist.

Suggestions

Move the tracking-plan template and naming reference tables into a references/ file (e.g. references/analytics-plan.md) and link to it from SKILL.md so the overview stays lean.

Either add the referenced templates/analytics-plan.md and policies/*.md to the bundle or remove the dangling references, since progressive_disclosure is scored against the actual bundle structure.

Trim or relocate the AARRR/HEART definitions in 'Frameworks uteis' to a reference, since Claude already knows these frameworks.

Dimension	Reasoning	Score
Conciseness	Mostly lean — tables, naming rules, and concrete examples with little padding — but the 'Frameworks uteis' section briefly defines AARRR/HEART concepts Claude already knows, fitting 'efficient with minor instances of over-explanation'.	4 / 5
Actionability	Provides copy-paste-ready tracking-plan and naming tables plus concrete rules (object_action, server-side for conversion events), but as an instruction skill it stops short of instrumentation code, leaving minor gaps fitting 'mostly executable guidance'.	4 / 5
Workflow Clarity	Includes an explicit validation feedback loop ('disparar a acao -> confirmar no debugger -> se nao aparecer, checar API key/env e disparar de novo') and a clear plan-to-handoff sequence, but the overall flow is not strictly numbered, fitting 'clear sequence with most checkpoints present'.	4 / 5
Progressive Disclosure	All content is inlined in a single ~110-line SKILL.md and it references templates/analytics-plan.md and policies/*.md that are not present in any bundle directory, fitting 'some structure with references not clearly signaled and content that should be separate inline'.	3 / 5
	Total	15 / 20 Passed

Description

96%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: concrete actions, comprehensive natural trigger terms including vendor names, and explicit what/when guidance in third-person voice. Its only weakness is mild breadth in a couple of generic terms that create minor overlap with adjacent analytics-adjacent skills.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'definicao de eventos, naming de tracking, funis, metricas de produto e instrumentacao analitica' — giving comprehensive coverage of the analytics-instrumentation domain, matching the anchor for multiple specific concrete actions.	5 / 5
Completeness	Explicitly answers both 'what' (define eventos/naming/funis/metricas/instrumentacao) and 'when' ('Use quando precisar medir...' plus an explicit 'Trigger em:' list), matching the anchor for clearly answering both what and when with concrete triggers.	5 / 5
Trigger Term Quality	The 'Trigger em:' clause provides comprehensive natural terms including synonyms ('funil de conversao', 'tracking plan', 'data analytics') and tool names users actually say ('PostHog', 'Amplitude', 'Mixpanel'), matching the comprehensive-coverage anchor.	5 / 5
Distinctiveness Conflict Risk	Carves a clear product-analytics niche with distinct tool triggers, but broad terms like 'analytics'/'data analytics' and the body's own carve-outs from observability (skill 20) and revenue (skill 59) leave minor overlap risk, fitting 'mostly distinct' rather than 'minimal conflict'.	4 / 5
	Total	19 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: felvieira/claude-skills-fv
Path: skills/21-data-analytics/SKILL.md
Commit: 74aa7c1

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

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.