Agent skill
tracking-live-gtm
Use when the user wants to inspect the real live GTM runtime before schema generation or compare multiple live GTM containers.
Install this agent skill to your Project
npx add-skill https://github.com/jtrackingai/event-tracking-skill/tree/main/skills/tracking-live-gtm
SKILL.md
Tracking Live GTM
Use this skill to audit the site's real live GTM setup before event generation.
Inputs
One of:
- confirmed
<artifact-dir>/site-analysis.json - explicit live GTM public IDs when the crawl did not capture them
Workflow
Run the live baseline step before schema preparation whenever the site has a real GTM container installed:
./event-tracking analyze-live-gtm <artifact-dir>/site-analysis.json
If multiple live containers matter and the user already knows the primary comparison target:
./event-tracking analyze-live-gtm <artifact-dir>/site-analysis.json --primary-container-id GTM-XXXXXXX
During review:
- show all detected live GTM containers
- explain which container is the primary comparison baseline
- summarize existing live events, measurement IDs, and obvious issues
- stop before schema authoring if the user wants to review the live baseline first
Required Output
Produce and share:
<artifact-dir>/live-gtm-analysis.json<artifact-dir>/live-gtm-review.md- updated
<artifact-dir>/workflow-state.json
Stop Boundary
Stop after the live GTM baseline is reviewed unless the user explicitly asks to continue into schema work.
Default next phase:
./event-tracking prepare-schema <artifact-dir>/site-analysis.json
References
- ../../references/event-schema-guide.md
- ../../references/output-contract.md
- ../../references/architecture.md
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
tracking-discover
Use when the user wants crawl coverage, platform detection, dataLayer discovery, or a fresh artifact directory before grouping and schema work.
tracking-shopify
Use when the platform is Shopify or the run needs the Shopify-specific schema, sync, install, or verification branch.
tracking-schema
Use when the user wants schema preparation, event design, selector validation, schema review, or event-spec generation.
tracking-group
Use when the work starts from `site-analysis.json` and the user wants page-group authoring, grouping adjustments, or page-group approval.
tracking-verify
Use when the user wants preview QA, failure interpretation, release readiness, or an explicit publish handoff.
tracking-sync
Use when the user wants GTM-ready config generation, GTM workspace sync, or container selection from an approved schema.
Didn't find tool you were looking for?