BrianRWagner/ai-marketing-claude-code-skills / meeting-prep
meeting-prep
VerifiedGenerate a pre-meeting prep brief in Claude Code. Researches participants, pulls vault context, builds agenda, surfaces sharp questions. Use when user says "prep for this meeting," "I have a call with," "meeting tomorrow with," or "prep brief for [name/company]."
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 4.4 KB |
| references/brief-template.md | markdown | 1.0 KB |
| references/meeting-types.md | markdown | 2.3 KB |
| references/question-banks.md | markdown | 2.7 KB |
references/brief-template.md
View on GitHub# Meeting Prep: [Name] | [Date] [Time]
**Meeting type:** [Client / Sales / Strategy / Partnership / Interview]
**Duration:** [time]
**Their role:** [role at company]
**Relationship stage:** [new / existing / lapsed]
---
## Why This Meeting Matters
[1-2 sentences on stakes, objective, and desired outcome]
## 3 Priorities for This Call
1. [Priority 1]
2. [Priority 2]
3. [Priority 3]
## Context From Vault
[Pulled notes, open items, prior commitments — or "No prior history found"]
## What They Care About Right Now
[Recent signals: posts, news, company context, anything fresh]
## Questions to Ask
1. [Question — should reference specific research]
2. [Question]
3. [Question]
4. [Question]
5. [Question]
6. [Optional question]
7. [Optional question]
## Watch For / Potential Friction
[Known objections, sensitivities, open loops, or landmines]
## Desired Outcome
[What does a successful meeting look like in one sentence?]
## Next Step to Propose
[Specific and concrete: "schedule X," "send Y," "agree on Z"]
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |