event-tracking-skill

Category: Data & AI | Uploader: jtrackingai | Downloads: 0 | Version: v1.0（Latest）

End-to-end GA4 + GTM tracking skill for site analysis, page grouping, schema design, GTM sync, preview QA, and publish readiness across generic sites and Shopify.

Changelog: Source: GitHub https://github.com/jtrackingai/event-tracking-skill

Directory Structure

Current level: tree/main/

📁 .codex/
- 📄 INSTALL.md 942 B
📁 .github/
- 📁 ISSUE_TEMPLATE/
  - 📄 bug_report.md 504 B
  - 📄 config.yml 400 B
  - 📄 feature_request.md 387 B
  - 📄 site_compatibility.md 554 B
📁 agents/
- 📄 openai.yaml 437 B
📁 docs/
- 📁 assets/
  - 📄 .gitkeep 1 B
  - 📄 jtracking-social-preview.png 978.1 KB
- 📄 README.codex.md 4.7 KB
- 📄 README.install.md 4.5 KB
- 📄 skills.md 4.9 KB
📁 references/
- 📄 architecture.md 6.3 KB
- 📄 crawl-guide.md 2.6 KB
- 📄 event-schema-guide.md 10.6 KB
- 📄 ga4-event-guidelines.md 4.8 KB
- 📄 gtm-troubleshooting.md 3.5 KB
- 📄 output-contract.md 10.6 KB
- 📄 page-grouping-guide.md 4.7 KB
- 📄 preview-report.md 5.7 KB
- 📄 shopify-workflow.md 3.6 KB
- 📄 skill-map.md 3.8 KB
📁 runtime/
- 📁 skill-runtime/
  - 📄 common.mjs 14.2 KB
  - 📄 self-update.mjs 3.3 KB
  - 📄 update-check.mjs 1.5 KB
📁 scripts/
- 📄 check.mjs 14.4 KB
- 📄 doctor.mjs 1.9 KB
- 📄 export-skills.mjs 3.4 KB
- 📄 install-skills.mjs 11.4 KB
- 📄 skill-bundles.mjs 7.0 KB
📁 skills/
- 📁 tracking-discover/
  - 📁 agents/
    
    📄 openai.yaml 269 B
  - 📄 SKILL.md 1.5 KB
- 📁 tracking-group/
  - 📁 agents/
    
    📄 openai.yaml 269 B
  - 📄 SKILL.md 1.2 KB
- 📁 tracking-live-gtm/
  - 📁 agents/
    
    📄 openai.yaml 300 B
  - 📄 SKILL.md 1.7 KB
- 📁 tracking-schema/
  - 📁 agents/
    
    📄 openai.yaml 270 B
  - 📄 SKILL.md 2.2 KB
- 📁 tracking-shopify/
  - 📁 agents/
    
    📄 openai.yaml 272 B
  - 📄 SKILL.md 2.1 KB
- 📁 tracking-sync/
  - 📁 agents/
    
    📄 openai.yaml 257 B
  - 📄 SKILL.md 1.5 KB
- 📁 tracking-verify/
  - 📁 agents/
    
    📄 openai.yaml 264 B
  - 📄 SKILL.md 2.1 KB
- 📄 manifest.json 3.1 KB
📁 src/
- 📁 crawler/
  - 📄 content-dedup.ts 1.5 KB
  - 📄 html-cleaner.ts 5.5 KB
  - 📄 page-analyzer.ts 27.9 KB
  - 📄 platform-detector.ts 3.6 KB
  - 📄 url-utils.ts 6.3 KB
- 📁 generator/
  - 📄 event-schema.ts 1.2 KB
  - 📄 gtm-config.ts 20.0 KB
  - 📄 live-tracking-insights.ts 8.7 KB
  - 📄 schema-context.ts 3.9 KB
  - 📄 schema-validator.ts 8.4 KB
  - 📄 selector-check.ts 5.7 KB
- 📁 gtm/
  - 📄 auth.ts 18.5 KB
  - 📄 client.ts 11.7 KB
  - 📄 live-parser.ts 25.6 KB
  - 📄 preview.ts 22.6 KB
  - 📄 sync.ts 16.8 KB
- 📁 reporter/
  - 📄 preview-report.ts 10.6 KB
  - 📄 schema-diff.ts 5.6 KB
  - 📄 tracking-health-report.ts 3.1 KB
  - 📄 tracking-health.ts 9.7 KB
  - 📄 tracking-plan-comparison.ts 5.0 KB
- 📁 shopify/
  - 📄 pixel.ts 19.9 KB
  - 📄 schema-template.ts 24.6 KB
- 📁 workflow/
  - 📄 run-index.ts 5.3 KB
  - 📄 scenario-requirements.json 272 B
  - 📄 scenario-requirements.ts 1.3 KB
  - 📄 scenario-transition.ts 1.4 KB
  - 📄 schema-audit.ts 5.9 KB
  - 📄 state.ts 25.4 KB
  - 📄 versioning.ts 4.8 KB
