القائمة
Use when the work starts from `site-analysis.json` and the user wants page-group authoring, grouping adjustments, or page-group approval.
التثبيت باستخدام 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 crawl coverage, platform detection, dataLayer discovery, or a fresh artifact directory before grouping and schema work.
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.
| name | tracking-group |
| description | Use when the work starts from `site-analysis.json` and the user wants page-group authoring, grouping adjustments, or page-group approval. |
Use this skill when the work starts from site-analysis.json and the goal is to produce approved pageGroups.
<artifact-dir>/site-analysis.jsonpageGroups and page inventory../event-tracking confirm-page-groups <artifact-dir>/site-analysis.json
Produce and share:
<artifact-dir>/site-analysis.json<artifact-dir>/workflow-state.jsonStop after page-group approval unless the user explicitly asks to continue into schema work.
A broad request such as "full workflow" or "全流程" does not count as page-group approval.
Do not run ./event-tracking confirm-page-groups <artifact-dir>/site-analysis.json --yes on the user's behalf unless the user explicitly confirms the current page groups in the current turn.
Useful follow-up:
./event-tracking prepare-schema <artifact-dir>/site-analysis.json