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.

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

100%

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

A dense, well-structured instruction skill that covers a four-layer framework, a sequenced workflow with validation, failure patterns, and a concrete output template, with detail appropriately offloaded to one reference file.

Dimension	Reasoning	Score
Conciseness	Lean, bullet-dense content that assumes Claude's competence and avoids explaining basics Claude already knows; every section earns its place with minimal editorial padding.	3 / 3
Actionability	Concrete, specific guidance throughout — verb+noun snake_case naming conventions (signed_up, created_project), a dashboard-type table, attribution model definitions, and a copy-paste markdown tracking-plan output template.	3 / 3
Workflow Clarity	A clearly sequenced 9-step workflow with validation checkpoints ("Audit existing tracking", "Test each event. Verify properties. Catch issues in staging"), so it is not capped at 2 for missing verification.	3 / 3
Progressive Disclosure	Well-organized body with clear sections and a single clearly-signaled one-level-deep reference (references/event-taxonomy-template.md, verified present) that holds the detailed event catalog.	3 / 3
	Total	12 / 12 Passed

Description

100%

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 well-crafted description that clearly states capabilities, provides extensive natural trigger terms, and uses third-person voice with an explicit 'Use when' clause. It distinguishes the skill's niche effectively.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — "event taxonomy, KPI hierarchy, dashboard architecture, attribution models, and analytics implementation strategy" — matching the anchor for naming several specific capabilities.	3 / 3
Completeness	Explicitly answers both what ("Design measurement frameworks including...") and when ("Use this skill whenever the user wants to...") with concrete triggers; not capped at 2 because the 'Use when' clause is present.	3 / 3
Trigger Term Quality	Strong coverage of natural terms users would say: "plan analytics, design dashboards, build event taxonomies, define KPIs, set up tracking, audit existing measurement" plus "north star metric, attribution model, GA4 setup, Mixpanel setup."	3 / 3
Distinctiveness Conflict Risk	Clear measurement-planning niche with distinct triggers (event taxonomy, KPI framework, attribution model) unlikely to collide with adjacent CRO or SEO skills.	3 / 3
	Total	12 / 12 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: rampstackco/claude-skills
Commit: f1bc195

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