- 📄 cli.ts 118.6 KB
📁 tests/
- 📄 auto-update.test.mjs 8.6 KB
- 📄 live-gtm-parser.test.mjs 2.8 KB
- 📄 skill-family.test.mjs 8.9 KB
- 📄 workflow-enhancements.test.mjs 35.3 KB
- 📄 workflow-state.test.mjs 8.4 KB
📄 .gitignore 126 B
📄 ARCHITECTURE.md 7.3 KB
📄 CONTRIBUTING.md 1.2 KB
📄 DEVELOPING.md 8.4 KB
📄 event-tracking 361 B
📄 LICENSE 11.1 KB
📄 package-lock.json 35.8 KB
📄 package.json 1001 B
📄 README.md 25.0 KB
📄 setup 2.4 KB
📄 SKILL.md 9.1 KB
📄 tsconfig.json 452 B
📄 VERSION 6 B

SKILL.md

---
name: event-tracking-skill
description: End-to-end GA4 + GTM tracking skill for site analysis, page grouping, schema design, GTM sync, preview QA, and publish readiness across generic sites and Shopify.
---

# Event Tracking Skill

Use this skill as the end-to-end coordinator for GA4 + GTM tracking delivery.

Use it when:

- the user needs a full GA4 + GTM implementation flow, from analysis to go-live readiness
- the request spans multiple workflow phases (discovery, schema, sync, verification, publish)
- the correct entry point is still unclear and you need this skill to route to the right phase

Do not assume the user wants the full workflow.

<!-- event-tracking auto-update bootstrap:start -->
## Auto-Update

This installed root skill can self-check for newer GitHub versions before you continue.

Before doing any task in this bundle:

1. Resolve the directory that contains this installed `SKILL.md`. For Codex installs it is usually `$CODEX_HOME/skills/event-tracking-skill` or `~/.codex/skills/event-tracking-skill`.
2. Run `node "<bundle-dir>/runtime/skill-runtime/update-check.mjs" --json`.
3. If the result status is `update_available`, immediately run `node "<bundle-dir>/runtime/skill-runtime/self-update.mjs" --apply`.
4. If the update succeeds, read `<bundle-dir>/SKILL.md` again before continuing so you are using the refreshed instructions.
5. If the result status is `disabled`, treat this bundle as a local development link or repo checkout and continue without updating.

<!-- event-tracking auto-update bootstrap:end -->

## Skill Family

The skill family is split into one umbrella skill plus seven phase skills:

- `tracking-discover` for crawl coverage, platform detection, and fresh artifact bootstrap
- `tracking-group` for page-group authoring and approval
- `tracking-live-gtm` for auditing the real live GTM runtime before schema generation
- `tracking-schema` for schema preparation, review, validation, and approval
- `tracking-sync` for GTM config generation and sync
- `tracking-verify` for preview QA and optional publish handoff
- `tracking-shopify` for Shopify-specific schema, sync, install, and verification rules

If the request is already bounded to one phase and that phase skill is available, route there instead of inlining the full runbook here.

Once `site-analysis.json` indicates Shopify, keep discovery and grouping shared, then let `tracking-shopify` own the Shopify-specific branch.

## Shared Contract

1. Use the repo-local wrapper `./event-tracking` for CLI commands in this repository. If the wrapper reports that `dist/cli.js` is missing, run `npm run build` first.
2. Keep one artifact directory per site (`<output-root>/<url-slug>`). Each iteration inside that artifact should use a distinct run ID with snapshots under `versions/<run-id>/`.
3. If the user already provides an artifact directory or one of its files, resume from the earliest unmet prerequisite instead of restarting from `analyze`.
4. Use `./event-tracking status <artifact-dir-or-file>` whenever the current checkpoint or next step is unclear.
5. Use `./event-tracking runs <output-root>` when the user wants to find recent site runs and does not remember the artifact directory.
6. Google OAuth client metadata is embedded in the CLI and may be overridden with `GOOGLE_OAUTH_CLIENT_ID` / `GOOGLE_OAUTH_CLIENT_SECRET`.
7. Any Playwright-backed or OAuth-triggering step must run outside a sandboxed environment by default. In practice, treat `analyze`, `validate-schema --check-selectors`, `preview`, and `sync` as non-sandbox commands, and do not first attempt them in the sandbox before retrying after interception.
8. Never auto-select a GTM account, GTM container, or GTM workspace on the user's behalf. Always show candidates and require explicit confirmation unless the user already provided the exact ID for that step.
9. Prefer scenario-first entry commands for user-facing flows: `run-new-setup`, `run-tracking-update`, `run-upkeep`, `run-health-audit`. Use `start-scenario` when the user wants a labeled scenario run without immediate template execution.
10. Use `./event-tracking scenario <artifact-dir> --set <scenario> [--sub-scenario ...] [--new-run]` for metadata-only adjustments when you should not alter execution flow.
11. Use `./event-tracking scenario-check <artifact-dir>` when the question is "is this scenario ready" rather than "what is the next workflow checkpoint".
12. Use `./event-tracking scenario-transition <artifact-dir> --to <scenario> [--reason ...]` when the user wants an auditable handoff between scenarios.
13. Do not continue past the phase boundary the user asked for. Stop after the requested phase unless the user explicitly asks to continue.

