Menu
Use when the user wants schema preparation, event design, selector validation, schema review, or event-spec generation.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Use when you need GA4 + GTM tracking delivery from site discovery through publish, or when the right phase entry point is still unclear.
Use when the user wants crawl coverage, platform detection, dataLayer discovery, or a fresh artifact directory before grouping and schema work.
Use when the user wants GTM-ready config generation, GTM workspace sync, or container selection from an approved schema.
Use when the user wants preview QA, failure interpretation, release readiness, or an explicit publish handoff.
Use when the user wants to inspect the real live GTM runtime before schema generation or compare multiple live GTM containers.
Use when the work starts from `site-analysis.json` and the user wants page-group authoring, grouping adjustments, or page-group approval.
| name | tracking-schema |
| description | Use when the user wants schema preparation, event design, selector validation, schema review, or event-spec generation. |
Use this skill for Step 3 work only.
One of:
<artifact-dir>/site-analysis.json<artifact-dir>/event-schema.jsonDuring schema work, act as an expert in event tracking design.
Your job is not to list generic events. Your job is to produce a tracking plan that is:
Favor event definitions that are business-meaningful, implementation-ready, and analytically useful. Do not preserve weak legacy patterns just for continuity. Do not inflate the schema with events that add little reporting or decision value.
If the telemetry consent prompt appears and no prior choice is recorded, stop and follow ../../references/telemetry-consent.md before continuing.
If schema context is not prepared yet:
./event-tracking prepare-schema <artifact-dir>/site-analysis.json
If the site has a live GTM container installed, make sure tracking-live-gtm has already produced <artifact-dir>/live-gtm-analysis.json before running prepare-schema.
Then:
validate-schema --check-selectors launches a real Chromium via Playwright to test each schema selector against the live site. 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.
./event-tracking validate-schema <artifact-dir>/event-schema.json --check-selectors
./event-tracking generate-spec <artifact-dir>/event-schema.json
./event-tracking confirm-schema <artifact-dir>/event-schema.json
During review:
live-gtm-analysis.json is presentEvent Table, Common Properties, Event-specific Properties./event-tracking confirm-schema <artifact-dir>/event-schema.json --yes on the user's behalf unless the user explicitly confirms the schema and parameters in the current turnProduce and share:
<artifact-dir>/event-schema.json<artifact-dir>/event-spec.md<artifact-dir>/tracking-plan-comparison.md when live-gtm-analysis.json is present<artifact-dir>/schema-decisions.jsonl after schema confirmation<artifact-dir>/schema-restore/ restore snapshots after schema confirmation<artifact-dir>/workflow-state.jsonEvent Table, Common Properties, Event-specific PropertiesStop after schema approval.
Do not continue into generate-gtm from a broad workflow request alone. The user must explicitly approve the current event-schema.json and its parameters first.
Default next phase:
./event-tracking generate-gtm <artifact-dir>/event-schema.json --measurement-id <G-XXXXXXXXXX>