Meeting Prep

references/nimble-playbook.md

&

wait

Instructions

Step 0: Preflight

references/nimble-playbook.md

• CLI missing or API key unset →

  references/profile-and-onboarding.md

  , stop
• Profile exists → read

  ~/.nimble/memory/people/index.md

  to identify existing person profiles. Load relevant

  ~/.nimble/memory/people/

  files for attendees before — skip redundant searches, surface prior meeting notes. Follow

  [[path/entity]]

  cross-references in person files: if an attendee's file links to

  [[competitors/widgetco]]

  , load that competitor file for richer context (e.g., recent intel from competitor-intel runs). Also check

  ~/.nimble/memory/companies/

  for cached company research. No same-day report check — meeting-prep is per-meeting, not per-day. Users may prep for multiple meetings in one day. Instead, check entity freshness: if a person/company profile was updated within the last 24 hours, offer to reuse it: "I have a recent profile for [Name] from earlier today. Use it, or refresh?"
• No profile → that's fine. Meeting prep doesn't require onboarding. Proceed to Step 1.

Step 1: Gather Meeting Context

$ARGUMENTS

list_events

gws

gws calendar +agenda --today

• Extract: attendee name(s), company, meeting date/time (if given)
• Confirm briefly: "Preparing briefing for your meeting with Alex Kim at WidgetCo..."

• Ask one clarifying question in plain text:

  "Who are you meeting with? (names, titles, and company if you have them)"

• Proceed with the person. Try to infer their company from search results.

What's the goal of this meeting?

• Sales / discovery — pitching, demo, exploring fit
• Partnership — integration, co-selling, joint venture
• Board / investor — board meeting, investor update, fundraising
• Interview — evaluating a candidate
• General / other — networking, catch-up, or not sure

Step 2: WSA Discovery

nimble agent list --search "{company-domain}" --limit 20

managed_by: "nimble"

nimble agent get --template-name {name}

nimble search

Step 3: Per-Attendee Research (sub-agents)

references/attendee-agent-prompt.md

references/nimble-playbook.md

~/.nimble/memory/people/[name-slug].md

nimble-researcher

agents/nimble-researcher.md

mode: "bypassPermissions"

extract-batch

references/nimble-playbook.md

• Attendee 1 research
• Attendee 2 research

• Attendee 3 research
• Attendee 4 research

Step 3.5: Gap Check

1. Run a

   --focus social

   fallback search directly (this searches social platform people indices and is the most reliable way to find someone):

   nimble search --query "[Name] [Company]" --focus social --max-results 5 --search-depth lite

2. If

   --focus social

   is unavailable, fall back to:

   nimble search --query "[Name]" --include-domain '["linkedin.com"]' --max-results 5 --search-depth lite

3. Try name variations: "[First] [Last]", "[Full Name] [Company] [Title if known]"

Step 4: Company Research

"\"Acme Supply\" news"

--include-domain '["[domain]"]'

• nimble search --query "\"[Company]\" news" --focus news --start-date "[14-days-ago]" --max-results 8 --search-depth lite

• nimble search --query "\"[Company]\" product launch OR announcement" --focus news --start-date "[14-days-ago]" --max-results 5 --search-depth lite

• nimble search --query "about" --include-domain '["[domain]"]' --max-results 3 --search-depth lite

• nimble search --query "\"[Company]\" funding OR raised OR investors" --max-results 5 --search-depth lite

• nimble search --query "[Company] [UserCompany] OR [user-domain]" --max-results 5 --search-depth lite

--start-date

references/nimble-playbook.md

~/.nimble/memory/companies/

Step 4.5: Value Positioning Research

business-profile.json

company.name

company.domain

~/.nimble/business-profile.json

• sales_context.key_differentiators

  — what makes the user's product unique

• sales_context.integration_partners

  — tools the user's product connects with

• sales_context.case_studies

  — similar customers and outcomes

• sales_context.common_objections

  — pre-built objection responses

