15 Claude Skills for Google Tag Manager and Tracking

A pack of 15 production-ready Claude Skills for GTM, GA4, Google Ads, Meta Pixel+CAPI, consent, click IDs, duplicate events and CRM offline conversions.

Each skill is a self-contained SKILL.md with explicit triggers, required inputs, analysis workflow, decision rules, a practical example, output format, and guardrails. Drop them into Claude Code and they activate automatically when their use case matches the conversation.

What is inside

How to install

Option A — Claude Code (recommended)

1. Clone or download this repository.
2. Copy the skill folders into your project’s .claude/skills/ directory, or into the user-level skills directory at ~/.claude/skills/.
3. Start a new Claude Code session in that project. Skills will activate automatically when their description matches the conversation.

git clone https://github.com/mardab96/gtm-tracking-claude-skills.git
mkdir -p ~/.claude/skills
cp -r gtm-tracking-claude-skills/*-* \
      gtm-tracking-claude-skills/references \
      ~/.claude/skills/

Option B — Other Claude environments

The skills are plain Markdown with YAML frontmatter and work anywhere Claude can read files. Paste the relevant SKILL.md content into context when you want to use it.

How to use

Once installed, describe what you want in natural language. Skills self-trigger on the patterns documented in their ## Use this skill when section.

Activation and trigger reliability

Claude Skills usually activate from the YAML description field first, then use the full SKILL.md instructions after activation. Each skill in this pack now names the moment it should be used in both places:

• description explains the tracking situation that should trigger the skill.
• ## Use this skill when lists concrete request patterns and decision moments.
• ## Required input tells the user what exports, screenshots, traces and reports make the skill reliable.

For best results, ask for the job and include the tracking object being diagnosed. Example: “Audit Google Ads conversion tracking before we scale” will trigger google-ads-conversion-tracking-audit more reliably than “Check tracking.”

Bring your data

Every skill is data-first. They work best when you provide actual exports, reports, screenshots or notes. Each SKILL.md documents exactly which inputs it expects under ## Required input.

Guardrails

These skills are designed for diagnosis and approval-ready recommendations. By default they do not:

• publish ads
• change budgets
• pause campaigns
• edit tracking setup
• change optimization events
• modify landing pages
• modify CRM fields
• send customer messages
• make performance claims without data

Use them to structure the work, not to hand over control of the account.

Validate the pack

Run the validator before publishing changes:

python3 scripts/validate-skills.py

It checks for placeholder text, missing required sections, weak activation descriptions and workflows that are too short to be useful.

Examples and review

Use the sample outputs to judge the expected depth of analysis:

• examples/google-ads-conversion-tracking-audit-sample.md
• examples/duplicate-event-finder-sample.md

Use evals/review-checklist.md for the next manual review pass.

License and attribution

Free to use, modify, and redistribute for personal and commercial work. If you ship something built on top of these skills, a credit is appreciated but not required.

Built and maintained by AdLume — performance marketing infrastructure for AI-native operators.