Meeting Brief Generator
Takes a company name and optional contact, runs targeted research via Tavily...
Install
npx skills add Varnan-Tech/opendirectory --skill meeting-brief-generator -g -a claude-code -y- Repository
- Varnan-Tech/opendirectory688
- Category
- Writing
- Updated
- 18d ago
- License
- MIT
- Context cost
- Mediumabout 1,991 tokens
- Runs scripts
- No, instructions only
What it does
Takes a company name and optional contact, runs targeted research via Tavily, synthesizes a 1-page pre-call brief with Gemini, and optionally saves it to Notion. Use when asked to prepare for a meeting, research a prospect before a call, generate a company brief, create a pre-call summary, or write a meeting prep doc. Trigger when a user says "prepare me for a meeting with", "research this company before my call", "generate a meeting brief for", "I have a call with X tomorrow", or "create a prospect brief for".
Meeting Brief Generator
Take a company name and optional contact. Research the company via Tavily. Synthesize a 1-page pre-call brief with Gemini. Optionally save to Notion.
Critical rule: DO NOT INVENT SPECIFICS. Every fact, number, and claim in the brief must come from a Tavily search result. Mark any section with no search data as "Limited public information found." Never fabricate funding amounts, employee counts, or product details.
Step 1: Setup Check
Confirm required env vars:
echo "TAVILY_API_KEY: ${TAVILY_API_KEY:+set}"
echo "GEMINI_API_KEY: ${GEMINI_API_KEY:+set}"
echo "NOTION_TOKEN: ${NOTION_TOKEN:-not set}"
echo "NOTION_DATABASE_ID: ${NOTION_DATABASE_ID:-not set}"
If TAVILY_API_KEY is missing: Stop. Tell the user: "TAVILY_API_KEY is required. Get it at app.tavily.com. Add it to your .env file."
If GEMINI_API_KEY is missing: Stop. Tell the user: "GEMINI_API_KEY is required. Get it at aistudio.google.com. Add it to your .env file."
If NOTION_TOKEN or NOTION_DATABASE_ID is missing: Continue. The brief will be output as text only. Notion saving is skipped.
Confirm input is present. The user must provide at minimum a company name. If not provided, ask: "Which company are you meeting with?"
Step 2: Gather Context
Collect the following. Ask only for what is missing.
Required:
- Company name (or domain/URL if provided)
- Meeting date
Optional (do not block if missing):
- Contact name and title
- Meeting type (discovery, demo, follow-up, QBR)
- Any specific topics or goals the user wants to cover
If the user provides a company URL or domain, use it to make Tavily queries more precise (e.g. site:example.com or include the domain in search terms).
Step 3: Research with Tavily
Run these searches in sequence. Each targets one section of the brief. Save the top results from each (title, url, content snippet, score).