• competitors

  — tracked competitors (check if the attendee's company uses any)

sales_context

1. nimble search --query "\"[AttendeeCompany]\" tech stack OR tools OR platform OR uses" --max-results 5 --search-depth lite

   → Discover what tools/platforms they use — match against

   integration_partners

2. nimble search --query "\"[AttendeeCompany]\" [UserCompany] OR [user-domain]" --max-results 5 --search-depth lite

   → Any existing relationship, mentions, or competitive overlap (skip if already run in Step 3)

3. nimble search --query "\"[AttendeeCompany]\" challenges OR pain points OR struggling OR migrating" --max-results 5 --search-depth lite

   → Pain signals to map against user's value props
4. (If

   competitors

   list exists)

   nimble search --query "\"[AttendeeCompany]\" [CompetitorName1] OR [CompetitorName2]" --max-results 5 --search-depth lite

   → Check if they use a competitor — critical for displacement positioning
5. (If

   case_studies

   exist with matching industry)

   nimble search --query "[UserCompany] [attendee-industry] case study OR customer story" --max-results 5 --search-depth lite

   → Find published case studies in the attendee's industry to reference

• Tools/platforms they use (for integration hooks)
• Pain signals or challenges (for value mapping)
• Competitor usage (for displacement angles)
• Industry match to existing case studies (for social proof)

Step 5: Deep Extraction

• Attendee's own LinkedIn posts, articles, or talks
• Recent company announcements directly relevant to the meeting
• Interviews or profiles of the attendee
• The company's about/team page (if attendee title wasn't found)
• (If value positioning active) Pages revealing their tech stack or tool usage
• (If value positioning active) Articles about their challenges or migration plans

nimble extract --url "https://..." --format markdown

references/nimble-playbook.md

Step 6: Synthesize Briefing

