lookup

Files (1)

• SKILL.md

SKILL.md (first lines)

## Purpose
The cheapest way to answer "who is this / where is their file / what do I have on them". The CRM keeps an SQLite index of every dossier, so a lookup costs ~100 tokens instead of a repo search. Read as little as possible: one index search, one outline, and at most one section.

Request: $ARGUMENTS

## Rules
- **Never locate records by searching files.** No Grep, Glob, `find`, `ls` or Read over the CRM folder to find a person — the index already has them. Only read a dossier file directly if the user asks you to edit it by hand.
- If the CRM tools are not available yet, load them first with ToolSearch: `select:mcp__plugin_crm_crm__crm_search,mcp__plugin_crm_crm__crm_outline,mcp__plugin_crm_crm__crm_read,mcp__plugin_crm_crm__crm_recent`. If they still cannot be loaded, the MCP server is not connected — tell the user to run `/crm:setup` and stop (do not fall back to searching files).

## Workflow

### 1. Nothing to look up
If the request is empty, call `crm_recent` (limit 10) and show it, then say: "Ask about anyone with `/crm <name>` or just mention them with 'crm'."

### 2. Find the record
Call `crm_search` with `query` = the name, company, alias or dossier code, `paths: true`, `limit: 5`.
- **One match** → go to step 3.
- **Several matches** → show the compact table (ID, name, org, category, last contact) and ask which one with AskUserQuestion. Do not read anything yet.
- **No match** → retry once with the surname, a nickname, or the company name. Still nothing → say so plainly and offer to create a dossier (`crm_create`).
- For organizations you can also filter: `orgType` (e.g. `PM`) or `orgGroup` (e.g. `LENDING`).

### 3. Point to the file
Call `crm_outline` for the matched ID and answer with a short card:

**<Name>** (<ID>) — <org> · <category> · <status> · last contact <date>
Dossier: `<folder path>`

| Section | File | Filled |
|---|---|---|
| index | `<folder>/INDEX.md` | 64% |
| … | … | … |

Keep it to the card — no summary of contents the user did not ask for.

### 4. Answer a specific question (only if asked)
If the request includes a question ("email?", "when did we last talk?", "what did she say about the offer?"), read **one** section with `crm_read` and answer from it:
- contact details, org, title, aliases → `index` (or `profile`)
- last conversation, what was said, follow-ups → `log`
- background, career → `profile`
- personality, motives → `intelligence-profile`
- a company's lending, deals, projects… → its type file (`lending`, `deal-flow`, `projects`, …) from the outline

Quote the answer with the file it came from. If that section does not answer it, say which section likely does and ask before reading more.

### 5. Next step
End with one line offering the obvious follow-up: `/crm:intel-briefing <name>` for a full brief, `/crm:post-meeting <name>` to log an interaction, or `crm_connections` to see who they are linked to.

From reggiechan74/crm-mcp-server, MIT.

More from reggiechan74/crm-mcp-server