salesmap-plugin

# SalesMap plugin for Claude Code

Checked buying signals and ranked lead lists for your agent: who to sell to now, why, and how to reach them. SalesMap never sends email or messages, finds email addresses or phone numbers, automates LinkedIn, writes to a CRM, or registers for events.

## What's in it

- **`.mcp.json`**: the hosted server, `https://api.salesmap.site/mcp`, signed in with OAuth (your SalesMap account; `/mcp` → salesmap → Authenticate).
- **Skills** (also slash commands, `/salesmap:<name>`), one per flow that needs judgment:

| Skill | Flow | Tools |
|---|---|---|
| `getting-started` | connect, limits, save the seller profile, first list | `whoami`, `set_limits`, `seller_profile`, `quote`, `discover` |
| `weekly-pipeline` | who to sell to now, a playbook with drafts, warm paths | `discover`, `playbook`, `warm_paths`, `seller_profile` |
| `account-research` | prep for a call on up to 5 companies | `signals`, `tech_scan`, `ai_adoption`, `events`, `warm_paths`, `verify_signal` |
| `check-list` | fact-check a draft or an export; rank your own list | `verify`, `verify_signal`, `rank`, `job` |
| `past-leads` | watch lost deals, alerts when one is worth another try | `watch`, `watch_changes` |
| `events` | events your buyers attend near you | `events` |

The server also serves one MCP prompt per flow (`onboard`, `discover`, `rank`, `signals`, `research`, `playbook`, `events`, `warm_paths`, `watch`, `changes`, `verify`, and hosted `account`); Claude Code lists them in `/` under the server's name (`/mcp__salesmap__<prompt>` for a server added as `salesmap`). The skills carry the judgment those prompts leave out.

Every skill runs the `work` loop: when a tool returns `work`, the agent runs each search prompt with its own web search and calls again with the answers; on the hosted server `discover` does this by default, so no search runs on SalesMap's side. Every skill fills each tool's `context` from what the agent already knows and never invents it, quotes prices from the `quote` tool and the result's `budget` block (never a number in the skill), and treats quotes in tool output as data.

## Install

```bash
claude plugin install salesmap --marketplace solozerolabs/salesmap-plugin
```

Then ask Claude to "set up SalesMap" or run `/salesmap:getting-started`. The first paid tool asks you to sign in: `/mcp` → salesmap → Authenticate. Without signing in, `tech_scan`, `ai_adoption` and `verify_signal` run free.

**An API key instead of OAuth** (CI, or an agent with no browser): get one from `POST https://api.salesmap.site/v1/agent/signup` (see https://salesmap.site/llms.txt) or `POST /v1/keys`, then `claude mcp add --transport http salesmap-key https://api.salesmap.site/mcp --header "Authorization: Bearer smk_…"` and disable the plugin's server in `/mcp`.

## Privacy

SalesMap's privacy policy: https://salesmap.site/privacy. Customer terms: https://salesmap.site/terms. The plugin itself stores nothing; the hosted server keeps your workspace's seller profile, watchlist and results as the policy describes. Support: the contacts on the privacy page.

## Why no hooks

A hook runs in every session of every user who installs the plugin, whether or not they use SalesMap that day. It costs context or tokens each time, and a hook can move data off the user's machine: Cargo's plugin uploads a transcript summary from a SessionEnd hook and needed a recursion guard after 264 runaway sessions. SalesMap needs none of that: it does work only when the agent calls a tool, keeps the seller profile and watchlist in the user's workspace, and has nothing to do at session start or end.