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.
Plugin projects from marketplace gtm-operator in sarahcallmesmadds/gtm-operator. Commands read from the repo's manifest — 1 month ago.
commsWrite the update that tells the people affected by a project what changed, as one Project Update memo. Use when the user says "write the project update", "announce this change", "tell people about this", "who needs to know", or whenever a project changes something other people depend on. Not on a sc
newCreate the tasks for a project that scope has already created, and move that project from Scoped to In progress. Also fills in a project someone created by hand. Use when the user says "start the project", "break this into tasks", "create the tasks", "let's build it", or after scope offers this pre-
problem-scanFind problems that keep coming up and that nobody has written down, from bounded conversation, meeting, CRM, sales-engagement and support context the user selects, and hand the ones worth writing up to problem-statement pre-filled. Use when the user says "what problems keep coming up", "scan for pro
problem-statementWrite the case that something is worth fixing, before anyone proposes a fix, as one Problem Statement memo in the Memos log. Use when the user says "write the problem statement", "write up this problem", "make the case for fixing this", when problem-scan hands one over, or before scoping anything. N
scopeWork out what a project actually is, what it deliberately is not, and whether it should be built at all, then create the project row at Scoped or Canceled. Use when the user says "scope this", "should we build this", "turn this problem into a project", "what would this take", or after a problem stat
shipRecord that a project shipped and close it, as one Release memo and the move from In progress to Done. Use when the user says "we shipped it", "write the release", "close the project", "mark it done", or when work reaches the people who will use it, not when it merges. Lists open tasks and asks befo
problem-statement-agentFinds a recurring problem in bounded company context or works from a problem the user already knows, then builds the evidence-based case that it is worth fixing before anyone proposes a solution. It may search and synthesize inside the scope the user approved, but it writes a Problem Statement memo
notionconnects to: https://mcp.notion.com/mcp
granolaconnects to: https://mcp.granola.ai/mcp
gongconnects to: https://mcp.gong.io/mcp
slackconnects to: https://mcp.slack.com/mcp
gmailconnects to: https://gmailmcp.googleapis.com/mcp/v1
hubspotconnects to: https://mcp.hubspot.com/anthropic
salesforceconnects to: https://api.salesforce.com/platform/mcp/v1/platform/sobject-reads
outreachconnects to: https://api.outreach.io/mcp
intercomconnects to: https://mcp.intercom.com/mcp
pylonconnects to: https://mcp.usepylon.com/
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
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
Talk like caveman. Cut filler. Keep technical details explicit.
22 skills · 1 command · 3 agents · hooks
Persistent memory for Claude Code: the next session starts where the last one left off.
29 skills · 1 MCP server · hooks
tasteskill 2.5.1: professional company websites at the figma.com and x.ai level, with one section per screen, real photographs, real product UI, effects kept for tech and gaming pages, and a real-browser checker and finish gate.
1 skill
AI-powered codebase understanding — analyze, visualize, and explain any project
9 skills · 10 agents · hooks
Open-source AI job search that runs locally in your AI coding CLI: scan job portals, evaluate listings into a structured A-H report with a 1-5 score, tailor your CV, track applications
5 skills · hooks
Cross-session memory and token savings for coding agents.
6 skills · 1 agent · 1 MCP server · hooks
This page updates itself from your repo. Add the badge to your README, or get it Featured to pin it above the organic results with a followed link to your site.