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-automation1422026年4月29日 更新
無料GitHub で公開
tracking-verify
Use when the user wants preview QA, failure interpretation, release readiness, or an explicit publish handoff.
インストール方法を見る含まれるファイル（2）
- SKILL.md2.7 KB
- agents/openai.yaml264 B
SKILL.md（原文）
インストールする前に、エージェントに与えられる指示の中身を確認できます。
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 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
レビュー
まだレビューはありません。使ってみた感想をお寄せください。
同じリポジトリのスキル
概要と使いどころ
Use when the user wants crawl coverage, platform detection, dataLayer discovery, or a fresh artifact directory before grouping and schema work.
日本語の概要は準備中です。原文の説明を表示しています。
jtrackingai/analytics-tracking-automation1422026年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-automation1422026年4月29日 更新
Use when the user wants to inspect the real live GTM runtime before schema generation or compare multiple live GTM containers.
日本語の概要は準備中です。原文の説明を表示しています。
jtrackingai/analytics-tracking-automation1422026年4月29日 更新
Use when the user wants schema preparation, event design, selector validation, schema review, or event-spec generation.
日本語の概要は準備中です。原文の説明を表示しています。
jtrackingai/analytics-tracking-automation1422026年4月29日 更新
Use when the platform is Shopify or the run needs the Shopify-specific schema, sync, install, or verification branch.
日本語の概要は準備中です。原文の説明を表示しています。
jtrackingai/analytics-tracking-automation1422026年4月29日 更新