Install
$ agentstack add skill-jtrackingai-analytics-tracking-automation-tracking-group ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Tracking Group
Use this skill when the work starts from site-analysis.json and the goal is to produce approved pageGroups.
Inputs
/site-analysis.json
Workflow
- Read the current
pageGroupsand 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 /site-analysis.json
Required Output
Produce and share:
- updated
/site-analysis.json - updated
/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 /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 /site-analysis.json
References
- [../../references/page-grouping-guide.md](../../references/page-grouping-guide.md)
- [../../references/output-contract.md](../../references/output-contract.md)
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: jtrackingai
- Source: jtrackingai/analytics-tracking-automation
- License: Apache-2.0
- Homepage: https://www.jtracking.ai/skills
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.