tracking-group
Use when the work starts from `site-analysis.json` and the user wants page-group authoring, grouping adjustments, or page-group…
Use when the user wants crawl coverage, platform detection, dataLayer discovery, or a fresh artifact directory before grouping and schema work.
Claude Code
$ npx -y skills add jtrackingai/analytics-tracking-automation --skill tracking-discover --agent claude-code
Codex
$ npx skills add jtrackingai/analytics-tracking-automation --skill tracking-discover -a codex -y
Cursor
$ npx skills add jtrackingai/analytics-tracking-automation --skill tracking-discover -a cursor -y
Gemini CLI
$ npx skills add jtrackingai/analytics-tracking-automation --skill tracking-discover -a gemini-cli -y
GitHub Copilot
$ npx skills add jtrackingai/analytics-tracking-automation --skill tracking-discover -a github-copilot -y
OpenCode
$ npx skills add jtrackingai/analytics-tracking-automation --skill tracking-discover -a opencode -y
Windsurf
$ npx skills add jtrackingai/analytics-tracking-automation --skill tracking-discover -a windsurf -y
name: tracking-discover description: Use when the user wants crawl coverage, platform detection, dataLayer discovery, or a fresh artifact directory before grouping and schema work.
Use this skill for analysis-only work and fresh workflow bootstrap.
In this repository, use the repo-root wrapper:
./event-tracking analyze <url> --output-root <output-root>
`analyze` launches a real Chromium via Playwright to fetch the target site over HTTP. 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. Before `run-new-setup` or `analyze`, if the tool needs a telemetry consent answer and no prior choice is already recorded, stop and follow [../../references/telemetry-consent.md](../../references/telemetry-consent.md). Do not choose on the user's behalf, and do not continue until they answer.
Partial mode:
./event-tracking analyze <url> --output-root <output-root> --urls https://example.com/page-a,https://example.com/page-b
Produce and share:
Report:
Unless the user explicitly asks for the next phase, stop after analysis. If telemetry consent is still unanswered, stop before analysis starts and wait for the user's explicit choice.
If the user wants to continue, the default next command is:
./event-tracking status <artifact-dir>
analytics-tracking-automation is a local-first AI skill for planning, reviewing, and delivering GA4 + GTM tracking.
Use when the work starts from `site-analysis.json` and the user wants page-group authoring, grouping adjustments, or page-group…
Use when the user wants to inspect the real live GTM runtime before schema generation or compare multiple live GTM containers.
Use when the user wants schema preparation, event design, selector validation, schema review, or event-spec generation.
Use when the platform is Shopify or the run needs the Shopify-specific schema, sync, install, or verification branch.
Use when the user wants GTM-ready config generation, GTM workspace sync, or container selection from an approved schema.
Use when the user wants preview QA, failure interpretation, release readiness, or an explicit publish handoff.
When the user wants to plan, design, or implement an A/B test or experiment, or build a growth experimentation program. Also use…
Comprehensive SEO analysis for any website or business type. Full site audits, single-page analysis, technical SEO (crawlability,…
Turn the current project website into a short, polished, shareable launch video using Hyperframes. Use when someone says "/brag",…
Full website GEO+SEO audit with parallel subagent delegation. Orchestrates a comprehensive Generative Engine Optimization audit…