tracking-discover
Use when the user wants crawl coverage, platform detection, dataLayer discovery, or a fresh artifact directory before grouping…
Use when the platform is Shopify or the run needs the Shopify-specific schema, sync, install, or verification branch.
Claude Code
$ npx -y skills add jtrackingai/analytics-tracking-automation --skill tracking-shopify --agent claude-code
Codex
$ npx skills add jtrackingai/analytics-tracking-automation --skill tracking-shopify -a codex -y
Cursor
$ npx skills add jtrackingai/analytics-tracking-automation --skill tracking-shopify -a cursor -y
Gemini CLI
$ npx skills add jtrackingai/analytics-tracking-automation --skill tracking-shopify -a gemini-cli -y
GitHub Copilot
$ npx skills add jtrackingai/analytics-tracking-automation --skill tracking-shopify -a github-copilot -y
OpenCode
$ npx skills add jtrackingai/analytics-tracking-automation --skill tracking-shopify -a opencode -y
Windsurf
$ npx skills add jtrackingai/analytics-tracking-automation --skill tracking-shopify -a windsurf -y
name: tracking-shopify description: Use when the platform is Shopify or the run needs the Shopify-specific schema, sync, install, or verification branch.
Use this skill as the Shopify-specific branch contract after platform detection.
Use this skill when:
Shopify still uses the same early workflow as generic sites:
Use `tracking-discover` and `tracking-group` for those phases.
Schema phase:
Sync phase:
Verification phase:
Expect some or all of:
Stop after the Shopify-specific artifact or manual verification plan the user asked for.
Do not force the generic preview path on a Shopify run.
analytics-tracking-automation is a local-first AI skill for planning, reviewing, and delivering GA4 + GTM tracking.
Use when the user wants crawl coverage, platform detection, dataLayer discovery, or a fresh artifact directory before grouping…
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 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…