CtrlK
BlogDocsLog inGet started
Tessl Logo

analytics-strategy

Design measurement frameworks including event taxonomy, KPI hierarchy, dashboard architecture, attribution models, and analytics implementation strategy. Use this skill whenever the user wants to plan analytics, design dashboards, build event taxonomies, define KPIs, set up tracking, or audit existing measurement. Triggers on analytics strategy, measurement plan, event taxonomy, tracking plan, KPI framework, dashboard design, north star metric, attribution model, conversion tracking, GA4 setup, Mixpanel setup, analytics audit. Also triggers when the user has data but no clear way to use it, or wants to make decisions but doesn't know what to track.

73

Quality

91%

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.

The body is a strong, actionable analytics-strategy framework with concrete naming standards, a tracking-plan template, and a sequenced workflow. It is slightly held back by a few explanations of concepts Claude already knows and implicit rather than explicit validation checkpoints.

Suggestions

Trim concept explanations Claude already knows (e.g., the 'AARRR/pirate metrics' aside and the per-model attribution definitions) to tighten conciseness.

Make workflow validation explicit with feedback loops — e.g., after 'Implement with care', add an explicit 'Validate each event in staging → fix → re-validate before building dashboards' checkpoint.

Consider splitting the detailed attribution-model and dashboard-type reference material into a separate referenced file to keep SKILL.md a leaner overview.

DimensionReasoningScore

Conciseness

Mostly efficient, information-dense guidance, but includes a few explanations of concepts Claude already knows (the AARRR/pirate-metrics aside and one-line definitions of each attribution model) that could be trimmed.

4 / 5

Actionability

Highly actionable for an instruction-only skill: concrete event-naming rules (verb+noun, snake_case, past tense), property examples, and a copy-paste-ready output template with sample catalog rows covering common cases.

5 / 5

Workflow Clarity

A clear 9-step sequence with a validation checkpoint in step 6 ('Test each event. Verify properties. Catch issues in staging'), though most other checkpoints are implicit rather than explicit validate→fix→retry loops.

4 / 5

Progressive Disclosure

Well-organized into clear sections with one real, well-signaled one-level-deep reference (references/event-taxonomy-template.md, verified to exist); minor gaps in that some detailed inline material could optionally be split out.

4 / 5

Total

17

/

20

Passed

Description

100%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.

The description is exemplary: third-person voice, comprehensive concrete capabilities, explicit 'Use when' trigger guidance, and a rich set of natural trigger terms including tool names. It cleanly answers what the skill does and when to invoke it with minimal conflict risk.

DimensionReasoningScore

Specificity

Lists multiple concrete capabilities — 'event taxonomy, KPI hierarchy, dashboard architecture, attribution models, and analytics implementation strategy' — giving comprehensive, specific coverage rather than vague abstraction.

5 / 5

Completeness

Explicitly answers both 'what' (design measurement frameworks including...) and 'when' via an explicit 'Use this skill whenever the user wants to plan analytics...' trigger clause, plus secondary trigger conditions.

5 / 5

Trigger Term Quality

Comprehensive natural-term coverage including synonyms and tool names — 'plan analytics, design dashboards, build event taxonomies... north star metric, attribution model, conversion tracking, GA4 setup, Mixpanel setup, analytics audit' — matching phrases users actually say.

5 / 5

Distinctiveness Conflict Risk

Occupies a clear analytics-strategy niche with distinct, specific triggers (north star metric, tracking plan, attribution model) and minimal overlap with adjacent skills it explicitly defers to.

5 / 5

Total

20

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

Repository
rampstackco/claude-skills
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.