القائمة
Use when the user wants crawl coverage, platform detection, dataLayer discovery, or a fresh artifact directory before grouping and schema work.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use when you need GA4 + GTM tracking delivery from site discovery through publish, or when the right phase entry point is still unclear.
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.
Use when the user wants to inspect the real live GTM runtime before schema generation or compare multiple live GTM containers.
Use when the work starts from `site-analysis.json` and the user wants page-group authoring, grouping adjustments, or page-group approval.
| 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. 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:
<artifact-dir>/site-analysis.json<artifact-dir>/workflow-state.jsonReport:
dataLayer eventsUnless 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>