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

96%

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

92%Weight 40%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is dense, actionable, and well-sequenced with explicit completion evidence and handoffs. Its only real weakness is progressive disclosure: a single monolithic file over 50 lines with no bundle to offload the frameworks/anti-patterns reference material.

Suggestions

Move the Frameworks uteis (AARRR/HEART) and Anti-padroes frequentes sections into a references/ file (e.g. references/frameworks.md) and link to it from SKILL.md, so the core overview stays lean and one level deep.

Create and bundle templates/analytics-plan.md (currently only referenced by path) so the cited handoff template actually exists in the skill bundle and is clearly signaled.

Consider splitting the Convencao de naming + Tracking plan tables into a references/naming-and-tracking-plan.md reference, keeping SKILL.md as the overview pointing to detailed material.

Dimension	Reasoning	Score
Conciseness	Lean, table-driven guidance that assumes Claude's competence (naming table, tracking-plan table, terse rules) without padding basic concepts; the only flourish ("aposta sem placar") is brief and mnemonic, so it earns score 3 rather than the mostly-efficient-but-padded 2.	3 / 3
Actionability	Provides copy-paste-ready specifics: a tracking-plan table with event/trigger/properties/owner, a bom-vs-ruim naming table, concrete rules (server-side for conversion events, _v2 on rename, snake_case properties), and a worked funnel with drop percentages — fully executable guidance.	3 / 3
Workflow Clarity	Clear input→output→evidence→handoff sequence with an explicit completion checkpoint ("Evidencia de Conclusao") and a verification gate inherited from verification-before-completion ("instrumentado exige prova: aparece no debugger/live events"); not 2 because validation is explicit rather than implicit.	3 / 3
Progressive Disclosure	Well-organized single-file body (~110 lines) with clear sections, but everything is inline and no bundle files exist (references/, scripts/, assets/ absent); the body references external governance docs (policies/, templates/) that are not part of this skill's bundle, so it stays monolithic rather than score-3 one-level-deep references.	2 / 3
	Total	11 / 12 Passed

Description

100%Weight 40%Scale 1-3

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 is concise, third-person, and explicitly covers both capability and trigger conditions with a rich set of natural keywords including vendor names. It is a strong, low-conflict skill description.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — "definicao de eventos, naming de tracking, funis, metricas de produto e instrumentacao analitica" — matching the anchor for naming several specific concrete actions rather than vague domain labels.	3 / 3
Completeness	Explicitly answers both what it does and when to use it via "Use quando precisar medir..." and a dedicated "Trigger em:" clause, matching the clear-what-and-when anchor; not 2 because the when is explicit, not implied.	3 / 3
Trigger Term Quality	Broad natural-phrase coverage ("tracking", "analytics", "funil de conversao", "instrumentar evento", "tracking plan", "data analytics") plus tool names a user would actually say ("PostHog", "Amplitude", "Mixpanel"), satisfying the good-coverage anchor; not score 2 because common variations are not missing.	3 / 3
Distinctiveness Conflict Risk	Niche is clearly product-analytics instrumentation with distinct tool-named triggers, unlikely to fire for adjacent skills (observabilidade/SEO are explicitly excluded in the body); not 2 because the triggers are specific enough to avoid overlap.	3 / 3
	Total	12 / 12 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: 030ef22

Reviewed: 8 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.