GTM Agent

Trigger

Apply this skill when a request concerns getting GTM Agent deployed, connected, checked, or upgraded for an organization, or asks whether that is possible and what it needs, before anything is created.

Scope

One deployment is: a private copy of the agent template eliasstravik/gtm-agent as the repository gtm-agent-<slug>, deployed as the Vercel project gtm-agent-<slug>; a Slack connector slack/gtm-agent-<slug> installed in the organization's Slack; the workspace repository gtm-<slug>; and, when workflows are enabled, the workflow project gtm-<slug> that gtm-workflow's shared setup --deploy takes live (project, Neon, share project, secrets, the first push of workflows/) and wires to this agent, which agent setup runs as its last step. The scripts in scripts/ use the GitHub and Vercel CLIs; references/setup.md lists what setup creates. Connection names come from the Vercel Secret Note or local label, following Connections naming. The agent remains optional for that setup. The workspace's contents belong to the other gtm skills.

Inputs

The request; the organization's workspace slug (the contract's slug rule; from an existing ~/.gtm/<slug>/ when one exists); the Vercel team slug (vercel teams ls; ask when more than one); the GitHub owner (the signed-in user unless the request names an organization); optionally a Slack channel id (C0…, at the bottom of a channel's About tab) for workflow notifications; references/setup.md.

Roles

The user has the GitHub and Vercel CLIs signed in on this computer, authorizes the Slack install when required, either directly or through their authorized browser agent, adds the Neon database to the workflow project through Vercel's Neon integration (Production only, preview branching off) and accepts Neon's marketplace terms the first time a team uses it, invites the bot to a channel, and says the first sentence in Slack; the agent runs the scripts, relays exactly what the user must do, and reports the outcome.

Procedure