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.
78
73%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./config/claude/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. The explicit 'when to use' guidance and cross-reference to a related skill demonstrate thoughtful design. The main weakness is that the 'what it does' portion could be more specific about concrete actions beyond 'set up, improve, or audit.'
Suggestions
Add more specific concrete actions to the 'what' portion, e.g., 'configure GA4 properties, create tracking plans, implement event schemas, set up conversion funnels, define UTM naming conventions.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names the domain (analytics tracking and measurement) and mentions some actions ('set up, improve, or audit'), but doesn't list specific concrete actions like 'configure GA4 properties, create tracking plans, implement event schemas, set up UTM parameter conventions.' 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 detailed trigger terms). Also includes a helpful cross-reference to the ab-test-setup skill for boundary clarity. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms users would actually say: 'set up tracking,' 'GA4,' 'Google Analytics,' 'conversion tracking,' 'event tracking,' 'UTM parameters,' 'tag manager,' 'GTM,' 'analytics implementation,' 'tracking plan.' These are all terms users would naturally use when requesting this type of help. | 3 / 3 |
Distinctiveness Conflict Risk | The description carves out a clear niche around analytics tracking/measurement with highly specific trigger terms like 'GA4,' 'GTM,' 'UTM parameters.' The explicit boundary note ('For A/B test measurement, see ab-test-setup') further reduces conflict risk with related skills. | 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 moderately well-structured analytics tracking skill that excels at progressive disclosure and organization but suffers from verbosity in its principles/philosophy sections and lacks fully actionable, executable guidance in key areas like GA4 setup. The core principles section and task-specific questions add token overhead without proportional value, and the implementation workflows would benefit from integrated validation checkpoints.
Suggestions
Remove or drastically condense the 'Core Principles' section — these are generic analytics truisms that Claude already understands and don't add actionable value.
Make the GA4 Quick Setup section truly actionable with specific commands, URLs, or code snippets for each step rather than vague instructions like 'Create GA4 property and data stream'.
Integrate validation steps directly into the implementation workflows (e.g., after installing gtag.js, verify with DebugView before proceeding to custom events) rather than having a disconnected validation checklist.
Remove the 'Task-Specific Questions' section which largely duplicates the 'Initial Assessment' section, or merge them into a single concise discovery checklist.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill contains some unnecessary content like 'Core Principles' that are generic advice Claude already knows (e.g., 'Quality > quantity of events', 'Clean data > more data'). The 'Task-Specific Questions' section at the end largely duplicates the 'Initial Assessment' section. 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 'Quick Setup' is a vague 5-step list without specific commands or URLs. Many sections describe what to do conceptually rather than providing copy-paste-ready implementations. | 2 / 3 |
Workflow Clarity | The GA4 Quick Setup provides a numbered sequence but lacks validation checkpoints between steps. The Debugging and Validation section exists as a separate checklist but isn't integrated into the implementation workflow as explicit verification gates. For an analytics implementation involving tag deployment (a potentially error-prone multi-step process), the lack of inline validation steps is a gap. | 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 links to deeper content, and the structure is easy to navigate with clear section headers. | 3 / 3 |
Total | 9 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
05d40bb
Table of Contents
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.