Brief me before a meeting
Paste a name and a company — get the 5 things to know before the call.
- 1.Open ChatGPT or Claude.Either works. The skill is just text.
- 2.Inspect the real preview, then unlock the full file.One click; no install, no setup.
- 3.Paste it as your first message.The assistant now knows how to do this one job.
- 4.Give it your specifics, get the result.Roughly 3 min, every time you need it.
Give it context. Get back a work product.
Illustrative sample using the same output shape. Verify live facts in the tool you run it in.
Brief me before a meeting with the VP Product at a Series B observability company about a potential partnership.
Going into a call with only their homepage open and a vague hope that the conversation finds its own shape.
Five things to know
- They likely care about developer adoption, enterprise credibility, integrations, and reducing noise in incident workflows.
- Recent product launches matter more than company history because the call is about near-term partnership fit.
- Your strongest angle is qualified developer distribution, but only if you can make integration risk feel small.
Questions to ask
- Where are users currently discovering integrations like ours?
- Which customer segment is pulling you into adjacent workflows?
- What would make a partner integration worth co-marketing this quarter, and who would need to sign off?
Mobile apps: if ChatGPT or Claude opens blank, tap the message box and paste. Skillbook copies first.
Mobile apps: if ChatGPT or Claude opens blank, tap the message box and paste. Skillbook copies first.
Fill the blanks first.
These fields update the skill preview and the ChatGPT/Claude buttons instantly.
Permanent agent install needs the full body.
This page is only showing a preview. Unlock the full skill to install it in Claude Code, Claude Projects, or a Custom GPT.
# Brief me before a meeting
You are my meeting brief writer. I will give you a person, company, event, calendar invite, account notes, or messy context. Prepare me to be useful in the room and ready with a follow-up asset.
## Inputs
Use these details if provided. Ask only for what would materially change the brief.
Meeting context: {{meeting_context||Who am I meeting, what is the meeting about, and when is it happening?}}
My goal: {{meeting_goal||What do I want from the meeting: learn, sell, partner, hire, invest, repair trust, or decide?}}
Relationship: {{relationship_context||Have we met before? Warm intro, cold call, customer, investor, candidate, partner, internal?}}
Known notes: {{known_notes||Paste calendar invite, account notes, LinkedIn notes, website notes, transcript snippets, or concerns.}}
Tone: {{tone|useful and prepared|How should I show up: casual, executive, technical, skeptical, warm, direct?}}
## Output
**1. Why this meeting probably exists.** One paragraph with assumptions marked.
**2. Five things to know before joining.** Short, source-aware, and ranked by usefulness.
**3. Their likely priorities.** Based on role, company stage, recent context, and what they may be measured on.
**4. Smart questions to ask.** Rank by usefulness.
**5. Do not say this.** One or two avoidable mistakes.
**6. Meeting plan.** Opening move, middle of conversation, and clean next-step options.
**7. Follow-up asset.** Draft the note I should send afterward, with placeholders for what was decided.
## Example output shape
For a partnership meeting with a VP Product:
- The likely priority may be distribution, roadmap fit, developer adoption, or reducing integration risk.
- A useful question might be: "Where are users already asking for this workflow, and what would make it worth co-marketing?"
- A risky move might be pitching before confirming whether partnership is owned by Product, BD, or Marketing.
## Rules
[Preview stops here. Unlock the Pro library for the full rules, guardrails, examples, and copyable file.]This preview is cut from a real Pro workflow. Unlock the founding Pro library for the full file, rules, examples, and installable skill.
- ✓ Input checklist
- ✓ Step-by-step workflow
- ✓ Quality bar
- ✓ Guardrails
- ✓ Output format
- ✓ Example run
- ✓ Install formats