‹ 首页

tracking-live-gtm

@jtrackingai · 收录于 1 周前

Use when the user wants to inspect the real live GTM runtime before schema generation or compare multiple live GTM containers.

场景gtm调试容器对比

适合你，如果需要检查或对比多个 GTM 容器的实时配置。

/ 下载安装
tracking-live-gtm.skill双击,或拖进 Claude 桌面版 / Cowork,即完成安装↓ .skill↓ .zip
用别的 agent?下载 .zip 解压,把文件夹放进它的技能目录
Claude Code~/.claude/skills/(项目级 .claude/skills/)
Codex CLI~/.codex/skills/
Cursor自动读取上面两处目录
其他工具见其文档的「skills」目录;两个下载是同一份文件,只是名字不同
/ 通过 npx 安装 校验哈希
npx oh-my-skill add jtrackingai/analytics-tracking-automation/tracking-live-gtm
/ 通过 bash 安装
curl -fsSL https://oh-my-skill.com/install.sh | bash -s -- jtrackingai/analytics-tracking-automation/tracking-live-gtm
/ 已经装过?验证本机副本,不用重装
npx oh-my-skill verify jtrackingai/analytics-tracking-automation/tracking-live-gtm
安装目标可用 --agent / --scope 或 --to 明确指定;省略时只会在唯一已存在的 agent 目录上自动选择,零命中或多命中会停止并提示。content_hash 缺失或不一致均拒装。
132GitHub stars
~555最小装载
~555含声明引用
~608文本包总量
镜像托管

怎么用

技能原文 SKILL.md作者撰写 · Apache-2.0 · 68378e0

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](../../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-gtm was 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
  • [../../references/event-schema-guide.md](../../references/event-schema-guide.md)
  • [../../references/output-contract.md](../../references/output-contract.md)
  • [../../references/architecture.md](../../references/architecture.md)
按 Apache-2.0 许可原样转载,未经改动 · 在 GitHub 查看 →

评论

登录即可评论;带「已验证安装」的,是发布者名下有本店的安装或持有记录。
…