Use when the user wants preview QA, failure interpretation, release readiness, or an explicit publish handoff.
The English summary is being prepared. Showing the original description.
See how to installReview the instructions the agent will receive before you install.
Use this skill for verification and optional publish handoff.
<artifact-dir>/event-schema.json<artifact-dir>/gtm-context.jsonIf 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:
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.
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/<artifact-dir>/workflow-state.jsonIf the platform is Shopify, switch to the Shopify-specific rules in tracking-shopify.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Use when you need GA4 + GTM tracking delivery from site discovery through publish, or when the right phase entry point is still unclear.
The English summary is being prepared. Showing the original description.
Use when the user wants crawl coverage, platform detection, dataLayer discovery, or a fresh artifact directory before grouping and schema work.
The English summary is being prepared. Showing the original description.
Use when the work starts from `site-analysis.json` and the user wants page-group authoring, grouping adjustments, or page-group approval.
The English summary is being prepared. Showing the original description.
Use when the user wants to inspect the real live GTM runtime before schema generation or compare multiple live GTM containers.
The English summary is being prepared. Showing the original description.
Use when the user wants schema preparation, event design, selector validation, schema review, or event-spec generation.
The English summary is being prepared. Showing the original description.
Use when the platform is Shopify or the run needs the Shopify-specific schema, sync, install, or verification branch.
The English summary is being prepared. Showing the original description.