## Conversation Intake

When the user enters through chat and has not yet provided a bounded phase, artifact directory, or exact command, start with an intent-first intake.

Classify the request into one of these entry intents:

- `resume_existing_run`: the user already has an artifact directory or one of its files; inspect the artifacts and use `status`
- `new_setup`: net-new tracking implementation from scratch; prefer `run-new-setup`, then follow its recommended next step
- `tracking_update`: revise or extend an existing implementation; prefer `run-tracking-update`
- `upkeep`: routine maintenance, review, or incremental QA on an existing setup; prefer `run-upkeep`
- `tracking_health_audit`: audit-only assessment of current live tracking; prefer `run-health-audit`
- `analysis_only`: crawl/bootstrap/discovery only without committing to the full workflow yet; route to `tracking-discover` and stop after `analyze`

Rules:

- Do not ask the user to choose between `scenario` and `analyze`. `scenario` is run-intent orchestration metadata; `analyze` is only one execution step.
- If intent is ambiguous, ask one short plain-language intake question using user-facing terms such as "new setup", "update existing tracking", "upkeep", "health audit", "analyze only", or "resume an existing run".
- If the user gives a fresh URL and asks to set up tracking, default to `new_setup`.
- If the user gives a fresh URL and only asks to inspect the site, analyze structure, or review current tracking signals, default to `analysis_only`.
- If the user gives an artifact directory or workflow file, default to `resume_existing_run` instead of restarting from `analyze`.

## Routing Rules

Route by user intent and current artifacts:

- fresh URL, crawl request, or no artifacts yet: start with `tracking-discover`
- `site-analysis.json` with missing or unconfirmed `pageGroups`: route to `tracking-group`
- confirmed `site-analysis.json` with detected live GTM container IDs but no live baseline review yet: route to `tracking-live-gtm`
- confirmed `site-analysis.json` or an in-progress `event-schema.json`: route to `tracking-schema`
- `gtm-config.json`: route to `tracking-sync`
- `gtm-context.json`: route to `tracking-verify`, with publish treated as a separate explicit action
- Shopify platform confirmation: keep shared early stages, then hand off to `tracking-shopify`

If only the root skill is available, follow the same routing logic directly and stop at the matching phase boundary.

## Stop Rules

- Do not bypass page-group approval before `prepare-schema`.
- For key decision checkpoints, always require explicit user confirmation before continuing:
  - `pageGroups` (before `confirm-page-groups` and before `prepare-schema`)
  - `event-schema.json` (before `confirm-schema` and before `generate-gtm`)
  - GTM target selection (account/container/workspace during `sync`)
  - publish decision (before `publish`)
- If confirmation is missing or ambiguous, stop and ask; do not auto-proceed.
- When live GTM containers are detected on the site, do not bypass the live baseline review before schema generation.
- Do not bypass schema approval before `generate-gtm` unless the user explicitly wants `--force`.
- Treat preview QA and publish as separate decisions.
- Treat `tracking-health.json` as the publish gate; do not jump to publish when health is missing, manual-only, or blocked unless the user explicitly wants `--force`.
- Treat Shopify manual verification as the expected path for Shopify runs, not as a fallback error case.
- Treat `tracking_health_audit` as an audit-only scenario. Do not run GTM deployment actions (`generate-gtm`, `sync`, `publish`) unless the user explicitly asks to override.

## Resume And Closeout

When resuming:

- prefer `workflow-state.json` when present
- still inspect the real artifact set if warnings indicate stale gates
- use `status` when the next step is unclear

When a phase or the full workflow ends, summarize:

- artifact directory
- current checkpoint from `workflow-state.json`
- key output files from the completed phase
- next recommended command, if any
- remaining manual actions, especially for custom dimensions, Shopify install, tracking health, preview QA, or publish approval

## References

- [skill-map.md](references/skill-map.md) for the umbrella / phase skill map
- [architecture.md](references/architecture.md) for lifecycle, checkpoints, and resume semantics
- [output-contract.md](references/output-contract.md) for artifact files and gate semantics
- [shopify-workflow.md](references/shopify-workflow.md) for Shopify-specific branch expectations

Comments 0

Latest | Hot

Please login before commenting.

Loading comments...

event-tracking-skill

Directory Structure

SKILL.md

Report

Notice