CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

70

Quality

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

The canonical home for this skill is analytics-tracking in alirezarezvani/claude-skills

SKILL.md
Quality
Evals
Security

Quality

Content

78%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 highly actionable, well-structured skill body with concrete code and clear setup workflows. Its main weakness is progressive disclosure: referenced bundle files are missing and substantial catalog content is inlined in SKILL.md.

Suggestions

Create the referenced bundle files (references/event-taxonomy-guide.md, references/gtm-patterns.md, scripts/tracking_plan_generator.py) or remove the dead links, since the body currently points to files that do not exist.

Move the full event taxonomy catalog, GTM container structure, and UTM/attribution tables into the reference files, keeping SKILL.md as a concise overview with one-level-deep pointers.

Flesh out Mode 3 (Debug Tracking Issues) into explicit numbered steps using GTM Preview + GA4 DebugView + Network tab, including a validate-and-retry feedback loop, rather than describing it only as a "structured debugging workflow."

DimensionReasoningScore

Conciseness

Mostly efficient with lean tables and copy-paste code blocks that assume Claude's competence, but framing prose like "You are an expert in analytics implementation..." and "Bad tracking is worse than no tracking" could be trimmed.

4 / 5

Actionability

Fully executable guidance throughout: runnable bash commands, copy-paste gtag/dataLayer code, concrete GTM tag/trigger/variable configurations, and specific UI navigation paths that cover the common SaaS setup cases.

5 / 5

Workflow Clarity

Three modes are clearly sequenced and GA4/cross-domain setup use numbered steps with a test checkpoint, but Mode 3 (Debug) promises a "structured debugging workflow" without enumerating the actual steps, leaving a validation gap.

4 / 5

Progressive Disclosure

Section organization is clear and references are signaled via markdown links, but the cited bundle files (references/event-taxonomy-guide.md, references/gtm-patterns.md, scripts/tracking_plan_generator.py) do not exist, and large taxonomy/container/UTM tables are inlined rather than split into those reference files.

3 / 5

Total

16

/

20

Passed

Description

95%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.

A strong, well-targeted description that clearly states capabilities, trigger conditions, and negative boundaries in third-person voice. Minor room to convert enumerated domains into additional concrete verbs for full specificity.

DimensionReasoningScore

Specificity

Names three concrete actions ("Set up, audit, and debug analytics tracking implementation") plus enumerated domains (GA4, GTM, event taxonomy, conversion tracking, data quality); not a full 5 because the enumerated items are domains rather than additional distinct actions.

4 / 5

Completeness

Explicitly answers both what ("Set up, audit, and debug analytics tracking implementation... data quality") and 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

Comprehensive trigger keyword list including synonyms ("Google Tag Manager" / "GTM") and natural user phrases ("missing events", "tracking broken", "analytics audit") covering the common ways users request this skill.

5 / 5

Distinctiveness Conflict Risk

Clear niche (analytics tracking implementation) with explicit NOT-for boundaries redirecting to campaign-analytics and product-analytics, minimizing overlap with adjacent marketing skills.

5 / 5

Total

19

/

20

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 2 missing

Warning

referenced_paths_exist

Referenced path issues: 8 missing

Warning

Total

14

/

16

Passed

Repository
alirezarezvani/claude-skills
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.