analytics-tracking

When the user wants to set up, improve, or audit analytics tracking and measurement. Also use when the user mentions "set up tracking," "GA4," "Google Analytics," "conversion tracking," "event tracking," "UTM parameters," "tag manager," "GTM," "analytics implementation," or "tracking plan." For A/B test measurement, see ab-test-setup.

Quality

75%

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

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/analytics-tracking/SKILL.md

Quality

Content

61%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 well-structured, mostly actionable overview with real reference files for deeper material and concrete code examples. Its weaknesses are the lack of an explicit end-to-end workflow with validation feedback loops (important for batch tracking changes) and some restate-the-obvious principles that dilute token efficiency.

Suggestions

Add an ordered end-to-end implementation workflow with explicit validation checkpoints (e.g., draft plan -> implement -> validate in GA4 DebugView/GTM Preview -> fix -> confirm conversions), since tracking is a batch operation that benefits from a validate-fix-retry loop.

Trim or remove the 'Core Principles' section and the generic 'Best Practices' bullet lists, which restate analytics common sense Claude already knows, to improve token efficiency.

Move the inline 'Essential Events' marketing/product tables fully into references/event-library.md to avoid duplication and keep the overview lean.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with tables and code, but the 'Core Principles' section ('Track for Decisions, Not Data', 'Quality > quantity of events') and 'Best Practices' lists restate analytics common sense Claude already knows, and several short table-heavy sections could be tightened or consolidated.	3 / 5
Actionability	Provides concrete executable examples (gtag('event', ...) snippet, dataLayer.push pattern, UTM parameter table, validation checklist) with only minor gaps such as the GA4 'Quick Setup' being high-level steps without exact commands.	4 / 5
Workflow Clarity	Sequences exist (Initial Assessment questions, GA4 Quick Setup steps, Debugging checklist) but there is no end-to-end ordered workflow with explicit validation checkpoints; because tracking implementation is a batch/risky operation, the missing validate-then-fix feedback loop caps this at 3.	3 / 5
Progressive Disclosure	Good structure with a clear overview body that points to three real one-level-deep references (event-library.md, ga4-implementation.md, gtm-implementation.md), each clearly signaled with bold lead-ins; minor gaps such as the tool-integration links and the inline 'Essential Events' tables that partly duplicate the event library.	4 / 5
	Total	14 / 20 Passed

Description

90%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 well-crafted: it states concrete actions, provides comprehensive natural trigger terms including synonyms, explicitly answers both 'what' and 'when', and includes boundary guidance to avoid conflict with adjacent skills. It is concise without padding.

Dimension	Reasoning	Score
Specificity	Names the domain and three concrete actions ('set up, improve, or audit analytics tracking and measurement'), giving several specific actions with only minor gaps in coverage rather than a fully exhaustive granular list.	4 / 5
Completeness	Explicitly answers both what ('set up, improve, or audit analytics tracking and measurement') and when ('Also use when the user mentions...') with concrete trigger phrases, matching the top anchor.	5 / 5
Trigger Term Quality	Comprehensive coverage of natural terms including synonyms and product names ('set up tracking', 'GA4', 'Google Analytics', 'conversion tracking', 'event tracking', 'UTM parameters', 'tag manager', 'GTM', 'analytics implementation', 'tracking plan') that users would actually say.	5 / 5
Distinctiveness Conflict Risk	Occupies a clear niche with distinct analytics-specific triggers and adds explicit boundary guidance ('For A/B test measurement, see ab-test-setup'), minimizing overlap with related skills.	5 / 5
	Total	19 / 20 Passed

Validation

87%

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

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
relative_links	Relative link issues: 6 suspicious	Warning

	Total	14 / 16 Passed

Repository: TheCraigHewitt/seomachine
Path: .claude/skills/analytics-tracking/SKILL.md
Commit: e818d5e

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