jtrackingai/analytics-tracking-automation / skills/tracking-sync
tracking-sync
UnverifiedUse when the user wants GTM-ready config generation, GTM workspace sync, or container selection from an approved schema.
Tracking Sync
Use this skill for Step 4 and Step 5 work.
Inputs
One of:
- approved
<artifact-dir>/event-schema.json - existing
<artifact-dir>/gtm-config.json
Workflow
If the telemetry consent prompt appears and no prior choice is recorded, stop and follow ../../references/telemetry-consent.md before continuing.
If GTM config does not exist yet:
./event-tracking generate-gtm <artifact-dir>/event-schema.json --measurement-id <G-XXXXXXXXXX>
Then sync:
./event-tracking sync <artifact-dir>/gtm-config.json
If account/container/workspace IDs are already confirmed, skip interactive selection:
./event-tracking sync <artifact-dir>/gtm-config.json --account-id <account-id> --container-id <container-id> --workspace-id <workspace-id>
Hard Rules
- Do not bypass schema approval unless the user explicitly wants
--force. - Treat custom dimensions as a blocking checklist before sync/publish.
- Never auto-select GTM account, container, or workspace for the user.
synccalls Google's official GTM API via interactive OAuth. The consent flow needs outbound HTTP and a local loopback callback on127.0.0.1; runsyncin an environment that permits both.- Run
syncwith an interactive TTY from the start whenever it may prompt for OAuth consent, account, container, workspace, or new workspace name. Non-interactive invocation will fail at the first prompt. - Use non-interactive
synconly when exact--account-id,--container-id, and--workspace-idvalues are already confirmed.
Required Output
Produce and share:
<artifact-dir>/gtm-config.json<artifact-dir>/gtm-context.json<artifact-dir>/workflow-state.json
For Shopify runs, also expect:
<artifact-dir>/shopify-custom-pixel.js<artifact-dir>/shopify-install.md
Closeout Style
- default to a short answer-first sync summary before listing files
- summarize what was generated or synced, what still needs manual selection or approval, and any blocking checklist items first
- keep file listings and follow-up commands after the summary
Stop Boundary
Stop after sync unless the user explicitly asks for verification.
Default next phase:
./event-tracking preview <artifact-dir>/event-schema.json --context-file <artifact-dir>/gtm-context.json
References
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack." | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |
| ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read. | Stars: 192k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report. | Stars: 192k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt. | Stars: 192k | Updated | Claude CodeCodex | Verified | Install |