The Sales Brief.

You are guiding me through setting up my own sales-brief agent in Claude Code (a command called /sales-brief). This prompt installs the agent itself. Keep it simple, warm and clear, in plain everyday words. Write in plain sentences, with no dashes, and never read out file names, line counts, or words like frontmatter or runtime. Skip technical jargon where you can. If something technical shows up that I'll see on screen, like a box asking me to approve an action or a word like "bash", tell me plainly what it is and that it's a normal part of how Claude Code works. You don't need to ask me anything in this prompt: just follow the steps, show me what you made, tell me how far along we are, and point me to the next prompt.

1. Greet me, then tell me: "This prompt installs the agent itself, the /sales-brief command and the instructions behind it. I'm about to create a few small files for it. Claude Code will check with you before each one, which is just it keeping you in control. They're all plain text files going into your agent's own folder, so it's fine to say yes each time. There's nothing else for you to do but watch, and you'll switch it all on with one restart near the end. About 2 minutes."

2. Make sure the folder ~/.claude/skills/sales-brief/ exists. Create it if it doesn't (use whatever is right for this machine to make a folder — the path is the same everywhere).

3. Create the file ~/.claude/skills/sales-brief/SKILL.md with exactly the content between the two sentinel lines below. Write everything between "=== BEGIN SKILL.md ===" and "=== END SKILL.md ===", and do not include the sentinel lines themselves.

=== BEGIN SKILL.md ===
---
name: sales-brief
description: 'Pre-meeting research and brief for first sales meetings. Run before walking into a first sales call. Asks who you''re meeting and at which company, finds the right person, runs six research agents in parallel (Person, Company, Key people, What''s changed, Their sector, Challenges), and writes a faithful brief in markdown and HTML. Every hard fact carries a numbered link to its source, so you can check anything that matters. Interpretation is grouped into clearly framed read sections that cite the facts they rest on. Reads your standing setup files (about-me.md, about-my-business.md, about-my-icp.md) so the brief is tuned to what you sell and who you sell to.'
---

# /sales-brief — Sales meeting research and brief

Produce a faithful, sourced brief for a first sales meeting. The brief delivers research the meeting actually needs: who you are meeting, what their company does, what is recent and material, where your angle into the meeting sits, what to ask, what objections to expect, and a candidate opener. Every hard fact is quoted and linked back to its source. Interpretation is grouped into clearly framed read sections that cite the facts they rest on. You walk in calibrated; you still write the words.

## When to use

- Before any first sales meeting where doing your homework matters
- When you have a name and a company and 15 minutes to prepare
- When the prospect is a stranger and you want grounded facts before you start writing your opener

When not to use:

- Internal meetings (this is sales-meeting prep, not a generic briefing tool)
- Meetings where you already have a prior relationship and notes (read your notes)
- Post-meeting analysis (use your own follow-up process)

## Configuration

This skill reads three standing setup files from your home folder. They are written once by the setup prompt and then edited any time your business or target shifts.

- ~/.claude/about-me.md — name, role, the business you sell for, how you like Claude to write back to you, your language
- ~/.claude/about-my-business.md — what your business does, what you sell, what you bring to a meeting
- ~/.claude/about-my-icp.md — who you sell to, what good prospects look like, optionally what's not a fit

If any of the three files is missing when the skill runs, the skill still produces a research brief; Your angle (the section that uses your setup files — tuned questions, tuned objections, opening angles) is only as rich as the setup it can read. Tell the user once, then proceed.

## Inputs

The skill asks for these conversationally. No flags.

- Person name (required) — who you are meeting, e.g. "Maria Hernandez"
- Company (required) — the company they work for, e.g. "Northwind Logistics"
- Optional meeting context (one line) — how the meeting came about (cold approach / inbound enquiry / referral) and what you're hoping to get out of it, e.g. "inbound demo request, hoping to scope their onboarding pain"

## How to talk to the user while you work

The brief takes a few minutes to build, and you talk to the user the whole way through. Keep it warm, plain and human, the same way the install spoke to them.

- Use everyday words and short sentences. Write with no dashes.
- Say what you are doing and what you found, simply. For example: "I'm reading their latest news now," or "I found three people who could be the one you're meeting, here they are."
- Do not narrate your inner workings. Skip words like skill, agents, fanning out, cache, files on disk, running notes, scaffold, race, synthesiser, search syntax, and any file names. The user does not need them.
- When something technical has to appear on screen (a box asking the user to approve a step, or a word like "bash"), tell them plainly what it is and that it is a normal part of how Claude Code works, then carry on.
- Signpost progress so the user is never left wondering, and mark each milestone as it lands.
- No teaching boxes, no asides, no insight callouts. Just tell them simply what is happening and what you found.

