Pre-meeting intelligence pack — 6-section brief + 3/3/3 framework. Agent skill.
SaferSkills independently audited m365-meeting-prep (Agent Skill) and scored it 79/100 (yellow). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 5 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 5 flagged
The text {match} tells the agent to skip the normal "ask the user first" gate. Used adversarially it removes the human-in-the-loop check before destructive or sensitive actions, turning a normally-gated agent into a fire-and-forget executor.
A bulleted imperative like {match} tells the agent to never reveal, disclose, or mention something to the user. Used adversarially it can instruct the agent to hide its tool calls or lie about what it did — stripping the transparency a user relies on to trust the agent.
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
The difference between a meeting that converts and one that wastes everyone's time is preparation depth. This skill produces a focused intel pack the user can read in <5 minutes before any meeting: who's in the room, what we know about them, what's happened between us, and the 3 things to ask / say / not-say.
Core principle: A great meeting brief has specific, recent, and actionable info — not generic "the company is in tech and has employees". The user already knows the basics.
1. Who are you meeting with? (Names + Company)
2. Why? (Sales discovery / customer check-in / investor pitch / hiring / partnership / other)
3. When? (Today, tomorrow, this week)
4. Where are the source materials?
- Calendar invite text
- LinkedIn profiles (URL or pasted text)
- Email thread
- CRM record export
- Notes from prior meetingsIf user pastes raw material, parse it. If user says "everything's in [Notion / HubSpot / Outlook]", note that you can't access logged-in apps — ask them to copy-paste the key bits.
Produce this structure for every meeting. Adjust depth based on meeting importance.
Two sentences max:
For each person in the meeting:
**[Name]** — [Title], [Company]
- LinkedIn: [headline]
- Background: [most relevant 2-3 prior roles or things]
- Decision power: [Champion / Decision-maker / Influencer / Blocker / Unknown]
- Last contact: [Date, what happened]
- Personal notes: [Hobbies, alma mater, quirks from CRM]If user can't tell decision power → note "Unknown" and add to "questions to ask".
- **Industry / model**: [SaaS B2B / e-comm / services / etc.]
- **Size / stage**: [Headcount, revenue if known, funding stage]
- **Recent news**: [Things from last 30 days — press, hiring, layoffs, product launches]
- **Their current pain (as we understand it)**: [from CRM notes or discovery]
- **Their relevant tech stack**: [What they use that's relevant to us]
- **Competitors using us / them**: [If known]- **First touch**: [When, how — inbound / outbound / referral]
- **Total interactions**: [N emails, M meetings]
- **Deal stage / status**: [Current pipeline stage]
- **Last meaningful interaction**: [Date, outcome]
- **Open commitments** (theirs and ours):
- We promised: [list]
- They promised: [list]- **Goal**: [One specific outcome — e.g., "Get verbal commitment on pricing", "Schedule technical eval", "Confirm renewal"]
- **Stretch goal**: [Bigger win possible]
- **Walk-away**: [Minimum acceptable outcome]
- **What we offer in this meeting**: [Concrete asset — demo, proposal, intro, etc.]The actionable kernel:
**3 questions to ask:**
1. [Specific, opens dialogue]
2. [Surfaces budget / timeline / authority]
3. [Probes objection or risk]
**3 things to say:**
1. [Specific to their pain or signal]
2. [Demonstrates research / personalization]
3. [Differentiates from competitor X]
**3 things NOT to say:**
1. [Topic that derailed last time]
2. [Sensitive area — internal restructure, etc.]
3. [Premature topic — pricing too early, etc.]See references/meeting-types.md for type-specific depth tweaks.
"Joined Salesforce in 2018, became Director in 2022". Useless — anyone can read LinkedIn.
✅ Instead: "Joined Salesforce in 2018; ran their SMB segment which is exactly our ICP. May know our churn problem from inside."
A 4-page brief won't get read. Max 1 page printed.
You're not writing a script. You're loading ammunition the user can pull from naturally.
Always confirm meeting time in both parties' time zones.
If any of these are true, surface prominently at top of brief:
| Meeting purpose | Single most important thing |
|---|---|
| First sales call | Their pain (Section 3) |
| Second sales call | Their budget / timeline (Section 6 questions) |
| Demo | Their use case fit (Section 4) |
| Closing call | Their objections (Section 6 "not to say") |
| Renewal | Usage data + ROI (Section 4) |
| Partnership | Mutual value (Section 5) |
| Investor | Their fund's portfolio overlap (Section 3) |
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.