# Meeting Prep: [Company Name]
*[Meeting date/time if known] | Prepared [today's date]*

## Quick Take
[2-3 sentences: who you're meeting, why it matters, and the one thing to know
going in. This is the "read nothing else" paragraph.]

## Attendees

### [Name] — [Title]
**Background:** [Current role, time in position, career trajectory highlights]
**Recent Activity:** [What they've been posting, speaking about, or working on.
  Direct quotes from posts/talks when available.]
**Conversation hooks:** [2-3 specific things to reference — shared connections,
  their recent project, a post they wrote, a talk they gave]
**Notes from prior meetings:** [If exists in memory — what was discussed, their
  preferences, open items. "No prior meetings on file" if none.]

[Repeat for each attendee]

## Relationship Map
[Cross-attendee connections — shared employers, mutual connections, overlapping
  interests, organizational dynamics between attendees. Skip if single attendee.]

## Company Context
- **What they do:** [One line]
- **Size / Stage:** [Employees, funding stage, HQ]
- **Recent news:** [Top 2-3 items, dated with source]
- **Relevant to your meeting:** [How their company context connects to your
  discussion — e.g., recent product launch you might discuss, funding that
  signals growth, leadership change affecting priorities]

## Value Positioning
*[Only for sales/discovery, partnership, and board/investor meetings. Omit entirely
  for interview, internal, and general external meetings.]*

### Value Mapping
[Match their specific needs/pain points to your capabilities. Every mapping must
  be grounded in research from Step 4.5, not generic claims.
  Format: "They [specific finding with source] → Your product [specific capability]"]

### Integration Hooks
[Tools/platforms they use that your product integrates with. Only include
  integrations confirmed from research (their tech stack) AND your profile
  (integration_partners). If no overlap found, say so honestly.]

### Recommended Positioning
[2-3 sentences on how to frame your pitch for THIS specific company and person.
  Consider: their company stage, recent news, the attendee's role and priorities,
  and any competitive displacement opportunity. This is the "elevator pitch
  calibrated to this meeting" paragraph.]

### Reference Customers
[Similar companies from your case_studies that match their industry, size, or
  use case. Include the outcome/metric if available. If no matching case studies,
  omit this subsection rather than forcing a weak match.]

## Talking Points
[3-5 specific, actionable conversation starters grounded in the research.
  Not generic "ask about their priorities" — specific: "Ask about their
  migration from [old tool] to [new tool] that they announced last month."
  When value positioning is active, weave 1-2 positioning angles into the
  talking points naturally — don't make every talking point a sales pitch.]

## Watch Out For
[1-3 things to be aware of — sensitive topics (recent layoffs, bad press),
  potential awkward overlaps, information gaps you couldn't fill.]

## Sources
[Numbered list of key URLs cited in the briefing]

• Every factual claim about an external company or person must have a source URL. Data drawn from the user's own business profile (differentiators, integrations, case studies) should be attributed to the profile rather than requiring an external source.
• Lead with the Quick Take — most readers stop there.
• Talking points must be specific to THIS meeting, grounded in research findings. Never generate generic conversation starters.
• Say "no public information found" for a person rather than speculating about their role or background.
• If memory has prior meeting notes, surface open items and continuity points prominently — this is the highest-value content.
• Value Positioning claims must be grounded in research from Step 4.5. Never generate generic positioning advice like "highlight your product's strengths." Every value mapping must reference a specific finding about the attendee's company paired with a specific capability from the user's profile or research.
• If

  sales_context

  is missing from the profile, note it once at the end of the Value Positioning section: "Tip: Edit your profile at

  ~/.nimble/business-profile.json

  to add sales context (differentiators, integrations, case studies) for richer positioning next time."

Step 7: Save to Memory

• Report →

  ~/.nimble/memory/reports/meeting-prep-[company-slug]-[date].md

• Per attendee →

  ~/.nimble/memory/people/[name-slug].md

  (use the format in

  references/memory-and-distribution.md

  ). Add

  [[path/entity]]

  cross-references for the attendee's employer (e.g.,

  [[competitors/widgetco]]

  or

  [[companies/widgetco]]

  ) and any other discovered relationships.
• Company profile → update

  ~/.nimble/memory/companies/[company-slug].md

  if new company data was found. Add reverse cross-references to the people researched (e.g.,

  [[people/alex-kim]]

  ).
• Profile → update

  last_runs.meeting-prep

  in

  ~/.nimble/business-profile.json

  (only if profile exists)
• Follow the wiki update pattern from

  references/memory-and-distribution.md

  : update

  index.md

  rows for all affected entity files, append a

  log.md

  entry for this run.

people/

Step 8: Share & Distribute

references/memory-and-distribution.md

Step 9: Follow-ups

• Go deeper on an attendee → more focused person research
• Add attendees → research additional people joining the meeting
• "What about [topic]?" → targeted search on specific dimension
• "Looks good" → done
• Sibling skills:

  company-deep-dive

  for a full 360 on the company,

  competitor-intel

  to track them as a competitor,

  competitor-positioning

  to compare messaging before a sales meeting

Agent Teams Mode (Dual-Mode)

echo $CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS

1. Each teammate researches their assigned attendee independently
2. When a teammate discovers a workplace, school, or connection that overlaps with another attendee, they send a message to that teammate: "My attendee [Name] worked at [Company] from 2019-2022 — did yours overlap?"
3. The receiving teammate checks and responds
4. Lead (you) collects all cross-references and builds the Relationship Map section

What This Skill Is NOT

• Not competitor monitoring — use

  competitor-intel

  for tracking competitors
• Not a company deep dive — use

  company-deep-dive

  for research without attendees
• Not a CRM — gathers web intelligence, doesn't manage contacts or pipelines
• Not a calendar app — reads events for context but doesn't manage them

Error Handling

references/nimble-playbook.md

• Person not found: Try name variations (full, first+last, with company). If still nothing: "Couldn't find public info on [Name]. Can you share their title or LinkedIn?"
• Ambiguous name: Present top candidates with company/title context and ask.
• Empty company results: Note it and focus on attendee-level findings.