What Trackbridge skills are
The Trackbridge skills are a bundle of Claude Code skills that scaffold and audit Trackbridge integrations from inside your editor. They do the parts of the integration that are well-defined enough to automate but have enough surface area that doing them by hand is tedious — installing both packages, wiring trackers, running the OAuth dance, mapping conversion actions, integrating a CMP.
They’re not required. Trackbridge is a TypeScript SDK; you can integrate it from the Quick start without touching Claude Code. The skills exist for the case where you have Claude Code, prefer to delegate the boilerplate, and want the consistency of every project being set up the same way.
What’s in the bundle
Section titled “What’s in the bundle”| Skill | Purpose |
|---|---|
trackbridge | Router. Decides which sibling skill to dispatch based on what your project needs. |
trackbridge-setup | First-time install: packages, tracker modules, env vars. |
trackbridge-ads-oauth | The Google Ads API OAuth flow, end to end. |
trackbridge-conversions | Wires trackConversion calls into checkout success and server webhooks. |
trackbridge-consent | Connects your CMP (Cookiebot, OneTrust, Iubenda, custom) to updateConsent. |
The skills install together and reference each other through the router. You don’t pick one — you install the bundle and the router decides which one applies to whatever you’re doing right now.
When the skills help
Section titled “When the skills help”- You’re starting a new integration. The router walks you through
trackbridge-setup, thentrackbridge-ads-oauth, thentrackbridge-conversions, then (if you have a CMP)trackbridge-consent. Each step writes the right files for your framework. - You’re adding a new conversion type to an existing integration.
trackbridge-conversionsknows the call shape, the dual-send rules, and the click-identifier forwarding pattern. - You’re stuck on the OAuth flow.
trackbridge-ads-oauthwalks the developer-token / OAuth-client / refresh-token sequence, including the Workspace-vs-personal pitfall and the customer-vs-MCC distinction. - You’re integrating a CMP for the first time.
trackbridge-consenthas the wiring patterns for the four common CMPs and a generic recipe for custom ones.
When the skills don’t help
Section titled “When the skills don’t help”- You don’t use Claude Code. That’s fine — the docs are the source of truth. The skills are convenience.
- You’re building tooling on top of Trackbridge. The skills target application code; building a meta-tool wants the SDK API reference directly.
- You need a different transport (Meta CAPI, TikTok Events API, etc.). Trackbridge is Google Ads + GA4. The skills follow the SDK’s scope.
What the skills will never do
Section titled “What the skills will never do”- Obtain your Google Ads API secrets for you. They walk you through the steps; the actual click-throughs in Ads UI and OAuth Playground are yours.
- Choose or install a CMP. They wire whatever you have.
- Decide your conversion strategy. They know how to fire conversions; what counts as a conversion in your business is your call.
- Run in production. They are development-time tools. The SDK runs in production; the skills don’t.
Source
Section titled “Source”The skills live at github.com/trackbridge/skills under MIT. Each skill is a Markdown file (SKILL.md) plus optional reference material. They’re plain text — you can read them before installing to see exactly what they’ll do.
- Installing the skills — the install command.
trackbridge— what the router skill decides.