‹ 首页

tracking-verify

@jtrackingai · 收录于 1 周前

Use when the user wants preview QA, failure interpretation, release readiness, or an explicit publish handoff.

场景上线前检查质量验证

适合你，如果需要在发布前做预览QA和失败解读

/ 下载安装
tracking-verify.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-verify
/ 通过 bash 安装
curl -fsSL https://oh-my-skill.com/install.sh | bash -s -- jtrackingai/analytics-tracking-automation/tracking-verify
/ 已经装过?验证本机副本,不用重装
npx oh-my-skill verify jtrackingai/analytics-tracking-automation/tracking-verify
安装目标可用 --agent / --scope 或 --to 明确指定;省略时只会在唯一已存在的 agent 目录上自动选择,零命中或多命中会停止并提示。content_hash 缺失或不一致均拒装。
132GitHub stars
~545最小装载
~545含声明引用
~588文本包总量
镜像托管

怎么用

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

Tracking Verify

Use this skill for verification and optional publish handoff.

Inputs
  • <artifact-dir>/event-schema.json
  • <artifact-dir>/gtm-context.json
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 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:

  • blockers
  • expected failures
  • selector mismatches
  • unexpected fired events outside the approved schema
  • release readiness

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.

Required Output

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/
  • updated <artifact-dir>/workflow-state.json
Closeout Style
  • default to a verification verdict first: healthy, blocked, or manual follow-up required
  • summarize blockers, unexpected events, and release-readiness in plain language before listing files
  • keep raw preview data and artifact references after the summary
Stop Boundary
  • stop after preview if the user only asked for QA
  • publish only when the user explicitly wants to affect the live site

If the platform is Shopify, switch to the Shopify-specific rules in tracking-shopify.

References
  • [../../references/preview-report.md](../../references/preview-report.md)
  • [../../references/gtm-troubleshooting.md](../../references/gtm-troubleshooting.md)
  • [../../references/output-contract.md](../../references/output-contract.md)
按 Apache-2.0 许可原样转载,未经改动 · 在 GitHub 查看 →

评论

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