Installing the skills
The skills are distributed from github.com/trackbridge/skills as a single MIT-licensed bundle. Install all five at once — they’re built to work together through the router.
Right now: git clone
Section titled “Right now: git clone”The current install path is direct git checkout into Claude Code’s skills directory:
mkdir -p ~/.claude/skillsgit clone https://github.com/trackbridge/skills.git ~/.claude/skills/trackbridgeClaude Code reads from ~/.claude/skills/. Once cloned, the five skills are available immediately — restart Claude Code if it’s running.
To verify, invoke the router by asking Claude Code something like “add Trackbridge to this project”. It should load the trackbridge skill and present its routing decision.
To update later:
cd ~/.claude/skills/trackbridgegit pullThere’s no separate version pinning today; you get whatever’s on main. The repo tags releases (v0.1.0, etc.) for human reference, but the loader doesn’t consume them.
Coming: skills-lock.json
Section titled “Coming: skills-lock.json”A skills loader CLI is in flight as part of the broader Trackbridge ecosystem. When it lands, install will look like this:
{ "version": 1, "skills": { "trackbridge": { "source": "trackbridge/skills", "sourceType": "github" } }}The loader resolves the bundle, content-addresses it via hash (recorded in the lockfile), and installs all five skills under your project’s .claude/skills/. Per-project pinning, hash-verified updates, no git clone required.
This page will be updated when the loader ships.
Project-local vs user-global
Section titled “Project-local vs user-global”The git clone recipe above installs to ~/.claude/skills/, which makes the skills available across every project on your machine. To install only for one project, clone into <project>/.claude/skills/trackbridge instead. Claude Code reads from both locations (project takes precedence on conflicts).
For team setups, project-local is preferable: commit a skills/ checkout (or the future skills-lock.json) so every contributor gets the same skills with no per-machine setup.
Verifying
Section titled “Verifying”Once installed, the bundled skills should be discoverable:
ls ~/.claude/skills/trackbridge/# trackbridge-setup/# trackbridge-ads-oauth/# trackbridge-conversions/# trackbridge-consent/# README.md# package.json# scripts/In Claude Code, mention “Trackbridge” — the router skill should activate. If it doesn’t, restart Claude Code and confirm the path matches what your version of Claude Code expects.
Uninstalling
Section titled “Uninstalling”Remove the directory:
rm -rf ~/.claude/skills/trackbridgeThe skills are pure files — no daemon, no global state. Removing the directory is a complete uninstall.
See also
Section titled “See also”- What Trackbridge skills are
trackbridge— the router skill that triggers on Trackbridge mentions.