Skip to content
Marketing
Skill

/tracking-discover

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

From plugin
analytics-tracking-automation
1377 skills
Install
$ npx -y skills add jtrackingai/analytics-tracking-automation --skill tracking-discover --agent claude-code

How it fires

How this skill gets triggered: by you, by Claude, or both.

  • Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
  • You can call itInvoke it directly when you want it.
  • Slash command/tracking-discover

Context preview

The summary Claude sees to decide when to auto-load this skill.

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

SKILL.md

tracking-discover.SKILL.md
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.

Tracking Discover

Use this skill for analysis-only work and fresh workflow bootstrap.

Inputs

  • target URL
  • output root directory
  • optional Shopify storefront password

Commands

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

Required Output

Produce and share:

  • `<artifact-dir>/site-analysis.json`
  • `<artifact-dir>/workflow-state.json`

Report:

  • pages analyzed
  • skipped URLs
  • warnings
  • detected `dataLayer` events
  • detected live GTM container IDs
  • detected platform

Closeout Style

  • default to a short human-readable analysis summary before listing files
  • summarize coverage, platform, GTM detection, and notable warnings first
  • do not dump raw page HTML, raw JSON, or full URL inventories unless the user explicitly asks for them
  • list generated files and the next command only after the summary

Stop Boundary

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>

References

  • [../../references/crawl-guide.md](../../references/crawl-guide.md)
  • [../../references/architecture.md](../../references/architecture.md)
  • [../../references/output-contract.md](../../references/output-contract.md)
  • [../../references/telemetry-consent.md](../../references/telemetry-consent.md)
Read more
Ships withanalytics-tracking-automation

analytics-tracking-automation is a local-first AI skill for planning, reviewing, and delivering GA4 + GTM tracking.

Get the whole plugin
Stats
139
Stars
39
Forks
Maintained
Maintenance
TypeScript
Language
Apache-2.0
License
4mo ago
Last commit
5mo ago
Created

Repo: jtrackingai/analytics-tracking-automation