How do I install the Soborbo Tracking skill?

Run npx skillmds@latest add soborbo/soborbo-tracking in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Soborbo Tracking safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: makes network calls. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Soborbo Tracking?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Soborbo Tracking free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Soborbo Tracking?

Soborbo (@soborbo) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Soborbo Tracking by soborbo — Agent Skill

Name: Soborbo Tracking
Rating: 4.5 (4 reviews)
Author: Soborbo

Soborbo Tracking

MOVED — the canonical Soborbo lead-gen tracking package (Astro client lib + event-gateway onboarding) now lives IN the engine repo: github.com/Soborbo/Serverside → soborbo-tracking/. As of 2026-07-21 it is no longer a standalone claudeskills skill and there is no vendored events.json copy: the worker and the client lib share the single canonical Serverside/src/events.json. Use the copy in Serverside.

Soborbo Updated Sep 10, 2026

File contents

soborbo-tracking — MOVED to the Serverside repo

This skill was consolidated into the engine repo on 2026-07-21.

Canonical home: github.com/Soborbo/Serverside → soborbo-tracking/.

Why it moved

The package used to live here and vendor a copy of the canonical event taxonomy (events.json) plus a hand-ported copy of the per-site generator. Two machine guards (check-event-contract.mjs --engine, and the Serverside-side F1-4 contract lock) only guarded that cross-repo drift — they could not remove it. Co-locating the client lib with the gateway worker collapses the duplication entirely: one repo, one src/events.json, one scripts/generate-site.mjs, no vendoring, no drift class.

Where things are now (all in Serverside)

Client lib + components + GTM + backend-dispatch reference → soborbo-tracking/
Install runbook → soborbo-tracking/INSTALL.md
Server binding / onboarding → soborbo-tracking/server/SETUP-SERVER.md + the .claude/skills/onboard-site skill, driving the canonical scripts/generate-site.mjs
The single canonical event source → src/events.json

Consumers

The live sites (beautyflow / lomtalan / skinlab) vendor their own copy of the client lib and were not affected by the move; when they next re-vendor, pull from Serverside/soborbo-tracking/, not from here.

Frequently asked questions