Menu

Individual skill

meeting-prep

0upvotes

Use this skill when a meeting is coming up and you need to know who is in the room before you walk in. Produces a meeting briefing: each attendee's role, background, and recent public activity with conversation hooks, a cross-attendee relationship map, company context, specific talking points, watch-outs, and — for sales, partnership, and investor meetings — value positioning grounded in research. Triggers: "prepare me for my meeting", "who am I meeting with", "research this person", "meeting prep", "brief me on this person", "I have a meeting with this company", "get me ready for my call", "what should I know about them", "background on someone before our meeting", "attendee research".

skills/alon-goldenberg/meeting-prep/SKILL.md

Read pinned source

Source commit 5d786aad0c7b2ca59b1abf1f601f9407ca261996

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
No
Observed behavior
Not checked yet
Last checked
Nov 11, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
237
Repository last updated
Oct 20, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Meeting prep

Runs before any meeting where you'd benefit from knowing the people across the table better than they expect. Produces one briefing per meeting: who the attendees are, what they've been saying publicly, how they connect to each other, what's happening at their company, and exactly what to bring up — never a generic dossier.

## The play

### 1. Pin down the meeting

Extract from the request (or ask): attendee names, company, meeting date, and any context the user volunteers ("they're evaluating us", "board intro"). If a calendar is connected, offer to pull today's meetings so the user can pick one; if not, skip silently. If only a name is given, proceed and infer the company from research.

Then establish the **meeting type**, because it gates the whole briefing shape:

| Signal in the request | Type |
|---|---|
Back to top