AI SummaryUse this skill for verification and optional publish handoff. If the telemetry consent prompt appears and no prior choice is recorded, stop and follow ../../references/telemetry-consent.md before continuing. If comparing against an older preview run, pass the previous health baseline:
Install
Copy this and paste it into Claude Code, Cursor, or any AI assistant:
I want to install the "tracking-verify" skill in my project. Please run this command in my terminal: # Install skill into your project mkdir -p .claude/skills/tracking-verify && curl --retry 3 --retry-delay 2 --retry-all-errors -o .claude/skills/tracking-verify/SKILL.md "https://raw.githubusercontent.com/jtrackingai/analytics-tracking-automation/main/skills/tracking-verify/SKILL.md" Then restart Claude Code (or reload the window in Cursor) so the skill is picked up.
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 before continuing. Run preview: `bash ./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: `bash ./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: `bash ./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
Discussion
Health Signals
My Fox Den
Community Rating
Sign in to rate this booster