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.
Install with Tessl CLI
npx tessl i github:coreyhaines31/marketingskills --skill analytics-trackingOverall
score
84%
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillEvaluation — 100%
↑ 1.08xAgent success when using this skill
Validation for skill structure
Discovery
90%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 comprehensive trigger terms makes it highly discoverable. The main weakness is that the capabilities could be more specific - listing concrete actions like 'configure events,' 'build tracking plans,' or 'audit tag implementations' would strengthen it further.
Suggestions
Add more specific concrete actions to the beginning, e.g., 'Configure GA4 events, build tracking plans, implement conversion pixels, audit tag implementations' instead of the generic 'set up, improve, or audit'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (analytics tracking/measurement) and mentions actions like 'set up, improve, or audit' but doesn't list specific concrete capabilities like 'configure GA4 events, create tracking plans, implement conversion pixels.' | 2 / 3 |
Completeness | Clearly answers both what ('set up, improve, or audit analytics tracking and measurement') and when ('Use when the user mentions...' with explicit trigger list). Also includes helpful cross-reference to related skill for disambiguation. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms users would say: 'GA4,' 'Google Analytics,' 'conversion tracking,' 'event tracking,' 'UTM parameters,' 'tag manager,' 'GTM,' 'analytics implementation,' 'tracking plan' - these are all terms users naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Very distinct niche with specific analytics/tracking focus. The explicit cross-reference to 'ab-test-setup' shows awareness of potential overlap and provides clear disambiguation guidance. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
73%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured analytics tracking skill with strong actionability and excellent progressive disclosure. The main weaknesses are some unnecessary philosophical content about tracking principles that Claude already understands, and workflow steps that could benefit from explicit validation checkpoints between implementation phases.
Suggestions
Remove or significantly condense the 'Core Principles' section - Claude understands these concepts and they consume tokens without adding actionable guidance.
Add explicit validation checkpoints to the GA4 Quick Setup workflow, e.g., 'After step 2, verify gtag is loading in browser console before proceeding.'
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some unnecessary explanatory content like 'Track for Decisions, Not Data' principles that Claude already understands. The tables and structure are good, but sections like 'Core Principles' add tokens without adding actionable value. | 2 / 3 |
Actionability | Provides concrete, executable code examples (gtag, dataLayer.push), specific event naming conventions, ready-to-use tracking plan templates, and clear implementation steps. The JavaScript snippets are copy-paste ready. | 3 / 3 |
Workflow Clarity | The GA4 Quick Setup provides numbered steps, and there's a validation checklist, but the workflow lacks explicit validation checkpoints between steps. For example, there's no 'verify events are firing before proceeding' step in the implementation sequence. | 2 / 3 |
Progressive Disclosure | Excellent structure with clear overview sections and well-signaled one-level-deep references to detailed guides (references/event-library.md, references/ga4-implementation.md, references/gtm-implementation.md). Navigation is clear with related skills linked at the end. | 3 / 3 |
Total | 10 / 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.
- 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.