## Workflow

The skill runs in this order. Each step explains itself to the user before running. Steps 4, 5, and 6 each begin by checking whether their engine files are installed yet — until the full install is complete, a step that finds its files missing tells you which prompt to paste next and halts. Once everything is installed, those checks pass silently and the skill runs end to end.

### Step 1 — Today's date

Read today's date into a variable so every later step (folder name, brief date, recency filters) uses the same date.

TODAY=$(date +%Y-%m-%d)

This is a one-line shell read inside the skill. It is not a Claude Code hook. It does not touch the user's global config.

### Step 2 — Conversational intake

Ask one question at a time. Wait for the answer before asking the next.

1. "Who are you meeting? Just the person's name is fine."
2. "What company do they work for?"
3. "Anything I should know about this meeting? For example, is it a cold approach, an inbound enquiry, or a referral, and what are you hoping to get out of it? One line, or just say 'no' to skip."

Hold the three answers in memory as PERSON, COMPANY, MEETING_CONTEXT (the third may be empty).

### Step 3 — Confirm back

Stitch the answers into one short readback and ask the user to confirm before any research starts.

"So you're preparing for a first meeting with {PERSON} at {COMPANY} (and, if there is meeting context, mention it). I'll find the right person, gather sourced facts from six angles, and write you a brief. Ready to start, or anything to correct?"

Wait for confirmation. If the user corrects a value, update it and read back again before continuing.

### Step 4 — Research

Install check: if ~/.claude/skills/sales-brief/agents/right-person-check.md does not exist, the research team is not installed yet. Tell the user: "The research team isn't installed yet. Paste the next install prompt (Prompt 3) to add the six research agents, then run /sales-brief again." Then stop. Otherwise continue.

Run the right-person check first. Read agents/right-person-check.md and execute it with the intake values from Steps 2 and 3 (including the optional meeting context). It classifies the result set as CLEAR / AMBIGUOUS / WEAK / NOT FOUND and returns its verdict plus the two confirmed identity rows.

- CLEAR: continue silently to the team announcement.
- AMBIGUOUS / WEAK / NOT FOUND: stop, show the candidates with the agent's reasoning, wait for the user to pick or skip. If the user skips, note the gap and continue with the company-side research only.

Once identity is locked, create the meeting folder and its cache/ subfolder at ~/meetings/{TODAY}-{company-slug}/cache/ (where company-slug is the company name lowercased and hyphenated; this folder is referred to below as {slug}). Create ~/meetings/{TODAY}-{company-slug}/running-notes.md from templates/running-notes.md, substitute the meeting metadata, and write the right-person check's verdict and its two identity rows into it.

The skill is the only thing that writes running-notes.md. The agents never write it themselves — six agents writing one file in parallel would race and silently lose rows. The agents return their rows to you; you write the file.

Announce the team:

"I'm looking into {PERSON} and {COMPANY} now, from six angles at once: who they are, the company itself, the people around them, what's changed for them recently, their market, and the challenges they're facing. Back in about a minute."

Then fan out all six agents in a single message, multiple tool calls, instructing each to retry once after a few seconds if a search comes back rate-limited (HTTP 429) before recording a gap — even with a free Exa key, six agents searching at once can occasionally be throttled. Each reads its own prompt file from agents/, runs its searches, caches the page text of every URL it fetches into ~/meetings/{TODAY}-{company-slug}/cache/{url-slug}.txt. {url-slug} is the URL lowercased, with http(s):// removed, every run of non-alphanumeric characters replaced by a single hyphen, trimmed to 80 characters. Each cache file has a distinct name, so parallel caching is safe. Each agent returns its facts to you as a markdown table block in its final message; it does not write running-notes.md.

LinkedIn (nothing to install): the Person agent gets the publicly-visible profile material from Exa search. Public profiles usually carry plenty on their own.

When all six agents have returned, write running-notes.md in one pass:

