meeting-brief-generator
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".
npx skills add Varnan-Tech/opendirectory --skill meeting-brief-generator --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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: ```bash 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.
- Step 1: Setup Check
- Step 2: Gather Context
- Step 3: Research with Tavily
- Step 4: Synthesize with Gemini
- Step 5: Self-QA
- Step 6: Output or Save to Notion
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}"
curl -s -X POST "https://api.tavily.com/search" \
cat > /tmp/meeting-brief-request.json << 'ENDJSON'
curl -s -X POST \
cat > /tmp/notion-brief-payload.json << 'ENDJSON'
curl -s -X POST "https://api.notion.com/v1/pages" \What does the meeting-brief-generator skill do?
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".
How do I install it?
Run `npx skills add Varnan-Tech/opendirectory --skill meeting-brief-generator --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From Varnan-Tech/opendirectory, a repository with 571 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.