agentleFS
Sign inStart free
GTMifyGTMify/aigtm/skills/meeting-prep/SKILL.md

meeting-prep

Skill25 starsChanged 5 months agoMITView on GitHub

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.

We split this skill into the rules it gives an agent

7 rules. 0 are common, 7 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 48 edited versions we read keep these.

  • 7

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Follow these steps in order.

    line 14
  2. Distinctive:

    Search the web for the company.

    line 17
  3. Distinctive:

    Search for the person by name + company.

    line 25
  4. Distinctive:

    Write 3 opening questions that:

    line 42
  5. Distinctive:

    Never fabricate information: If you can't find something, say "Not found" — don't guess.

    line 90
  6. Distinctive:

    Date your sources: If a news article is from 2 years ago, say so.

    line 93
  7. Distinctive:

    Respect privacy: Don't include personal information (home address, family details, political views) even if findable.

    line 94

“Common” is measured: kept by at least 6 in 10 of the 48 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free