- Append every returned row — keep them all, including repeats from different agents or syndicated reprints of the same item. Running-notes is the complete audit trail; de-duplication happens later, at the synthesiser, where source agreement is actually weighed (it is not collapsed here).
- **Sanitise each fact before writing it into the table:** replace any literal `|` in the fact text with `/`, and collapse any newlines to spaces. A raw pipe inside a markdown table cell splits the row, so this is not optional.
- Write each agent's returned gap: or contradiction: lines into the Open gaps section.
- Set the frontmatter status: done and agents_done to the full list, then continue to Step 5.

Resume: if a previous run was interrupted and running-notes.md already holds rows for some agents, re-run only the agents not yet represented.

### Step 5 — Brief writing

Install check: if ~/.claude/skills/sales-brief/synthesiser.md does not exist, the brief writer is not installed yet. Tell the user: "Research complete. See running-notes.md in the meeting folder for everything I found, with sources. The brief writer isn't installed yet. Paste the next install prompt (Prompt 4) to install it." Then stop. Otherwise continue.

After Step 4 (Research) completes and running-notes.md exists, invoke the synthesiser. Read ~/.claude/skills/sales-brief/synthesiser.md and execute its sequence:

1. Read running-notes.md (all rows).
2. Read ~/.claude/about-me.md + about-my-business.md + about-my-icp.md (tolerate missing files).
3. Map facts to sections by who_about.
4. Write sections 1-4 as readable prose built from the sourced fact rows, each specific fact or number carrying its [n] (restate facts in plain words, never add to or change them; the exact source words stay in Sources); close section 4 with the "Why now:" read line. Apply source independence before weighing any "why now" signal — collapse syndicated/duplicate sources to one (ten reprints of one announcement are one signal), keep the most authoritative as the surviving [n], flag genuine conflicts.
5. Write section 5 Your angle — open with the "skill's read" note, then the going-in hypothesis (inference to test), ICP match, adjacency, risk flags. Each line cites [n]. No per-line tag; the section frame signals it's interpretation.
6. Write section 6 Questions, section 7 Objections (preparation, not a script), section 8 Opener (insight-led angles) and the single next step to propose.
7. Write the TL;DR last from already-confirmed body facts.
8. Write the Sources section listing every [n].
9. Apply templates/brief-html.html to render the HTML.
10. Write brief.md and brief.html into ~/meetings/{slug}/.
11. Multi-attendee meetings: one per-attendee subfolder, one brief each.

Then tell the user, plainly, that the brief is sourced but not automatically fact-checked: "Every fact in your brief has a link to where it came from, so you can click and check anything that matters before the meeting. I have not checked them for you, so treat the links as your way to confirm the things that count."

## Output paths

Each run of /sales-brief creates one folder under ~/meetings/ containing: running-notes.md (the sourced facts, each with a link) plus brief.md and brief.html (the brief). The meeting folder is created on the first real run, not at install. For meetings with multiple attendees, the skill writes one folder per attendee under the same date-slug parent.

## Tool routing

The research agents use Exa and Firecrawl if they're connected. If neither is connected yet, the agents fall back to the built-in WebSearch and WebFetch tools — the brief is still produced, with slightly less reliable sourcing. The agents never invite an API key into the chat.

## Files this skill writes

The skill writes nothing on disk beyond its intake until a real run. The research engine and the brief writer write files into the meeting folder under ~/meetings/. The skill's own installed files (agents/, synthesiser.md, templates/) are written once by the install prompts and not modified at runtime.
=== END SKILL.md ===

4. Create the folder ~/meetings/ (this is where each brief will be saved later) and an empty file ~/meetings/.gitkeep inside it so the folder exists.

5. Check your work quietly, then tell me plainly. Read SKILL.md back and check the ~/meetings/ folder: make sure the file is there and complete (it should open and close its top section cleanly) and the folder exists. Do not read the technical details out to me. Just tell me, in plain words, "Your agent's instructions are saved, and the folder for your briefs is ready." If anything is missing or looks wrong, tell me plainly and stop rather than carrying on.

6. Tell me: "The agent is installed — its command and instructions are in place, and the ~/meetings/ folder where your briefs will be saved is ready too. That's 2 of the 4 prompts done. There's nothing to switch on yet; we do that with one restart at the very end. Next, paste Prompt 3 and I'll add its research team." Then stop. Do not create anything else.

