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," "tracking plan," "how do I measure this," "track conversions," "attribution," "Mixpanel," "Segment," "are my events firing," or "analytics isn't working." Use this whenever someone asks how to know if something is working or wants to measure marketing results. For A/B test measurement, see ab-test-setup.
89
73%
Does it follow best practices?
Impact
99%
1.11xAverage score across 6 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/analytics-tracking/SKILL.mdQuality
Discovery
89%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a strong description with excellent trigger term coverage and completeness, including an explicit 'Use when' clause with extensive natural-language keywords and tool names. The main weakness is that the 'what' portion could be more specific about concrete actions beyond 'set up, improve, or audit.' The cross-reference to the ab-test-setup skill is a nice touch for disambiguation.
Suggestions
Expand the capability description with more specific concrete actions, e.g., 'Configures GA4 properties, creates tracking plans, implements UTM parameters, debugs event firing, sets up conversion goals in tag managers.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description mentions some actions like 'set up, improve, or audit analytics tracking and measurement' but doesn't list multiple specific concrete actions (e.g., 'configure GA4 properties, create tracking plans, implement UTM parameters, debug event firing'). The actions remain somewhat high-level. | 2 / 3 |
Completeness | Clearly answers both 'what' (set up, improve, or audit analytics tracking and measurement) and 'when' (explicit 'Use when' triggers with extensive keyword list). Also includes a cross-reference to a related skill (ab-test-setup) for disambiguation. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms including 'GA4,' 'Google Analytics,' 'conversion tracking,' 'event tracking,' 'UTM parameters,' 'tag manager,' 'GTM,' 'Mixpanel,' 'Segment,' 'analytics isn't working,' and natural phrases like 'how do I measure this' and 'are my events firing.' | 3 / 3 |
Distinctiveness Conflict Risk | The description carves out a clear niche around analytics tracking and measurement with highly specific trigger terms like 'GA4,' 'GTM,' 'Mixpanel,' 'Segment,' and 'UTM parameters.' The explicit cross-reference to ab-test-setup further reduces conflict risk. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
57%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill is well-structured with good progressive disclosure and useful reference tables, but suffers from including conceptual content Claude already knows (core principles, basic definitions) and lacks the concrete, step-by-step executable guidance needed for a high actionability score. The workflow would benefit from explicit validation checkpoints integrated into the implementation steps rather than listed separately.
Suggestions
Remove or drastically condense the 'Core Principles' section — these are general analytics truisms Claude already knows, not actionable implementation guidance.
Add explicit validation steps within the GA4 implementation workflow (e.g., 'After step 3, open DebugView and confirm enhanced measurement events appear before proceeding').
Make the GA4 Quick Setup more concrete with actual commands/URLs rather than abstract steps like 'Create GA4 property and data stream'.
Remove explanations of well-known concepts like what UTM parameters are or what GTM Tags/Triggers/Variables do — just show the implementation patterns.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill includes some unnecessary content Claude already knows (e.g., 'Naming conventions matter', 'Quality > quantity of events', explaining what Tags/Triggers/Variables are in GTM, standard UTM parameter definitions). The 'Core Principles' section is largely philosophical padding. However, the tables and code examples are reasonably efficient. | 2 / 3 |
Actionability | There are some concrete code examples (gtag event, dataLayer.push) and useful tables, but much of the content is high-level guidance rather than executable instructions. The GA4 setup is a 5-step list without specific commands or URLs. The tracking plan is a template but lacks a worked example showing how to fill it out for a real scenario. | 2 / 3 |
Workflow Clarity | The GA4 implementation has a numbered sequence but lacks validation checkpoints between steps. The debugging/validation section exists as a separate block rather than being integrated into the workflow. There's no explicit feedback loop (implement -> validate -> fix -> re-validate) for the tracking implementation process, which is important for analytics where silent failures are common. | 2 / 3 |
Progressive Disclosure | The skill effectively uses one-level-deep references to detailed guides (event-library.md, ga4-implementation.md, gtm-implementation.md, tool integration guides). The main document serves as a clear overview with well-signaled pointers to deeper content. Related skills are listed at the end for cross-referencing. | 3 / 3 |
Total | 9 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- coreyhaines31/marketingskills
- Commit
1bcff9f
- 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.