mcpbeat

Tracking Verify

jtrackingai/tracking-verify

Use when the user wants preview QA, failure interpretation, release readiness, or an explicit publish handoff.

761 tokens
context cost
the whole folder, loaded on every use
2
files
instructions only
0
copies elsewhere
how many repositories repackaged it
134
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository 
npx skills add https://github.com/jtrackingai/analytics-tracking-automation --skill tracking-verify

The instruction itself

7 sections, as written by the author

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 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/gtm-troubleshooting.md
  • ../../references/output-contract.md

How to use it

Copy the folder

Take jtrackingai/tracking-verify from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.