CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

product-analytics-setup

How to actually instrument product analytics correctly. Event taxonomy, property design, naming conventions, schema versioning, identity stitching, funnel design, retention cohorts, North Star metric selection, dashboard hygiene, instrumentation debt, and the failure modes that produce data nobody trusts. Triggers on product analytics setup, event taxonomy, tracking plan, instrumentation, schema versioning, North Star metric, retention cohorts, funnel design, naming conventions, instrument new feature, audit existing analytics, dashboard reconciliation, instrumentation debt, Mixpanel setup, Amplitude setup, PostHog setup, warehouse-native analytics. Also triggers when the team has data but cannot trust it, or when designing instrumentation for a new feature, or when auditing an existing setup that has drifted.

Quality

84%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

82%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, highly actionable instruction skill: concrete defaults and named patterns throughout, a dependency-ordered 12-step framework with a defined tracking-plan deliverable, and clean one-level-deep progressive disclosure. The two real defects are a dangling reference to a nonexistent retention-patterns file and mild duplication between the frontmatter triggers, the 'When to use' paragraph, and the framework recap.

Suggestions

Fix the dangling reference: either add references/retention-measurement-patterns.md to the bundle (and to the Reference files list) or fold its detail into an existing reference such as cohort-definition-patterns.md, so the Retention measurement section's link resolves.

Trim duplication for conciseness: drop the 'When to use this skill' paragraph (it repeats the frontmatter description's triggers) and compress the 12-consideration framework into a short checklist of one-line pointers instead of restating each section.

Add an explicit validation checkpoint to the framework workflow, e.g., a final step "Review the completed tracking plan against all 12 considerations and reconcile any gaps before publishing," giving the primary workflow a verify-before-ship loop.

DimensionReasoningScore

Conciseness

The body is dense with skill-specific judgment Claude cannot be assumed to hold ("Thirty to fifty events is the sweet spot", "bracket retention is the right default", "Keep old events firing during the transition (90 days is typical)", "one NSM, three to five input metrics, five to ten health metrics"), so it is well above anchor 3. It falls short of anchor 5's 'every token earns its place' because of two redundant stretches: the "When to use this skill" paragraph repeats the frontmatter trigger list, and the 12-consideration framework section recapitulates the preceding ten sections nearly verbatim. These are minor trims, matching anchor 4.

4 / 5

Actionability

For an instruction-only skill the guidance is fully concrete and immediately usable: exact event name formats ("checkout_completed, not checkout_complete"), type rules ("Timestamps in ISO 8601, always", booleans for two-value flags), a step-by-step breaking-change migration pattern, named funnel/cohort shapes with time windows, a numbered 12-step framework, and a defined deliverable ("The output of the framework is a tracking plan"). Per the code-vs-instruction scoring note, the absence of code is not penalized, and the specificity here covers the common cases, matching the top anchor.

5 / 5

Workflow Clarity

The framework provides a clear, dependency-ordered sequence ("The discipline is bottom-up" — events, properties, naming, versioning, identity, funnels, cohorts, retention, North Star, dashboards, debt, single source of truth) with a defined output and verification cadence via quarterly audits and the gap-stating protocol, which fits anchor 4's 'clear sequence with most checkpoints present'. It is not anchor 5 because the primary workflow has no explicit validate-then-proceed checkpoint (e.g., reviewing the finished tracking plan against the 12 considerations before shipping), though the absence of destructive/batch operations means the anchor-3 cap does not apply.

4 / 5

Progressive Disclosure

Structure is good: ten concise overview sections each defer detail to a one-level-deep reference file, the final Reference files section lists each with a one-line scope description, all references are a single level deep, and no bundle file points to further files. However, the Retention measurement section cites "references/retention-measurement-patterns.md", which does not exist in the bundle and is absent from the Reference files list — a dangling link that breaks navigation for that section. That is anchor 4's 'minor organization gaps' rather than anchor 5's 'easy navigation', and well above anchor 3 since 9 of 10 cited files are real, clearly signaled, and appropriately split.

4 / 5

Total

17

/

20

Passed

Description

83%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 comprehensive, trigger-rich description that clearly answers both what the skill does and when to use it, with concrete tool names and problem-state triggers. The only weakness is minor overlap risk with adjacent analytics-strategy skills on metric/dashboard terms, since the boundary clarification is not carried into the description itself.

DimensionReasoningScore

Specificity

The description opens with a concrete capability statement ("How to actually instrument product analytics correctly") and enumerates eleven specific capabilities: "Event taxonomy, property design, naming conventions, schema versioning, identity stitching, funnel design, retention cohorts, North Star metric selection, dashboard hygiene, instrumentation debt, and the failure modes that produce data nobody trusts." This matches the anchor for multiple specific concrete capabilities with comprehensive coverage; it exceeds anchor 4 because there are no meaningful gaps in domain coverage, and nothing is vague or padded fluff.

5 / 5

Completeness

Both halves are explicit: the 'what' is the concrete capability list, and the 'when' is stated twice with concrete trigger phrases — "Triggers on product analytics setup, event taxonomy, tracking plan..." and "Also triggers when the team has data but cannot trust it, or when designing instrumentation for a new feature, or when auditing an existing setup that has drifted." This mirrors the anchor-5 exemplar (what + explicit use-when with concrete triggers) exactly, so it cannot be capped at 3 or fit anchor 4's weaker 'when'.

5 / 5

Trigger Term Quality

Seventeen explicit trigger terms including natural user phrases ("product analytics setup", "tracking plan", "instrument new feature", "audit existing analytics", "dashboard reconciliation"), tool names users would naturally say ("Mixpanel setup, Amplitude setup, PostHog setup"), and colloquial problem statements ("when the team has data but cannot trust it"). Coverage is comprehensive with synonyms; no common variation of the domain is missing, matching the top anchor rather than anchor 4's 'a few natural terms missing'.

5 / 5

Distinctiveness Conflict Risk

The niche is clear and most triggers are strongly specific ("tracking plan", "event taxonomy", "Mixpanel setup", "instrumentation debt"), so it exceeds anchor 3's residual overlap. However, terms like "North Star metric", "dashboard hygiene", and "retention cohorts" plausibly overlap with a closely related analytics-strategy skill in the same catalog, and the description itself does not state that boundary (the strategy-vs-execution distinction lives in the body, not the description). That is exactly anchor 4's 'mostly distinct; minor overlap risk with closely related skills', not anchor 5's minimal conflict risk.

4 / 5

Total

19

/

20

Passed

Validation

81%

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

Validation — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

relative_links

Relative link issues: 1 missing

Warning

referenced_paths_exist

Referenced path issues: 2 missing

Warning

Total

13

/

16

Passed

Repository

rampstackco/claude-skills

Path

skills/product-analytics-setup/SKILL.md

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.