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.
Plugin software from marketplace gtm-operator in sarahcallmesmadds/gtm-operator. Commands read from the repo's manifest — 1 month ago.
backfillFind the tools you already pay for from signed agreements, spend and accounting records, a named contract folder, your own mailbox, and bounded Slack context, then offer them as candidates approved one at a time. Use after setup, when the user says "backfill the directory", "find what we subscribe t
contractsWhat renewals and notice deadlines are coming up in the Software directory, and what happens if you do nothing. Use when the user asks "what's renewing", "any contracts coming up", "what do we need to cancel", "what's due this quarter", or before budget planning. Read-only; changes nothing, cancels
newAdd one tool to the Software directory, filled in conversation. Use when the user says "add this tool", "we just bought", "put Gong in the directory", "write down what we use for", or notices a tool everybody uses was never written down. Checks for a duplicate before drafting; never guesses an owner
reviewA full pass over one tool in the Software directory, confirming everything on the row is still true, and the only skill that moves Last reviewed after creation stamped it. Use before a renewal, when somebody who owned a tool leaves, when a row's freshness stamp is old, or when the user says "review
updateChange the facts on a tool that is already in the Software directory, one row at a time. Use when the user says a vendor was acquired or renamed, a contract was extended, the cost moved, the owner left, a tool was dropped, or "update the row for". Never moves Last reviewed; shows a before and after
notionconnects to: https://mcp.notion.com/mcp
boxconnects to: https://mcp.box.com
google-driveconnects to: https://drivemcp.googleapis.com/mcp/v1
gmailconnects to: https://gmailmcp.googleapis.com/mcp/v1
slackconnects to: https://mcp.slack.com/mcp
rampconnects to: https://ramp-mcp-remote.ramp.com/mcp
quickbooksconnects to: https://mcp.quickbooks.intuit.com/mcp
docusignconnects to: https://mcp.docusign.com/mcp
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
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
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
Package any website or local web build into a lightweight desktop app with Pake CLI.
1 skill
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.