From sales-plugin
Generate a meeting prep brief in minutes — company snapshot, contact intel, tailored discovery questions, pain points, and an opening insight. Uses web research + HubSpot context.
How this skill is triggered — by the user, by Claude, or both
Slash command
/sales-plugin:meeting-prep [contact name] at [company name][contact name] at [company name]The summary Claude sees in its skill listing — used to decide when to auto-load this skill
The user has invoked the meeting prep skill. The argument (if provided) is: $ARGUMENTS
The user has invoked the meeting prep skill. The argument (if provided) is: $ARGUMENTS
Guard check: If $ARGUMENTS is empty or the literal string $ARGUMENTS, ask the user: "Who are you meeting? Please share the contact name and company — e.g. 'Florian Korner at NOSTA'." — then wait for their response and use that throughout.
Extract:
The expected format is [contact name] at [company name]. If only one is provided:
If the user provides extra context (e.g. "replacing their current card provider", "CFO", "multi-country logistics"), save it as meeting context — this will inform the Discovery Questions and Pain Points sections.
Use WebSearch to research the company. Run 2–3 searches to build a complete picture:
"[company name]" — general overview"[company name] news [current year]" — recent developments"[company name] revenue employees" — size and scale (if not clear from search 1)From the results, use WebFetch on the most relevant pages (company website, Crunchbase, press articles) to extract:
Summarize findings concisely. Do not include raw search results in the output.
Search HubSpot for any existing records related to this company and contact.
Search for the Company:
search_crm_objects with objectType: "Organization" and query on the company namename, domain, vertical, sub_vertical, country_region, hubspot_owner_id, notes_last_updatedsearch_ownersSearch for a Deal:
search_crm_objects with objectType: "Object" and query on the company namedealname, name_of_deal_stage, pipeline, expected_monthly_transaction_volume, total_addressable_monthly_transaction_volume, closedate, hubspot_owner_idSearch for the Contact:
search_crm_objects with objectType: "Contact" and query on the contact namefirstname, lastname, email, jobtitle, phone, country_regionFetch recent communications (if a deal or contact was found):
Email, Note, and Call objectTypes filtered by association to the recordIf nothing is found in HubSpot: That's fine — proceed with web research only. Note in the output that no CRM record was found.
Save any useful CRM context — deal stage, recent conversation themes, known pain points from notes — as CRM intel for use in later steps.
Use WebSearch to research the contact:
"[contact name]" "[company name]" LinkedIn — LinkedIn profile"[contact name]" "[company name]" — any other mentions (articles, talks, interviews)From the results, use WebFetch on the most relevant pages to extract:
If the contact cannot be found online, note this and work with whatever is available from HubSpot (job title, email history).
Using all research from Steps 2–4, generate the brief in exactly this structure:
# Meeting Prep Brief: [Contact Name] at [Company Name]
---
## 1. Company Snapshot
**What they do:** [1–2 sentence summary of the business]
**Size:** [employee count, revenue/funding if known]
**HQ & Markets:** [headquarters location, countries/regions they operate in]
**Recent news:**
- [Bullet 1 — most relevant recent development]
- [Bullet 2 — second item if available]
---
## 2. Contact Intel
**Role:** [current job title at company]
**Background:** [2–3 sentences covering career path, previous roles, expertise areas]
**Tenure:** [how long in current role, if known]
**Notable:** [anything distinctive — public talks, articles, board seats, specializations]
---
## 3. Discovery Questions
Based on what we know about [company] and [contact's role]:
1. [Question targeting a strategic priority or challenge the company likely faces — informed by company research]
2. [Question about their current setup/process relevant to what Pliant offers — informed by contact's role]
3. [Question about decision-making or evaluation criteria — informed by deal stage or context]
---
## 4. Pain Points to Probe
Based on [mention the source: deal context / industry research / meeting context provided]:
- **[Pain point 1]:** [1 sentence — why this is likely a pain point and how to surface it]
- **[Pain point 2]:** [1 sentence]
- **[Pain point 3]:** [1 sentence]
---
## 5. Opening Insight
> "[One specific, impressive talking point that shows you did your homework — reference a recent company event, a metric, a market trend relevant to them, or something from the contact's background.]"
**Why this works:** [1 sentence explaining why this opener builds credibility]
---
## 6. CRM Context
| Field | Value | Source |
|---|---|---|
| Vertical | [vertical] | Company |
| Sub-Vertical | [sub_vertical] | Company |
| Country | [country_region] | Company |
| Deal | [dealname] — [deal stage] | Deal |
| Last Activity | [notes_last_updated] | Company |
| Owner | [resolved owner name from hubspot_owner_id] | Company |
Section 6 is conditional: Only include it if Step 3 found an active deal (not Closed lost or Churned). If no active deal exists, omit Section 6 entirely from the output — do not show an empty table or a placeholder.
Say: "Your meeting prep brief is ready. Want me to adjust any section, dig deeper on a specific topic, or draft an opening email to [contact name]?"
npx claudepluginhub bendikas12/sales_plugin --plugin sales-pluginGuides creation, editing, and verification of skills for AI coding agents using test-driven development with subagent scenarios. Use when authoring or debugging skills.