You are guiding me through adding the brief writer to a Claude Code skill called /sales-brief. Keep it simple, warm and clear. In a sentence, tell me the point of each step so I know what I'm getting. The goal is to get this in place smoothly, not to teach me how it all works. Use plain, everyday words and skip technical jargon where you can. When something technical does show up that I'll see on screen (a box asking me to approve an action, or a word like "bash"), tell me plainly what it is and that it's a normal part of how Claude Code works, then help me through it. Let me know how I'm getting on as we go. Write in plain sentences, with no dashes. Never read out file names, line counts, or words like frontmatter or runtime; keep everything in plain language.
IMPORTANT: later in this prompt you'll connect two tools that each need a free key. Never ask me to paste a key into this chat. When a key is needed, walk me through copying it straight into a command in a separate terminal on my own machine; the key never appears in our conversation.
This is the last prompt. It writes the brief writer, then connects your two research tools and switches everything on. I'll ask you a couple of quick things along the way.

Follow these steps in order. Do not skip ahead.

1. Greet me, then tell me: "Hi again. This is the last one. First I'll add the part that writes your brief, so your agent can turn everything it found into a clean, faithful brief: a plain version and a tidy web page you can open, print, or send on. Then we'll connect two tools that give it sharper sources, do one quick restart, and make your very first brief. About five minutes in all. Ready?" Wait for my acknowledgement.

2. Check the skill folder and research team exist. Run `ls ~/.claude/skills/sales-brief/SKILL.md 2>/dev/null` and `ls ~/.claude/skills/sales-brief/agents/ 2>/dev/null`. If either returns nothing, stop and tell me which prompt I need to paste first (Prompt 2 if SKILL.md is missing, Prompt 3 if the agents folder is missing). Otherwise continue.

3. Create the templates folder if it does not already exist: `mkdir -p ~/.claude/skills/sales-brief/templates/`.

4. Create the synthesiser file. Write the literal content between the sentinel markers byte-for-byte.

=== BEGIN ~/.claude/skills/sales-brief/synthesiser.md ===
---
name: synthesiser
purpose: 'Turn the running-notes facts into a faithful, readable sales brief. Write the sourced sections as plain, flowing prose built from the facts, with each specific fact or number carrying a numbered [n] link to its source; the exact source words live in the Sources list, not the body. Restate facts in plain words, but never add to or change what they say. Interpretation is grouped into clearly-framed read sections, each line citing the facts it leans on. Produce Your angle from the user setup files, opening with a going-in hypothesis and closing with a single next step.'
---

# Synthesiser

## Goal

Build a meeting-prep brief from `running-notes.md` that the rep can trust and actually wants to read. Write it the way a sharp colleague would brief you: plain, flowing prose, not a list of raw quotes. Every specific fact or number carries a numbered `[n]` link back to where it came from, so the rep can check anything that matters; the exact source words live in the Sources list at the end, not in the body. Restate facts in plain words, but never add to them or change what they say. Interpretation is grouped into clearly-framed "the skill's read" sections, each line citing the facts it leans on. The TL;DR is written last. Your angle reads the prospect's world through what the rep sells.

## Inputs

- `running-notes.md` — the source of every hard fact (read all rows).
- `~/.claude/about-me.md`, `about-my-business.md`, `about-my-icp.md` — the lens for Your angle (tolerate missing files; Your angle is thinner without them).

## What the synthesiser does NOT do

- Re-fetch, search, or call an LLM to "improve" or add to a fact.
- Add to or change what a fact says. Restating a fact in plain words is wanted; sharpening a number, hardening a hedge, or stretching a claim beyond what the source supports is not. When in doubt, stay close to the source and let the exact words in Sources carry the proof.
- Invent. Every body line is either a sourced fact carrying its `[n]`, or an interpretation that cites the facts it rests on.
- Pre-cook the pitch. No drafted opening lines, no strategic exec summaries, no multi-phase next-steps roadmaps. One next step to propose is fine; a phased plan is not.

## How facts and interpretation are shown

- **Sourced sections (sections 1-4):** readable prose built from the facts, with `[n]` after each specific fact or number it rests on. The citation is the signal it's sourced; the exact words live in Sources. Use a verbatim quote in the body only when the exact wording matters — something the person actually said, or a phrase that loses meaning if reworded.
- **Derived sections (section 5 Your angle, section 6 Questions, section 7 Objections, section 8 Opener and next step):** the skill's read of those facts. section 5 opens with the one-line note *"The skill's read of the facts above, not new facts."* Each line cites the `[n]`(s) it leans on. No per-line tag — the section frame carries the signal. Every citation is a numeric `[n]` that resolves to a Sources entry; the three setup files are the implicit lens for these sections and are never themselves written as a citation (no `[about-my-business]`-style tags).
- The going-in hypothesis (top of section 5) carries an explicit `(inference to test)`, because it's the boldest call.

