analytics-tracking

Set up, audit, and debug analytics tracking implementation — GA4, Google Tag Manager, event taxonomy, conversion tracking, and data quality. Use when building a tracking plan from scratch, auditing existing analytics for gaps or errors, debugging missing events, or setting up GTM. Trigger keywords: GA4 setup, Google Tag Manager, GTM, event tracking, analytics implementation, conversion tracking, tracking plan, event taxonomy, custom dimensions, UTM tracking, analytics audit, missing events, tracking broken. NOT for analyzing marketing campaign data — use campaign-analytics for that. NOT for BI dashboards — use product-analytics for in-product event analysis.

Quality

91%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

—

The risk profile of this skill

Quality

Content

82%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A strong, operational skill body with executable code, concrete commands, and clear mode-based sequencing. Its main gaps are the missing inline workflow/validation feedback loop for audit and debug modes and an orphaned debugging reference file that the body never points to.

Suggestions

Link references/debugging-playbook.md from the Mode 3 (Debug Tracking Issues) section so the existing reference is discoverable rather than orphaned.

Add an explicit validate→fix→retry feedback loop to the Audit and Debug workflows (e.g. confirm in GTM Preview + GA4 DebugView after each fix) to raise workflow_clarity.

Trim the philosophy intro paragraph and the generic Communication section, which restate principles Claude already applies, to tighten conciseness.

Dimension	Reasoning	Score
Conciseness	Largely lean and operational (tables, executable snippets, commands) and never explains concepts Claude already knows, but the philosophy intro ("Bad tracking is worse than no tracking...") and the generic Communication section add mild padding that could be trimmed. Not 5 because not every token earns its place; not 3 because the bulk is efficient.	4 / 5
Actionability	Copy-paste-ready code throughout — `window.dataLayer.push({...})`, `gtag('event', ...)` — plus an executable generator (`python3 scripts/tracking_plan_generator.py [plan.json] [--json]`) and concrete GTM tag/trigger/variable field templates covering the common SaaS cases.	5 / 5
Workflow Clarity	Three clearly sequenced modes and GA4/GTM setup enumerated with concrete test steps (e.g. "Test: visit domain A, click link to domain B, check GA4 DebugView"). Not 5 because the Audit and Debug modes give no inline step sequence and the destructive/batch-adjacent dedup and consent changes lack an explicit validate→fix→retry feedback loop.	4 / 5
Progressive Disclosure	Body is well structured with one-level-deep, clearly signaled references to event-taxonomy-guide.md and gtm-patterns.md, both of which exist. Not 5 because references/debugging-playbook.md is present in the bundle yet never linked from the body — Mode 3 says only "Structured debugging workflow" with no pointer — leaving one reference orphaned and navigation incomplete.	4 / 5
	Total	17 / 20 Passed

Description

100%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

An exemplar description: concrete actions, a dedicated trigger-keyword block, explicit 'Use when' guidance, and hard boundary clauses against sibling skills. Nothing material is missing or vague.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions across the domain — "Set up, audit, and debug" spanning "GA4, Google Tag Manager, event taxonomy, conversion tracking, and data quality" — giving comprehensive coverage rather than generic verbs. Not below 5 because no meaningful capability is omitted.	5 / 5
Completeness	Explicitly answers both: the "what" ("Set up, audit, and debug analytics tracking implementation") and the "when" ("Use when building a tracking plan from scratch, auditing existing analytics..., debugging missing events, or setting up GTM") with concrete trigger phrases.	5 / 5
Trigger Term Quality	An explicit "Trigger keywords:" block covers natural terms and synonyms users actually say ("GA4 setup, Google Tag Manager, GTM, event tracking, analytics implementation, conversion tracking, tracking plan... missing events, tracking broken"), matching the comprehensive-synonym anchor.	5 / 5
Distinctiveness Conflict Risk	Clear niche with explicit boundary clauses — "NOT for analyzing marketing campaign data — use campaign-analytics" and "NOT for BI dashboards — use product-analytics" — minimizing conflict risk with adjacent skills.	5 / 5
	Total	20 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: alirezarezvani/claude-skills
Path: marketing-skill/skills/analytics-tracking/SKILL.md
Commit: 19392f7

Reviewed: ~1 hour ago

Table of Contents

Discovery Implementation Validation

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.