tracking-discover
Use when the user wants crawl coverage, platform detection, dataLayer discovery, or a fresh artifact directory before grouping…
@jtrackingaiInstall SkillMarketing
Skill
/tracking-sync
Use when the user wants GTM-ready config generation, GTM workspace sync, or container selection from an approved schema.
Claude Code
$ npx -y skills add jtrackingai/analytics-tracking-automation --skill tracking-sync --agent claude-code
Codex
$ npx skills add jtrackingai/analytics-tracking-automation --skill tracking-sync -a codex -y
Cursor
$ npx skills add jtrackingai/analytics-tracking-automation --skill tracking-sync -a cursor -y
Gemini CLI
$ npx skills add jtrackingai/analytics-tracking-automation --skill tracking-sync -a gemini-cli -y
GitHub Copilot
$ npx skills add jtrackingai/analytics-tracking-automation --skill tracking-sync -a github-copilot -y
OpenCode
$ npx skills add jtrackingai/analytics-tracking-automation --skill tracking-sync -a opencode -y
Windsurf
$ npx skills add jtrackingai/analytics-tracking-automation --skill tracking-sync -a windsurf -y
SKILL.md
tracking-sync.SKILL.mdname: tracking-sync
description: Use 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](../../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.
- `sync` calls Google's official GTM API via interactive OAuth. The consent flow needs outbound HTTP and a local loopback callback on `127.0.0.1`; run `sync` in an environment that permits both.
- Run `sync` with 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 `sync` only when exact `--account-id`, `--container-id`, and `--workspace-id` values 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
- [../../references/output-contract.md](../../references/output-contract.md)
- [../../references/gtm-troubleshooting.md](../../references/gtm-troubleshooting.md)
Read more
name: tracking-sync description: Use 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](../../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.
- `sync` calls Google's official GTM API via interactive OAuth. The consent flow needs outbound HTTP and a local loopback callback on `127.0.0.1`; run `sync` in an environment that permits both.
- Run `sync` with 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 `sync` only when exact `--account-id`, `--container-id`, and `--workspace-id` values 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
- [../../references/output-contract.md](../../references/output-contract.md)
- [../../references/gtm-troubleshooting.md](../../references/gtm-troubleshooting.md)
Stats
145
Stars
41
Forks
Quiet
Maintenance
TypeScript
Language
Apache-2.0
License
Last commit
Created
Ships withanalytics-tracking-automation
analytics-tracking-automation is a local-first AI skill for planning, reviewing, and delivering GA4 + GTM tracking.
1457 skills
Stars on GitHub
Momentum
- stars in total
- 145
Other skills on analytics-tracking-automation.
@jtrackingaiInstall Skilltracking-group
Use when the work starts from `site-analysis.json` and the user wants page-group authoring, grouping adjustments, or page-group…
@jtrackingaiInstall Skilltracking-live-gtm
Use when the user wants to inspect the real live GTM runtime before schema generation or compare multiple live GTM containers.
@jtrackingaiInstall Skilltracking-schema
Use when the user wants schema preparation, event design, selector validation, schema review, or event-spec generation.
@jtrackingaiInstall Skilltracking-shopify
Use when the platform is Shopify or the run needs the Shopify-specific schema, sync, install, or verification branch.
@jtrackingaiInstall Skilltracking-verify
Use when the user wants preview QA, failure interpretation, release readiness, or an explicit publish handoff.
@jtrackingaiInstall SkillMore skills from other plugins.
Auto-invoked
ab-testing
When the user wants to plan, design, or implement an A/B test or experiment, or build a growth experimentation program. Also use…
@coreyhaines31Install Skillseo
Comprehensive SEO analysis for any website or business type. Full site audits, single-page analysis, technical SEO (crawlability,…
@agricidanielInstall Skillbrag
Turn the current project website into a short, polished, shareable launch video using Hyperframes. Use when someone says "/brag",…
@latent-spacesInstall Skillgeo-audit
Full website GEO+SEO audit with parallel subagent delegation. Orchestrates a comprehensive Generative Engine Optimization audit…
@zubair-trabzadaInstall SkillQuestions about tracking-sync.
- Which coding agents can use tracking-sync?
- tracking-sync installs in Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, OpenCode and Windsurf with the skills CLI, using each agent's flag shown on this page. Flowy's auto-invocation, which fires a skill when your prompt matches, runs in Claude Code only.