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.
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 'Use when' clause with numerous natural keywords makes it highly discoverable, and the cross-reference to ab-test-setup demonstrates good skill ecosystem awareness. The main weakness is that the 'what' portion could be more specific about concrete actions beyond 'set up, improve, or audit.'
Suggestions
Expand the capability description with more specific concrete actions, e.g., 'Configures GA4 properties, creates tracking plans, implements event schemas, sets up conversion goals, audits tag implementations' to improve specificity.
| 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 conversion goals.' 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 disambiguation. | 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 naturally use when requesting analytics help. | 3 / 3 |
Distinctiveness Conflict Risk | The description carves out a clear niche around analytics tracking/measurement with highly specific trigger terms (GA4, GTM, UTM parameters). The explicit cross-reference to ab-test-setup further reduces conflict risk by drawing a boundary between 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 falls short on actionability and conciseness. The core principles section adds little value for Claude, and the implementation guidance is often too high-level to be directly executable. The skill would benefit from trimming generic advice and replacing vague steps with specific, copy-paste-ready implementation instructions.
Suggestions
Remove or drastically condense the 'Core Principles' section — these are generic analytics best practices Claude already knows, not actionable implementation guidance.
Make the GA4 Quick Setup section truly actionable with specific commands, URLs, or code snippets for each step rather than a vague numbered list.
Integrate the validation checklist directly into the implementation workflow as explicit checkpoints (e.g., 'After step 3, use GA4 DebugView to confirm events fire before proceeding').
Remove the 'Task-Specific Questions' section which largely duplicates the 'Initial Assessment' section.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill contains some unnecessary content like 'Core Principles' (Track for Decisions, Start with Questions, Name Things Consistently) which are generic advice Claude already knows. The 'Task-Specific Questions' section at the end is also somewhat redundant given 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 specific naming conventions, 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. The tracking plan template is useful but the overall skill leans more toward describing what to do than showing exactly how. | 2 / 3 |
Workflow Clarity | The GA4 implementation has a numbered sequence but lacks validation checkpoints between steps. The debugging/validation section exists with a checklist, but it's disconnected from the implementation workflow rather than integrated as feedback loops. For a task involving tag deployment (potentially breaking tracking), there should be explicit validate-before-publish steps integrated into the workflow. | 2 / 3 |
Progressive Disclosure | The skill effectively uses one-level-deep references to detailed guides (event-library.md, ga4-implementation.md, gtm-implementation.md) and tool integrations. The main file serves as a clear overview with well-signaled links to deeper content. Navigation between sections and related skills is well-organized. | 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 | |
- Repository
- freekmurze/dotfiles
- Commit
2c6f6e8
- 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.