FreePublished on GitHub

tracking-sync

Use when the user wants GTM-ready config generation, GTM workspace sync, or container selection from an approved schema.

The English summary is being prepared. Showing the original description.

jtrackingai/analytics-tracking-automation

Works withShopify

See how to install

Files included (2)

SKILL.md2.6 KB
agents/openai.yaml257 B

SKILL.md (original)

Review the instructions the agent will receive before you install.

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.
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

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

More skills from this repository

analytics-tracking-automation

Free

Use when you need GA4 + GTM tracking delivery from site discovery through publish, or when the right phase entry point is still unclear.

The English summary is being prepared. Showing the original description.

jtrackingai/analytics-tracking-automation144Updated Apr 29, 2026

tracking-discover

Free

Use when the user wants crawl coverage, platform detection, dataLayer discovery, or a fresh artifact directory before grouping and schema work.

The English summary is being prepared. Showing the original description.

jtrackingai/analytics-tracking-automation144Updated Apr 29, 2026

tracking-group

Free

Use when the work starts from `site-analysis.json` and the user wants page-group authoring, grouping adjustments, or page-group approval.

The English summary is being prepared. Showing the original description.

jtrackingai/analytics-tracking-automation144Updated Apr 29, 2026

tracking-live-gtm

Free

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

The English summary is being prepared. Showing the original description.

jtrackingai/analytics-tracking-automation144Updated Apr 29, 2026

tracking-schema

Free

Use when the user wants schema preparation, event design, selector validation, schema review, or event-spec generation.

The English summary is being prepared. Showing the original description.

jtrackingai/analytics-tracking-automation144Updated Apr 29, 2026

tracking-shopify

Free

Use when the platform is Shopify or the run needs the Shopify-specific schema, sync, install, or verification branch.

The English summary is being prepared. Showing the original description.

jtrackingai/analytics-tracking-automation144Updated Apr 29, 2026

See all skills by jtrackingai

Report a problem with this skill

Install

Install with a command

npx skills add https://github.com/jtrackingai/analytics-tracking-automation --skill tracking-sync

Paste it into your terminal and run it (requires Node.js). You can choose which agents to install it for, such as Claude Code or Codex.

Ask your agent

Please install the following Agent Skill.
https://github.com/jtrackingai/analytics-tracking-automation/tree/main/skills/tracking-sync

First review SKILL.md and the bundled files and confirm there is nothing suspicious (such as sending data externally or reading credentials). Then place it in ~/.claude/skills/tracking-sync/ for Claude Code, or ~/.agents/skills/tracking-sync/ for Codex.

Send this text to Claude Code or Codex as is. It checks the contents before installing.

View source on GitHub

Repository: jtrackingai/analytics-tracking-automation
Stars: 144
Forks: 41
Category: Other
License: Apache-2.0
Original language: English
Last updated: Apr 29, 2026

A skill is a set of instructions and scripts for an agent. cccskills does not guarantee that skills are safe. Review the contents before you install.