CtrlK
BlogDocsLog inGet started
Tessl Logo

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

1.11x
Quality

73%

Does it follow best practices?

Impact

99%

1.11x

Average score across 6 eval scenarios

SecuritybySnyk

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/analytics-tracking/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

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 parameters, set up conversion goals, debug event firing, audit tag manager configurations.'

DimensionReasoningScore

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 explicitly defers A/B test measurement to another 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 well-structured reference document with good progressive disclosure and useful tables, but it leans toward being a knowledge base rather than an actionable skill. The core principles section states things Claude already knows, and the implementation guidance is often too high-level to be directly executable. Integrating validation steps into the workflows and replacing abstract advice with specific commands would significantly improve it.

Suggestions

Remove or drastically shorten the 'Core Principles' section—these are general analytics truisms that Claude already knows and they consume tokens without adding actionable value.

Make the GA4 Quick Setup steps concrete and executable: include specific URLs, exact UI paths, and integrate a validation step (e.g., 'After step 3, open DebugView and confirm enhanced measurement events appear before proceeding').

Replace abstract guidance like 'Configure custom events' and 'Enable enhanced measurement' with specific click paths or API calls that are copy-paste ready.

DimensionReasoningScore

Conciseness

The skill contains some unnecessary padding—sections like 'Core Principles' explain concepts Claude already knows (e.g., 'Quality > quantity of events', 'Clean data > more data', 'Naming conventions matter'). The 'Task-Specific Questions' section and 'Initial Assessment' are somewhat redundant. 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. Many sections describe what to do abstractly ('Configure custom events', 'Enable enhanced measurement') without showing exactly how.

2 / 3

Workflow Clarity

The GA4 Quick Setup provides a numbered sequence but lacks validation checkpoints between steps. The debugging/validation section exists as a separate checklist but isn't integrated into the implementation workflow as explicit feedback loops. For an implementation that can silently fail (events not firing, wrong values), the lack of 'validate then proceed' patterns 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 related skills are listed at the bottom.

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.

Validation11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository
coreyhaines31/marketingskills
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.