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 skill description with excellent trigger term coverage and completeness. Its 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 reducing overlap.
Suggestions
Add more specific concrete actions to the 'what' portion, e.g., 'configure GA4 properties, create tracking plans, implement UTM tagging, debug event firing, set up conversion goals' to improve specificity.
| 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' clause with extensive trigger terms). 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 users would actually say: 'GA4,' 'Google Analytics,' 'conversion tracking,' 'event tracking,' 'UTM parameters,' 'tag manager,' 'GTM,' 'Mixpanel,' 'Segment,' 'analytics isn't working,' 'how do I measure this,' 'track conversions,' 'attribution,' and 'are my events firing.' These cover both tool names and natural language queries. | 3 / 3 |
Distinctiveness Conflict Risk | The description carves out a clear niche around analytics tracking and measurement with highly specific tool names (GA4, GTM, Mixpanel, Segment) and explicitly delineates its boundary from the ab-test-setup skill, reducing 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.
This is a reasonably well-organized analytics tracking skill with good progressive disclosure and useful reference tables, but it suffers from verbosity in its principles sections and lacks the concrete, step-by-step executable guidance needed for reliable implementation. The workflow would benefit from explicit validation gates integrated into the implementation sequence rather than listed separately.
Suggestions
Remove or drastically condense the 'Core Principles' section—these are generic best practices Claude already knows, not actionable implementation guidance.
Integrate the validation checklist directly into the GA4 and GTM implementation workflows as explicit checkpoints (e.g., 'After step 3, open GA4 DebugView and confirm events appear before proceeding').
Replace the high-level GA4 Quick Setup list with specific commands or UI paths (e.g., 'Admin > Data Streams > Add stream > Web > enter URL') to make it truly actionable.
Trim the 'Privacy and Compliance' section to just the implementation-specific items (consent mode snippet, IP anonymization config) rather than listing general considerations.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill contains some unnecessary padding—'Core Principles' section is largely advice Claude already knows (track for decisions, start with questions, name things consistently, maintain data quality). The tables and event examples are useful, but sections like 'Privacy and Compliance' are fairly generic. Could be tightened significantly. | 2 / 3 |
Actionability | There are some concrete code examples (gtag event, dataLayer push) and useful tables, but much of the content is descriptive rather than executable. The GA4 setup is a high-level numbered list without specific commands. The tracking plan template is helpful but the debugging section lacks actual commands or step-by-step procedures. | 2 / 3 |
Workflow Clarity | The GA4 Quick Setup provides a numbered sequence but lacks validation checkpoints between steps. The debugging/validation checklist exists but isn't integrated into the implementation workflow as explicit gates. For an analytics implementation that can silently fail, there should be explicit validate-then-proceed steps after each major phase. | 2 / 3 |
Progressive Disclosure | Content is well-structured with clear sections and appropriate references to deeper materials (event-library.md, ga4-implementation.md, gtm-implementation.md, tool integration guides). References are one level deep and clearly signaled with descriptive link text. Related skills are listed at the end. | 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
2c7c108
- 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.