Help us improve
Share bugs, ideas, or general feedback.
From bd-intern
Generates structured pre-meeting briefing documents from company config, research files, Linear projects, meeting history, and fresh intelligence via researcher agent. Saves as Markdown file.
npx claudepluginhub mmashiat/bd-internHow this skill is triggered — by the user, by Claude, or both
Slash command
/bd-intern:meeting-prepThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Read `config/company.yaml` from the bd-intern plugin directory. Use:
Researches meeting attendees and their companies using real-time web data to surface roles, recent activity, company context, and talking points.
Generates strategic sales meeting battle plans as self-contained HTML with coaching frameworks, belief stacks, scripted talk tracks, discovery questions, stakeholder maps, landmine warnings, and timed phase-by-phase game plans for discovery, demos, executive calls, and QBRs.
Generates 1-page pre-call briefs for companies via Tavily research and Gemini synthesis, optionally saving to Notion. Use for meeting prep, prospect research, or call summaries.
Share bugs, ideas, or general feedback.
Read config/company.yaml from the bd-intern plugin directory. Use:
company.name, products[] — for positioningpipeline.engagement_offer — for desired outcomespaths.research, paths.meeting_notes — for intelligence gatheringIf config is missing, stop and tell the user to run /bd-intern setup.
Collect:
{paths.research}/{company}*.md{crm.team_name} — get stage, health, updates{paths.meeting_notes} for files mentioning company nameStructure:
3 bullets:
Key facts from research (condensed — 5-8 lines max)
Timeline table:
| Date | Event | Key Outcome |
What they care about right now (from news, job postings, announcements)
config.products fits best3 specific points with supporting detail. Not generic — tied to their situation.
3-5 strategic questions that:
Topics to avoid or handle carefully (past issues, competitive sensitivities, known objections)
Specific success definition for this meeting (e.g., "Agree to technical deep-dive next week" not "Good conversation")
List any outstanding items, flag overdue ones.
Save to {paths.research}/{Company} Meeting Prep {YYYY-MM-DD}.md