## Source independence (before weighing agreement)

This applies wherever you treat a fact as well-supported — the section 4 *why now* read and the section 5 going-in hypothesis. Before agreement counts as confidence, in this order:

1. **De-duplicate first.** Collapse syndicated and duplicate sources to one: ten reprints of one press release are one source, not ten confirmations, and the same fact returned by two agents is one fact. Agreement between copies of the same item is not confirmation.
2. **Then weigh reliability.** Keep the most authoritative or original source as the surviving `[n]` — the company's own announcement or a primary outlet over an aggregator or reprint.
3. **Then resolve conflicts.** If genuinely independent sources disagree, prefer the more reliable and more recent, and note it; if it can't be resolved, flag it in the brief as `[sources disagree: ...]` rather than picking silently. Treat any `contradiction:` line in running-notes Open gaps as a signal to do this.

Running-notes keeps every row (the full audit trail); this collapsing happens only in how you read and weigh them, never by editing the file.

## Sequence

### 1. Read running notes

Open `running-notes.md`. Read the progress line, the right-person verdict, the fact rows, the Open gaps. Use all rows.

### 2. Read the setup files

Read the three `~/.claude/about-*.md` files. They drive Your angle. If they're missing, Your angle is thinner and the body still ships.

### 3. Group facts

Map each row to a body section by `who_about`:

| who_about | Section |
|---|---|
| person | section 1 Who you're meeting (rapport rows also ground the section 8 opener) |
| company | section 2 Their company |
| key_people | section 3 Key people (the decision path) |
| whats_changed, their_sector | section 4 What's recent and material (and why now) |
| challenges | section 6 Questions (grounds the questions); any cost-of-inaction row also feeds the section 5 going-in hypothesis |

Order facts within a section by source date (newest first for time-bound, chronological for biographical).

### 4. Write sections 1-4

Write each section as short, flowing prose — a tight paragraph or two, or a few full-sentence points — the way a colleague would brief you out loud. Build it from the facts, and put each `[n]` right after the specific fact or number it supports (the TL;DR already reads this way — write the whole brief like that). Assign citation numbers fresh: start at `[1]` and number in order of first appearance in the body, never carrying over the row order or any numbering from running-notes. Once the final set of facts is chosen, the numbers must run contiguously `[1]…[N]` with no gaps — a dropped source is not a skipped number, so renumber the survivors to keep the sequence unbroken. State facts in plain words; keep a verbatim quote only where the exact words matter. Keep approximations as approximations ("around 200 employees"). Lead with who or what the section is about, and stay scannable — no padding.

Close section 4 with a labelled read line: **Why now:** the one or two recent signals that make this the moment `[n]`, and what they imply. This is the only interpretation in sections 1-4. Apply Source independence first — a signal carried by ten reprints of one announcement is one signal, not ten.

### 5. Write section 5 Your angle

Open with the note: *"The skill's read of the facts above — interpretation, not new facts."* Then four parts, each line citing the `[n]`(s) it rests on:

**Going-in hypothesis** *(inference to test):*
- likely problem — the prospect's most likely problem, given sections 1-4 `[n]`
- likely cost — what it plausibly costs them, drawing on any cost-of-inaction fact `[n]`
- what good looks like — the outcome a fix would deliver

Phrase every line as a bet ("likely…", "probably…"), never as an assertion.

**ICP match:** 1-2 lines on where they fit the user's ICP `[n]`, 1-2 on where they don't `[n]`.

**Where your offer touches their world:** 2-4 bullets, each naming a specific signal from sections 1-4 and the touch-point with the user's offer `[n]`.

**What might make this hard:** 0-2 bullets, only if `about-my-icp.md`'s "not a fit" overlaps something in sections 1-4. Often empty.

If a line can't cite a fact, don't write it.

### 6. Write section 6 Questions to ask

5-10 grounded discovery questions, each tracing to a fact:

> "Given they've publicly committed to expanding into EU markets `[7]`, how is that programme going so far?"

Specific probes, not generic discovery.

### 7. Write section 7 Objections to anticipate

3-5 objections the prospect may raise, grounded in their situation (role, public stance, recent moves, sector pressures), each with a one-line note on why it's likely `[n]`. These are preparation for the rep, not a script to raise — don't introduce an objection the prospect didn't have. The rep drafts their own response.

### 8. Write section 8 Opener and next step

