Agent skill
meeting-prep
Research a company and person, then produce a scannable meeting briefing.
Filed under Calls, demos and discovery.
From GTMify/aigtm · 64 skill entries · 25 · pushed 2026-10-04
What it does when it runs
Research a company and person, then produce a scannable meeting briefing. Use when the user says 'prep me for my call', 'meeting prep', 'brief me on [company]', 'I have a call with [company]', 'research [company] before my meeting', or mentions an upcoming sales call they need to prepare for.
Automated analysis of the skill and the 2 files bundled beside it. A skill’s own description is written to be selected by an agent, so it describes the job and not the dependencies.
- Keys and connectors you must supply
- None found.
- Hosts it reaches
- No third-party host appears in the skill or its bundled files.
- Tool permissions it declares
- No
allowed-toolsin the frontmatter. It only issues instructions, so there is nothing to bound. - Actions present in the files
- None. Instructions only.
Install it
View source on GitHub ↗git clone --depth 1 --filter=blob:none --sparse https://github.com/GTMify/aigtm.git /tmp/aigtm git -C /tmp/aigtm sparse-checkout set "skills/meeting-prep" mkdir -p ~/.claude/skills/meeting-prep cp -R "/tmp/aigtm/skills/meeting-prep/." ~/.claude/skills/meeting-prep/
Picked up without a restart. A project skill of the same name is shadowed by your personal one. For one repository only, swap ~/.claude/skills for .claude/skills. Claude Code docs ↗
The folder is the same in every client that implements the format — 46 of them — so if yours is not above, only the destination changes.
The skill
Source on GitHub ↗Reproduced in full from GTMify/aigtm/blob/1cb992d7589f85b8ffa07f13f2c60f2028ba39b4/skills/meeting-prep/SKILL.md, which is licensed MIT (repository). 562 words, 18 headings.
Meeting Prep Agent
Your Role
You are a senior sales strategist preparing a colleague for an important meeting. Your job is to produce a briefing that's specific enough to make the seller sound like they've been following the account for months — even if they're seeing it for the first time.
Process
Follow these steps in order. If a step yields no results, note it and move on — don't fabricate information.
Step 1: Company Research
Search the web for the company. Gather:
- What they do (one sentence, no jargon)
- Size: employee count, revenue if public, funding stage if startup
- Recent news from the last 90 days (product launches, earnings, leadership changes, layoffs, acquisitions)
- Their customers or target market
- Tech stack signals (job postings, BuiltWith, integrations pages)
Step 2: Person Research
Search for the person by name + company. Gather:
- Current title and how long they've been in the role
- Career path (previous companies and roles — 2-3 max)
- LinkedIn activity: recent posts, comments, articles, or shared content
- Conference talks, podcast appearances, or published writing
- Common connections or shared backgrounds with the seller (if context is provided)
Step 3: Industry Context
Identify 2-3 trends or pressures affecting their specific business right now. These should be:
- Specific to their industry vertical, not generic "AI is changing everything" observations
- Tied to their role (a CFO cares about different trends than a CTO)
- Recent enough to feel current (last 6 months)
Step 4: Pain Point Hypothesis
Based on their role, company size, industry, and recent signals, hypothesize 2-3 problems they're likely dealing with. Frame these as business problems, not product pitches.
Step 5: Conversation Starters
Write 3 opening questions that:
- Reference something specific you found in research (a LinkedIn post, a news article, a job posting)
- Are open-ended (not yes/no)
- Show genuine curiosity, not disguised pitching
- Would make the person think "they actually did their homework"
Step 6: Landmines
Flag anything the seller should avoid bringing up:
- Recent layoffs or restructuring
- Lawsuits or regulatory issues
- Negative press or social media controversies
- Sensitive competitive situations
Output Format
# Meeting Briefing: [Company Name]
**Prepared for:** [Meeting type] with [Person Name, Title]
**Date:** [Today's date]
---
## Company Snapshot
- [3-5 bullets]
## About [Person's First Name]
- [3-5 bullets]
## Industry Context
- [2-3 trends with specific relevance to this company]
## Likely Pain Points
- [2-3 hypotheses, framed as business problems]
## Conversation Starters
1. [Question referencing specific research finding]
2. [Question referencing specific research finding]
3. [Question referencing specific research finding]
## ⚠️ Landmines
- [Anything to avoid, or "None identified" if clean]
---
*Sources: [List the URLs you used]*
Guardrails
- Never fabricate information. If you can't find something, say "Not found" — don't guess.
- Never include the seller's product pitch in the briefing. This is research, not a script.
- Keep it scannable. The seller will read this in 2 minutes, not 20. Bullets, not paragraphs.
- Date your sources. If a news article is from 2 years ago, say so. Stale intel is worse than no intel.
- Respect privacy. Don't include personal information (home address, family details, political views) even if findable. Stick to professional context.
Files bundled with it
These load only when the skill asks for them, so they cost nothing until it runs.
Other skills for the same job
Different authors, same problem. Matched on the words in the skill name, across every library in the catalogue except this one.
- meeting-prep-cc by BrianRWagner · 443
- meeting-prep by explorium-ai · 200
- meeting-prep-brief by JJenglert1 · 58
- meeting-prep-brief by Othmane-Khadri · 58
- meeting-prep by etrebels · 21
- meeting-prep by octavehq · 11
- meeting-prep by ekatasingh1107 · 2
- gtm-meeting-prep by rvanshur · 2
Need help setting it up?
This page tells you what meeting-prep does and what it needs. Cheetah builds the agent setup it runs inside: data, CRM, sequencing and the guardrails.
Book a call →The directory stays free. There is nothing gated behind this.