tracking-discover
Use when the user wants crawl coverage, platform detection, dataLayer discovery, or a fresh artifact directory before grouping…
@jtrackingaiInstall SkillMarketing
Skill
/tracking-verify
Use when the user wants preview QA, failure interpretation, release readiness, or an explicit publish handoff.
Claude Code
$ npx -y skills add jtrackingai/analytics-tracking-automation --skill tracking-verify --agent claude-code
Codex
$ npx skills add jtrackingai/analytics-tracking-automation --skill tracking-verify -a codex -y
Cursor
$ npx skills add jtrackingai/analytics-tracking-automation --skill tracking-verify -a cursor -y
Gemini CLI
$ npx skills add jtrackingai/analytics-tracking-automation --skill tracking-verify -a gemini-cli -y
GitHub Copilot
$ npx skills add jtrackingai/analytics-tracking-automation --skill tracking-verify -a github-copilot -y
OpenCode
$ npx skills add jtrackingai/analytics-tracking-automation --skill tracking-verify -a opencode -y
Windsurf
$ npx skills add jtrackingai/analytics-tracking-automation --skill tracking-verify -a windsurf -y
SKILL.md
tracking-verify.SKILL.mdname: tracking-verify
description: Use when the user wants preview QA, failure interpretation, release readiness, or an explicit publish handoff.
Tracking Verify
Use this skill for verification and optional publish handoff.
Inputs
- `<artifact-dir>/event-schema.json`
- `<artifact-dir>/gtm-context.json`
Workflow
If the telemetry consent prompt appears and no prior choice is recorded, stop and follow [../../references/telemetry-consent.md](../../references/telemetry-consent.md) before continuing.
Run preview:
./event-tracking preview <artifact-dir>/event-schema.json --context-file <artifact-dir>/gtm-context.json
If comparing against an older preview run, pass the previous health baseline:
./event-tracking preview <artifact-dir>/event-schema.json --context-file <artifact-dir>/gtm-context.json --baseline <previous-tracking-health.json>
`preview` launches a real Chromium via Playwright and exercises the live site to fire GA4/GTM events for verification. Run it in an environment that permits outbound network and local browser execution; environments that restrict either tend to cause Playwright to hang or fail silently rather than return a clean error.
Then interpret:
- blockers
- expected failures
- selector mismatches
- unexpected fired events outside the approved schema
- release readiness
If the user explicitly wants to publish after verification:
./event-tracking publish --context-file <artifact-dir>/gtm-context.json --version-name "GA4 Events v1 - <date>"
If `tracking-health.json` is missing, still manual-only, or has blockers, `publish` now stops by default. Only use `--force` when the user explicitly wants to override that gate.
Required Output
Produce and share:
- `<artifact-dir>/preview-report.md`
- `<artifact-dir>/preview-result.json`
- `<artifact-dir>/tracking-health.json`
- `<artifact-dir>/tracking-health-report.md`
- `<artifact-dir>/tracking-health-history/`
- updated `<artifact-dir>/workflow-state.json`
Closeout Style
- default to a verification verdict first: healthy, blocked, or manual follow-up required
- summarize blockers, unexpected events, and release-readiness in plain language before listing files
- keep raw preview data and artifact references after the summary
Stop Boundary
- stop after preview if the user only asked for QA
- publish only when the user explicitly wants to affect the live site
If the platform is Shopify, switch to the Shopify-specific rules in `tracking-shopify`.
References
- [../../references/preview-report.md](../../references/preview-report.md)
- [../../references/gtm-troubleshooting.md](../../references/gtm-troubleshooting.md)
- [../../references/output-contract.md](../../references/output-contract.md)
Read more
name: tracking-verify description: Use when the user wants preview QA, failure interpretation, release readiness, or an explicit publish handoff.
Tracking Verify
Use this skill for verification and optional publish handoff.
Inputs
- `<artifact-dir>/event-schema.json`
- `<artifact-dir>/gtm-context.json`
Workflow
If the telemetry consent prompt appears and no prior choice is recorded, stop and follow [../../references/telemetry-consent.md](../../references/telemetry-consent.md) before continuing.
Run preview:
./event-tracking preview <artifact-dir>/event-schema.json --context-file <artifact-dir>/gtm-context.json
If comparing against an older preview run, pass the previous health baseline:
./event-tracking preview <artifact-dir>/event-schema.json --context-file <artifact-dir>/gtm-context.json --baseline <previous-tracking-health.json>
`preview` launches a real Chromium via Playwright and exercises the live site to fire GA4/GTM events for verification. Run it in an environment that permits outbound network and local browser execution; environments that restrict either tend to cause Playwright to hang or fail silently rather than return a clean error.
Then interpret:
- blockers
- expected failures
- selector mismatches
- unexpected fired events outside the approved schema
- release readiness
If the user explicitly wants to publish after verification:
./event-tracking publish --context-file <artifact-dir>/gtm-context.json --version-name "GA4 Events v1 - <date>"
If `tracking-health.json` is missing, still manual-only, or has blockers, `publish` now stops by default. Only use `--force` when the user explicitly wants to override that gate.
Required Output
Produce and share:
- `<artifact-dir>/preview-report.md`
- `<artifact-dir>/preview-result.json`
- `<artifact-dir>/tracking-health.json`
- `<artifact-dir>/tracking-health-report.md`
- `<artifact-dir>/tracking-health-history/`
- updated `<artifact-dir>/workflow-state.json`
Closeout Style
- default to a verification verdict first: healthy, blocked, or manual follow-up required
- summarize blockers, unexpected events, and release-readiness in plain language before listing files
- keep raw preview data and artifact references after the summary
Stop Boundary
- stop after preview if the user only asked for QA
- publish only when the user explicitly wants to affect the live site
If the platform is Shopify, switch to the Shopify-specific rules in `tracking-shopify`.
References
- [../../references/preview-report.md](../../references/preview-report.md)
- [../../references/gtm-troubleshooting.md](../../references/gtm-troubleshooting.md)
- [../../references/output-contract.md](../../references/output-contract.md)
Stats
145
Stars
41
Forks
Quiet
Maintenance
TypeScript
Language
Apache-2.0
License
Last commit
Created
Ships withanalytics-tracking-automation
analytics-tracking-automation is a local-first AI skill for planning, reviewing, and delivering GA4 + GTM tracking.
1457 skills
Stars on GitHub
Momentum
- stars in total
- 145
Other skills on analytics-tracking-automation.
@jtrackingaiInstall Skilltracking-group
Use when the work starts from `site-analysis.json` and the user wants page-group authoring, grouping adjustments, or page-group…
@jtrackingaiInstall Skilltracking-live-gtm
Use when the user wants to inspect the real live GTM runtime before schema generation or compare multiple live GTM containers.
@jtrackingaiInstall Skilltracking-schema
Use when the user wants schema preparation, event design, selector validation, schema review, or event-spec generation.
@jtrackingaiInstall Skilltracking-shopify
Use when the platform is Shopify or the run needs the Shopify-specific schema, sync, install, or verification branch.
@jtrackingaiInstall Skilltracking-sync
Use when the user wants GTM-ready config generation, GTM workspace sync, or container selection from an approved schema.
@jtrackingaiInstall SkillMore skills from other plugins.
Auto-invoked
ab-testing
When the user wants to plan, design, or implement an A/B test or experiment, or build a growth experimentation program. Also use…
@coreyhaines31Install Skillseo
Comprehensive SEO analysis for any website or business type. Full site audits, single-page analysis, technical SEO (crawlability,…
@agricidanielInstall Skillbrag
Turn the current project website into a short, polished, shareable launch video using Hyperframes. Use when someone says "/brag",…
@latent-spacesInstall Skillgeo-audit
Full website GEO+SEO audit with parallel subagent delegation. Orchestrates a comprehensive Generative Engine Optimization audit…
@zubair-trabzadaInstall SkillQuestions about tracking-verify.
- Which coding agents can use tracking-verify?
- tracking-verify installs in Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, OpenCode and Windsurf with the skills CLI, using each agent's flag shown on this page. Flowy's auto-invocation, which fires a skill when your prompt matches, runs in Claude Code only.