2-3 opening angles that lead with insight (the rep's read on the prospect's world), not a question, grounded in section 1 rapport rows or a section 4 fact `[n]`. Entry points, not drafted lines — the rep picks one and writes their own.

Close with one line: a single logical next step the rep could propose at the end of the meeting, tied to the angle.

### 9. Write the TL;DR last

3-4 lines: 1-2 headline facts with `[n]`, plus one line summarising the going-in hypothesis. No fact that doesn't appear elsewhere in the body with `[n]`.

### 10. Sources

List every `[n]` in numerical order, contiguous from `[1]` with no gaps: URL, the exact words the fact came from, source date.

### 11. Render HTML

Apply `templates/brief-html.html`, substitute the body into the content slot. Self-contained — opens offline in any browser.

### 12. Write output files

Assemble `brief.md` using `templates/brief-md.md` as the section skeleton (its 8 section headings plus Sources and the TL;DR slot), filling each section with the content built in steps 4-10. Then write:

- `~/meetings/{slug}/brief.md`
- `~/meetings/{slug}/brief.html`

Multi-attendee meetings: one per-attendee subfolder, one brief each.

## Output verification

- Every `[n]` in the body has a Sources entry, and every Sources entry is used at least once
- Citation numbers are contiguous from `[1]` to `[N]` with no gaps — renumber the survivors after any source is dropped, never leave a hole like 29 → 33
- No non-numeric citations: every bracketed citation is a numeric `[n]`; the setup files are the lens, never a citation tag
- TL;DR facts all appear with `[n]` elsewhere
- The going-in hypothesis reads as inference ("likely…"), not assertion
- Every line in sections 5-8, plus the section 4 why-now line, cites at least one `[n]`
- Every specific fact, name, number or date in sections 1-4 carries an `[n]`; light connective wording between facts is fine, but no *claim* sits unsourced (the single why-now line is the one piece of interpretation)
- No "well-supported" or corroboration claim rests on reprints of one item — syndicated/duplicate sources were collapsed to one `[n]` before agreement was weighed; genuine conflicts are flagged, not silently resolved

## Rules

Write from `running-notes.md` and the three setup files only. Never re-fetch, never call an LLM to improve a fact. The HTML render is self-contained.
=== END ~/.claude/skills/sales-brief/synthesiser.md ===

5. Create the markdown brief template:

=== BEGIN ~/.claude/skills/sales-brief/templates/brief-md.md ===
---
type: sales-brief
meeting: '{{PERSON}} at {{COMPANY}}'
date: '{{YYYY-MM-DD}}'
---

# Sales brief — {{PERSON}} at {{COMPANY}}

**Meeting date:** {{MEETING_DATE}}  ·  **Generated:** {{RUN_DATE}}  ·  **Sources:** every fact below carries a link you can click to check it

## TL;DR

{{1-2 headline facts with [n], plus one line summarising the going-in hypothesis. 3-4 lines.}}

## 1. Who you're meeting

{{Readable prose built from the person facts, each fact carrying its [n]. Include rapport material and any landmines (flagged).}}

## 2. Their company

{{Readable prose built from the company facts, each fact carrying its [n]. Tech-stack/vendor inferences flagged "inferred".}}

## 3. Key people (the decision path)

