Is tracking-group safe to install?

SaferSkills independently audited tracking-group (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.

CategoryWeightCategory scoreContribution

Securityprompt, exec, net, exfil, eval

35%

100

35.0 pts

Supply chainhash, typosquat, maintainer, lockfile

20%

100

20.0 pts

Maintenancestaleness, pinning, CI

15%

100

15.0 pts

TransparencySKILL.md, perms, README

15%

100

15.0 pts

Communityinstalls, verify, response

15%

100

15.0 pts

Findings & checks · 0 flagged

Securityscore 100 · 0 findings

✓—All security checks passedNo findings in this category for the latest scan.pass

Supply chainscore 100 · 0 findings

✓—All supply chain checks passedNo findings in this category for the latest scan.pass

Maintenancescore 100 · 0 findings

✓—All maintenance checks passedNo findings in this category for the latest scan.pass

Transparencyscore 100 · 0 findings

✓—All transparency checks passedNo findings in this category for the latest scan.pass

Communityscore 100 · 0 findings

✓—All community checks passedNo findings in this category for the latest scan.pass

The primary manifest — the file an agent reads to learn what this artifact does.

skills/tracking-group/SKILL.md · 1 file

skills/tracking-group/SKILL.md1.9 KB · Markdown

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.

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

tracking-group— agent skill

Is tracking-group safe to install?

Tracking Group

Inputs

Workflow

Required Output

Closeout Style

Stop Boundary

References

Audit the pieces. Scan the whole. Decide.