meeting-brief-generator

Name: meeting-brief-generator
Author: Varnan-Tech

25installs59forks

How to install meeting-brief-generator?

varnan-tech/opendirectory/meeting-brief-generator

$npx -y skills add Varnan-Tech/opendirectory --skill meeting-brief-generator

Installs into the current project.

Summary

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-cal

Files · 1

View on GitHub

SKILL.md

1	# Meeting Brief Generator
2
3	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.
4
5	---
6
7	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.
8
9	---
10
11	## Step 1: Setup Check
12
13	Confirm required env vars:
14
15	```bash
16	echo "TAVILY_API_KEY: ${TAVILY_API_KEY:+set}"
17	echo "GEMINI_API_KEY: ${GEMINI_API_KEY:+set}"
18	echo "NOTION_TOKEN: ${NOTION_TOKEN:-not set}"
19	echo "NOTION_DATABASE_ID: ${NOTION_DATABASE_ID:-not set}"
20	```
21
22	If TAVILY_API_KEY is missing:
23	Stop. Tell the user: "TAVILY_API_KEY is required. Get it at app.tavily.com. Add it to your .env file."
24
25	If GEMINI_API_KEY is missing:
26	Stop. Tell the user: "GEMINI_API_KEY is required. Get it at aistudio.google.com. Add it to your .env file."
27
28	If NOTION_TOKEN or NOTION_DATABASE_ID is missing:
29	Continue. The brief will be output as text only. Notion saving is skipped.
30
31	Confirm input is present.
32	The user must provide at minimum a company name. If not provided, ask: "Which company are you meeting with?"
33
34	---
35
36	## Step 2: Gather Context
37
38	Collect the following. Ask only for what is missing.
39
40	Required:
41	- Company name (or domain/URL if provided)
42	- Meeting date
43
44	Optional (do not block if missing):
45	- Contact name and title
46	- Meeting type (discovery, demo, follow-up, QBR)
47	- Any specific topics or goals the user wants to cover
48
49	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).
50
51	---
52
53	## Step 3: Research with Tavily
54
55	Run these searches in sequence. Each targets one section of the brief. Save the top results from each (title, url, content snippet, score).
56
57	Keep results with score >= 0.5. If a search returns 0 qualifying results, mark that section as "Limited public information found."
58
59	Search 1: Company overview
60	```bash
61	curl -s -X POST "https://api.tavily.com/search" \
62	-H "Content-Type: application/json" \
63	-d '{
64	"api_key": "'"$TAVILY_API_KEY"'",
65	"query": "\"COMPANY\" overview founded employees headquarters",
66	"search_depth": "advanced",
67	"max_results": 5,
68	"include_answer": true
69	}'
70	```
71
72	Search 2: Recent news (last 30 days)
73	```bash
74	curl -s -X POST "https://api.tavily.com/search" \
75	-H "Content-Type: application/json" \
76	-d '{
77	"api_key": "'"$TAVILY_API_KEY"'",
78	"query": "\"COMPANY\" news announcement",
79	"search_depth": "advanced",
80	"max_results": 5,
81	"include_answer": true,
82	"topic": "news",
83	"time_range": "month"
84	}'
85	```
86
87	Search 3: Tech stack
88	```bash
89	curl -s -X POST "https://api.tavily.com/search" \
90	-H "Content-Type: application/json" \
91	-d '{
92	"api_key": "'"$TAVILY_API_KEY"'",
93	"query": "\"COMPANY\" technology stack engineering infrastructure tools",
94	"search_depth": "advanced",
95	"max_results": 5,
96	"include_answer": true
97	}'
98	```
99
100	Search 4: Product and pricing
101	```bash
102	curl -s -X POST "https://api.tavily.com/search" \
103	-H "Content-Type: application/json" \
104	-d '{
105	"api_key": "'"$TAVILY_API_KEY"'",
106	"query": "\"COMPANY\" product features pricing use case",
107	"search_depth": "advanced",
108	"max_results": 5,
109	"include_answer": true
110	}'
111	```
112
113	Search 5: Competitors
114	```bash
115	curl -s -X POST "https://api.tavily.com/search" \
116	-H "Content-Type: application/json" \
117	-d '{
118	"api_key": "'"$TAVILY_API_KEY"'",
119	"query": "\"COMPANY\" competitors alternatives vs",
120	"search_depth": "advanced",
121	"max_results": 5,
122	"include_answer": true
123	}'
124	```
125
126	Search 6: Funding and growth
127	```bash
128	curl -s -X POST "https://api.tavily.com/search" \
129	-H "Content-Type: application/json" \
130	-d '{
131	"api_key": "'"$TAVILY_API_KEY"'",
132	"query": "\"COMPANY\" funding raised valuation growth",
133	"search_depth": "advanced",
134	"max_results": 5,
135	"include_answer": true
136	}'
137	```
138
139	If contact name is provided, run two more searches:
140
141	Search 7: Contact profile
142	```bash
143	curl -s -X POST "https://api.tavily.com/search" \
144	-H "Content-Type: application/json" \
145	-d '{
146	"api_key": "'"$TAVILY_API_KEY"'",
147	"query": "\"CONTACT_NAME

People who liked this also viewed

6 picks

Type

meeting-brief-generator

25installs59forks

View on GitHub

How to install meeting-brief-generator?

varnan-tech/opendirectory/meeting-brief-generator

$npx -y skills add Varnan-Tech/opendirectory --skill meeting-brief-generator

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# Meeting Brief Generator
2
3	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.
4
5	---
6
7	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.
8
9	---
10
11	## Step 1: Setup Check
12
13	Confirm required env vars:
14
15	```bash
16	echo "TAVILY_API_KEY: ${TAVILY_API_KEY:+set}"
17	echo "GEMINI_API_KEY: ${GEMINI_API_KEY:+set}"
18	echo "NOTION_TOKEN: ${NOTION_TOKEN:-not set}"
19	echo "NOTION_DATABASE_ID: ${NOTION_DATABASE_ID:-not set}"
20	```
21
22	If TAVILY_API_KEY is missing:
23	Stop. Tell the user: "TAVILY_API_KEY is required. Get it at app.tavily.com. Add it to your .env file."
24
25	If GEMINI_API_KEY is missing:
26	Stop. Tell the user: "GEMINI_API_KEY is required. Get it at aistudio.google.com. Add it to your .env file."
27
28	If NOTION_TOKEN or NOTION_DATABASE_ID is missing:
29	Continue. The brief will be output as text only. Notion saving is skipped.
30
31	Confirm input is present.
32	The user must provide at minimum a company name. If not provided, ask: "Which company are you meeting with?"
33
34	---
35
36	## Step 2: Gather Context
37
38	Collect the following. Ask only for what is missing.
39
40	Required:
41	- Company name (or domain/URL if provided)
42	- Meeting date
43
44	Optional (do not block if missing):
45	- Contact name and title
46	- Meeting type (discovery, demo, follow-up, QBR)
47	- Any specific topics or goals the user wants to cover
48
49	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).
50
51	---
52
53	## Step 3: Research with Tavily
54
55	Run these searches in sequence. Each targets one section of the brief. Save the top results from each (title, url, content snippet, score).
56
57	Keep results with score >= 0.5. If a search returns 0 qualifying results, mark that section as "Limited public information found."
58
59	Search 1: Company overview
60	```bash
61	curl -s -X POST "https://api.tavily.com/search" \
62	-H "Content-Type: application/json" \
63	-d '{
64	"api_key": "'"$TAVILY_API_KEY"'",
65	"query": "\"COMPANY\" overview founded employees headquarters",
66	"search_depth": "advanced",
67	"max_results": 5,
68	"include_answer": true
69	}'
70	```
71
72	Search 2: Recent news (last 30 days)
73	```bash
74	curl -s -X POST "https://api.tavily.com/search" \
75	-H "Content-Type: application/json" \
76	-d '{
77	"api_key": "'"$TAVILY_API_KEY"'",
78	"query": "\"COMPANY\" news announcement",
79	"search_depth": "advanced",
80	"max_results": 5,
81	"include_answer": true,
82	"topic": "news",
83	"time_range": "month"
84	}'
85	```
86
87	Search 3: Tech stack
88	```bash
89	curl -s -X POST "https://api.tavily.com/search" \
90	-H "Content-Type: application/json" \
91	-d '{
92	"api_key": "'"$TAVILY_API_KEY"'",
93	"query": "\"COMPANY\" technology stack engineering infrastructure tools",
94	"search_depth": "advanced",
95	"max_results": 5,
96	"include_answer": true
97	}'
98	```
99
100	Search 4: Product and pricing
101	```bash
102	curl -s -X POST "https://api.tavily.com/search" \
103	-H "Content-Type: application/json" \
104	-d '{
105	"api_key": "'"$TAVILY_API_KEY"'",
106	"query": "\"COMPANY\" product features pricing use case",
107	"search_depth": "advanced",
108	"max_results": 5,
109	"include_answer": true
110	}'
111	```
112
113	Search 5: Competitors
114	```bash
115	curl -s -X POST "https://api.tavily.com/search" \
116	-H "Content-Type: application/json" \
117	-d '{
118	"api_key": "'"$TAVILY_API_KEY"'",
119	"query": "\"COMPANY\" competitors alternatives vs",
120	"search_depth": "advanced",
121	"max_results": 5,
122	"include_answer": true
123	}'
124	```
125
126	Search 6: Funding and growth
127	```bash
128	curl -s -X POST "https://api.tavily.com/search" \
129	-H "Content-Type: application/json" \
130	-d '{
131	"api_key": "'"$TAVILY_API_KEY"'",
132	"query": "\"COMPANY\" funding raised valuation growth",
133	"search_depth": "advanced",
134	"max_results": 5,
135	"include_answer": true
136	}'
137	```
138
139	If contact name is provided, run two more searches:
140
141	Search 7: Contact profile
142	```bash
143	curl -s -X POST "https://api.tavily.com/search" \
144	-H "Content-Type: application/json" \
145	-d '{
146	"api_key": "'"$TAVILY_API_KEY"'",
147	"query": "\"CONTACT_NAME

People who liked this also viewed

6 picks

Type