gtm-operator

The Process library: the living reference of how and why things are done. Finds current answers, audits stale or conflicting artifacts, and sweeps scoped documents, conversations, meetings, CRM activity, billing, and spend evidence for missing process knowledge. Proposes candidates one approval at a time. Needs the setup plugin, which it reads config from and never calls.

5 skills · 1 agent · 12 MCP servers

Runs a project from named problem to shipped release. Its problem-statement agent finds recurring problems in bounded internal, meeting, CRM, sales-engagement and support context, or works from a known problem, then writes the case that one is worth fixing only after explicit approval. The skills scope the work, create tasks, communicate changes and record the release. External connectors are read-only and Notion is the only write destination. Needs the setup plugin, which it reads config from and never calls.

6 skills · 1 agent · 10 MCP servers

The Software directory: what we use, who owns it, what we pay and when that comes round again, and what would break if it went away. Adds and maintains tools, reports renewals by consequence, and backfills from signed agreements, spend, accounting, a named contract folder, the user's own mailbox and bounded Slack context. External systems are read-only, candidates are approved one at a time, and Slack can support Importance only with exact consequence evidence. Needs the setup plugin, which it reads config from and never calls.

5 skills · 8 MCP servers

Time-stamped communication, append-only. Writes one memo of any of seven types from free-form notes or explicitly scoped Slack and Gmail context, turns a Granola or Gong meeting source into a record of what it decided, assembles the recurring team update from Projects, Calendar, Memos and Tasks rather than from memory, and finds what was said about something and when, following corrections to the end of the chain. There is no update skill and there never will be: a correction is a new memo. Needs the setup plugin, which it reads config from and never calls.

4 skills · 5 MCP servers

Imports lead lists into the CRM config names, HubSpot or Salesforce, one per install: mapped, deduped, matched to companies, on the memberships the org's grid names, verified by reading every write back, and written back to a Notion source. Every write sits behind one confirmation.

2 skills · 5 MCP servers

The GTM calendar: what is happening in market, and when. Shows what else is already aimed at the same people before it writes anything, asks how it went when a row is marked done, and answers what an audience is receiving for a window. Needs the setup plugin, which it reads config from and never calls.

3 skills · 1 MCP server

Creates the Notion databases the foundation plugins read and write, wires the relations between them, and writes the foundation's config. Nothing else in the marketplace creates a database, and nothing else writes the foundation's config. install explains the model before it asks anything, asks only the questions that are genuinely the user's to decide, and reads everything it created back out of Notion before calling itself done.

2 skills · 1 MCP server