agentsclimarketplace
Sign in

Tracking verify

Skill jtrackingai/analytics-tracking-automation/skills/tracking-verify

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

Install
npx -y skills add jtrackingai/analytics-tracking-automation --skill tracking-verify

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • runs commandsInstructs the agent to run 3 commands, including `./event-tracking preview <artifact-dir>/event-schema.json --context-file <artifact-dir>/gtm-context.json` and 2 more.

SKILL.md

2.7 KB, 553 tokens by cl100k_base, as published. Nobody here has run it

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

What ships with it: 1 file

264 B alongside SKILL.md

agents/

Keep looking

Skills are one crate of 325,949. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.