Tracking group

Skill jtrackingai/analytics-tracking-automation/skills/tracking-group

AI-powered GA4 + GTM event tracking — automates site analysis, event schema, GTM sync, preview verification, and publishing. Works with Cursor, Codex, and any AI agent.

Install

npx -y skills add jtrackingai/analytics-tracking-automation --skill tracking-group

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

What its author says it does

Copied from the file, not written here

Use when the work starts from `site-analysis.json` and the user wants page-group authoring, grouping adjustments, or page-group approval.

SKILL.md

1.9 KB, as published. Nobody here has run it

Tracking Group

Use this skill when the work starts from site-analysis.json and the goal is to produce approved pageGroups.

Inputs

<artifact-dir>/site-analysis.json

Workflow

Read the current pageGroups and page inventory.
Group pages by business purpose, not just URL shape.
Present a concise table with group name, content type, URL pattern, and pages.
Default to a reviewable summary first: total groups, grouping logic, and a compact table. Do not dump raw URL lists unless the user explicitly asks for them.
Ask the user to confirm or adjust the grouping.
Record approval with:

./event-tracking confirm-page-groups <artifact-dir>/site-analysis.json

Required Output

Produce and share:

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

Closeout Style

default to a page-group summary first: group count, grouping logic, and a compact group table
keep the summary reviewable in chat; do not dump full raw URL lists unless the user explicitly asks
list files and the next command only after the summary

Stop Boundary

Stop 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