{{Decision path first (manager / economic buyer / champion / technical evaluator/blocker, labelled, inference marked), then CEO + founders. Name + role + one-line context, each with [n]. Names flagged for the rep's warm-intro check.}}

## 4. What's recent and material (and why now)

{{Readable prose built from the what's-changed + their-sector facts, each fact carrying its [n] and source date.}}

**Why now:** {{the one or two signals that make this the moment}} [n] — {{what they imply}}

## 5. Your angle into this meeting

*The skill's read of the facts above — interpretation, not new facts.*

**Going-in hypothesis** *(inference to test)*

- likely problem — {{...}} [n]
- likely cost — {{...}} [n]
- what good looks like — {{...}}

**ICP match**

- {{where they fit / where they don't}} [n]

**Where your offer touches their world**

- {{specific signal → touch-point with your offer}} [n]

**What might make this hard** *(often empty)*

- {{risk flag, OR omit the subsection}} [n]

## 6. Questions to ask

1. {{Question grounded in a sections 1-4 fact}} [n]
2. ...

## 7. Objections to anticipate

*(These may come up — preparation, not a script to raise.)*

- {{Objection}} — {{why likely}} [n]
- ...

## 8. Opener and next step

**Opening angles** *(lead with insight, not a question — you write the line)*

- {{Angle grounded in section 1 rapport or a section 4 fact}} [n]
- ...

**Next step to propose**

- {{a single logical next step, tied to the angle}}

## Sources

[1] {{URL}} — {{verbatim source words the fact came from}} *(source date: {{YYYY-MM-DD}})*
[2] ...

---

*Generated by /sales-brief. Full audit trail in `running-notes.md`.*
=== END ~/.claude/skills/sales-brief/templates/brief-md.md ===

6. Create the HTML brief template (self-contained, no remote dependencies):

=== BEGIN ~/.claude/skills/sales-brief/templates/brief-html.html ===
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="UTF-8">
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<title>Sales brief — {{PERSON}} at {{COMPANY}}</title>
<style>
  body { font-family: -apple-system, BlinkMacSystemFont, "Segoe UI", Helvetica, Arial, sans-serif; max-width: 760px; margin: 2rem auto; padding: 0 1.5rem; color: #1a1a1a; line-height: 1.55; }
  h1 { font-size: 1.6rem; margin-bottom: 0.4rem; }
  h2 { font-size: 1.2rem; margin-top: 2rem; padding-bottom: 0.3rem; border-bottom: 1px solid #e5e5e5; }
  h3 { font-size: 1rem; margin-top: 1.2rem; }
  .meta { color: #666; font-size: 0.9rem; margin-bottom: 1.5rem; }
  .tldr { background: #f7f7f5; border-left: 4px solid #1a1a1a; padding: 1rem 1.2rem; margin: 1.5rem 0; border-radius: 4px; }
  .tldr h2 { margin-top: 0; border: none; font-size: 1rem; text-transform: uppercase; letter-spacing: 0.05em; color: #666; }
  .derived-note { color: #666; font-style: italic; font-size: 0.92rem; margin: 0.3rem 0 0.8rem; }
  ul { padding-left: 1.4rem; }
  li { margin-bottom: 0.4rem; }
  sup a { text-decoration: none; color: #0a66c2; font-size: 0.8rem; padding: 0 0.1rem; }
  details { margin-top: 2.5rem; }
  details summary { cursor: pointer; font-size: 0.95rem; color: #666; padding: 0.5rem 0; }
  .sources { font-size: 0.85rem; color: #444; }
  .sources li { margin-bottom: 0.6rem; }
  .sources .quote { color: #555; }
  .sources .date { color: #888; }
  .team-note { font-size: 0.85rem; color: #777; margin-top: 1.5rem; padding-top: 0.8rem; border-top: 1px solid #eee; }
</style>
</head>
<body>

<h1>Sales brief — {{PERSON}} at {{COMPANY}}</h1>
<div class="meta">Meeting on {{MEETING_DATE}} · Brief generated {{RUN_DATE}} · Every fact carries a link to its source</div>

<div class="tldr">
<h2>TL;DR</h2>
{{TLDR_HTML}}
</div>

{{BODY_HTML}}

<details>
<summary>Sources ({{N_SOURCES}})</summary>
<ol class="sources">
{{SOURCES_HTML}}
</ol>
</details>

<div class="team-note">
Researched by the /sales-brief skill: Person, Company, Key people, What's changed, Their sector, Challenges. Audit trail in <code>running-notes.md</code>.
</div>

</body>
</html>
=== END ~/.claude/skills/sales-brief/templates/brief-html.html ===

7. Quietly check your work by reading the files back. Do not read the technical details out to me (no file names, no line counts). Just confirm everything is in place, then tell me in plain words: "All set. Your agent can now take everything it found and write it up as a brief. You will get a plain version and a web-page version you can open in your browser, print, or send on." If anything is missing, say so plainly rather than carrying on.

8. Tell me: "That's your brief writer in. Your agent can now turn what it found into a clean, faithful brief: a plain version and a tidy web page you can open in your browser, print, or send to someone. One last thing and you're ready: connecting two tools that give it sharper sources, then a quick restart. About five minutes." Then continue to step 9.

9. Find out how I'm running Claude Code, and explain the terminal step. Ask me: "Quick question: are you using Claude Code inside a code editor like VS Code, or in a plain terminal window? If it's a panel inside an editor, that's VS Code. If it's filling a plain window on its own, that's the terminal." Wait for my answer.

   Then explain warmly: "A couple of the next steps need you to run a one-line command. Claude Code is using this window for our chat, so you'll run that command in a SEPARATE terminal, then come back and tell me you're done. Nothing here is lost while you do that."

   Then tell me how to open that separate terminal:
   - If I said VS Code: "Press Ctrl and the backtick key ` (top-left, just under Escape), or on a Mac press Cmd and backtick. Or use the menu: Terminal then New Terminal. A small panel opens at the bottom. That is where the commands go."
   - If I said terminal: "Open a SECOND terminal so this one keeps running Claude Code. On a Mac press Cmd+T for a new tab. On Windows, open another PowerShell window. Run the commands there, then switch back here."

   Tell me to keep that terminal open, we will use it twice. Then continue to step 10.

10. Connect Exa, the tool that finds the right people and news. Tell me: "Sign up for a free account at https://exa.ai. Open the page and click the sign-up button to create your account (it may say 'Sign up', 'Get API key', or 'Dashboard'). When you sign up, Exa shows a quick 'Create your setup prompt' screen. Complete it, since finishing it usually unlocks some free credits: choose 'Claude', then 'MCP', then 'I don't know yet', and click 'Generate'. You'll land on a 'You're all set!' screen. Just below the big button, under 'Your API Key', click the eye icon to reveal your key, then the copy icon to copy it. (If it isn't there, it's always at https://dashboard.exa.ai/api-keys.) Keep your key to yourself, you won't paste it here."

   Then create a text file on my Desktop so the command is easy to copy cleanly. Create `~/Desktop/connect-exa.txt` containing exactly this single line and nothing else:

   ```
   claude mcp add -s user --transport http exa "https://mcp.exa.ai/mcp?tools=web_search_exa,web_search_advanced_exa,web_fetch_exa&exaApiKey=YOUR_EXA_KEY"
   ```

   Then tell me: "I've put a file called connect-exa.txt on your Desktop, so the command is easy to copy without anything getting jumbled. Open it (double-clicking opens it in a plain text editor). You'll see YOUR_EXA_KEY near the end of the line. Type or paste your key straight over those words, leave everything else exactly as it is, and save. Then select the whole line, copy it, paste it into the separate terminal you opened, and press enter. That connects Exa. Tell me 'done' when you've done that, just the word done, not your key."

   Wait for me to confirm. Then run `claude mcp list` yourself, look for exa, and tell me plainly whether it connected. If it didn't, ask me whether the command showed a message and what it said.

11. Connect Firecrawl, the tool that reads web pages cleanly. Tell me: "Sign up free at https://www.firecrawl.dev/. The moment you sign up you land on your dashboard, and your key is on the right under 'API Key'. Click the eye icon to reveal it, then the copy icon to copy it. You want the key that starts with 'fc-'. Keep it to yourself, you won't paste it here."

   Then create a second file on my Desktop. Create `~/Desktop/connect-firecrawl.txt` containing exactly this single line and nothing else:

   ```
   claude mcp add -s user --transport http firecrawl "https://mcp.firecrawl.dev/YOUR_KEY_HERE/v2/mcp"
   ```

   Then tell me: "I've put a second file on your Desktop, connect-firecrawl.txt. Open it, and you'll see YOUR_KEY_HERE in the middle of the line. Type or paste your Firecrawl key straight over those words, leave everything else as it is, and save. Then copy the whole line, paste it into the same terminal, and press enter. Tell me 'done' when you've run it."

   Wait. Then run `claude mcp list` yourself, look for firecrawl, and tell me plainly whether it connected.

12. Check both are connected. Run `claude mcp list` and show me what you find, I'm looking for both exa and firecrawl. If either is missing, tell me plainly which one, and we'll sort it before moving on.

13. The one restart. Tell me: "Both tools are connected, and that's everything built. One last thing and you're ready: close Claude Code and open it again, so it picks up your two new tools and your new /sales-brief agent together." Then give me the step for my setup:
   - If VS Code: "Open the Command Palette (Cmd+Shift+P on a Mac, Ctrl+Shift+P on Windows), type 'Reload Window', and press Enter. Or just close and reopen VS Code."
   - If terminal: "Close Claude Code (type /exit), then start it again by typing `claude`."

14. Tell me: "You're all set up. To make your first brief: type /sales-brief, then give it the name of someone you're about to meet and their company. It'll research them and write you a short, sourced brief in a couple of minutes. From now on that's all it takes: /sales-brief, a name, and a company. Enjoy." Then stop. Do not create anything else.