Use when you need GA4 + GTM tracking delivery from site discovery through publish, or when the right phase entry point is still unclear.
中文简介正在准备中。当前显示原文说明。
jtrackingai/analytics-tracking-automation1442026年4月29日 更新
免费在 GitHub 公开
tracking-live-gtm
Use when the user wants to inspect the real live GTM runtime before schema generation or compare multiple live GTM containers.
中文简介正在准备中。当前显示原文说明。
查看安装方法包含的文件（2）
- SKILL.md2.8 KB
- agents/openai.yaml300 B
SKILL.md（原文）
安装前可以查看交给 AI 代理的指令内容。
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
If the telemetry consent prompt appears and no prior choice is recorded, stop and follow ../../references/telemetry-consent.md before continuing.
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
If the user wants to test the quality of the already-published live GTM setup on the real site, run:
./event-tracking verify-live-gtm <artifact-dir>/site-analysis.json
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
- when
verify-live-gtmwas run, separate parsed live definitions from browser-verified live firing evidence - if this review is part of
tracking_health_audit, clearly separate runtime-detected live definitions from any formal preview-verified automation evidence - 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- optional
<artifact-dir>/live-preview-result.json - optional
<artifact-dir>/live-preview-report.md - optional
<artifact-dir>/live-tracking-health.json - updated
<artifact-dir>/workflow-state.json
Closeout Style
- default to a compact live-tracking summary before listing files
- name the detected live events directly instead of only reporting event counts
- in
tracking_health_audit, explicitly separate runtime-detected live definitions from formal preview-verified automation evidence - list artifacts only after the decision-ready summary
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
评价
还没有评价。欢迎分享你的使用感受。
评论
无需登录即可发表。欢迎分享使用感受、提问，或说明在哪些环境下无法运行。
还没有评论。来写第一条吧。
同一仓库的技能
Use when the user wants crawl coverage, platform detection, dataLayer discovery, or a fresh artifact directory before grouping and schema work.
中文简介正在准备中。当前显示原文说明。
jtrackingai/analytics-tracking-automation1442026年4月29日 更新
Use when the work starts from `site-analysis.json` and the user wants page-group authoring, grouping adjustments, or page-group approval.
中文简介正在准备中。当前显示原文说明。
jtrackingai/analytics-tracking-automation1442026年4月29日 更新
Use when the user wants schema preparation, event design, selector validation, schema review, or event-spec generation.
中文简介正在准备中。当前显示原文说明。
jtrackingai/analytics-tracking-automation1442026年4月29日 更新
Use when the platform is Shopify or the run needs the Shopify-specific schema, sync, install, or verification branch.
中文简介正在准备中。当前显示原文说明。
jtrackingai/analytics-tracking-automation1442026年4月29日 更新
Use when the user wants GTM-ready config generation, GTM workspace sync, or container selection from an approved schema.
中文简介正在准备中。当前显示原文说明。
jtrackingai/analytics-tracking-automation1442026年4月29日 更新