prep
/prep
Use when the user has a meeting, call, 1:1, a person to meet, or a decision coming up and needs to walk in prepared. Assembles a one-page brief from context/, wiki/, connections, open loops, and the knowledge graph — who · what · goal · history · open loops · the ask · risks. Trigger on "/prep", "prep me for", "brief me on <person/meeting>", "what do I need to know before", "get me ready for".
- Author
- alirezarezvani ↗
- Repository
- gaios ↗
- Licence
- MIT
- Last repository change
- 06.06.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 06.06.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Use when the user has a meeting, call, 1:1, a person to meet, or a decision coming up and needs to walk in prepared. Assembles a one-page brief from context/, wiki/, connections, open loops, and the knowledge graph — who · what · goal · history · open loops · the ask · risks. Trigger on "/prep", "prep me for", "brief me on <person/meeting>", "what do I need to know before", "get me ready for".
Triggers from the description
Original author description
Use when the user has a meeting, call, 1:1, a person to meet, or a decision coming up and needs to walk in prepared. Assembles a one-page brief from context/, wiki/, connections, open loops, and the knowledge graph — who · what · goal · history · open loops · the ask · risks. Trigger on "/prep", "prep me for", "brief me on <person/meeting>", "what do I need to know before", "get me ready for".
How it works
- When to run
- The output (always this shape)
- Process
- Autonomy
- Guardrails (from CLAUDE.md)
SKILL.md preview
---
name: prep
description: Use when the user has a meeting, call, 1:1, a person to meet, or a decision coming up and needs to walk in prepared. Assembles a one-page brief from context/, wiki/, connections, open loops, and the knowledge graph — who · what · goal · history · open loops · the ask · risks. Trigger on "/prep", "prep me for", "brief me on <person/meeting>", "what do I need to know before", "get me ready for".
---
# Prep
Chief-of-Staff prep: walk into anything already briefed. Pull the scattered context into one page.
## When to run
- Before a meeting / call / 1:1, meeting a person, or making a decision.
- Surfaced by `/daily` ("on the calendar → offer `/prep`").
## The output (always this shape)
```
## Prep — <meeting / person / topic> · <date · time>
**Goal** — what a good outcome looks like for you, in one line.
**Who** — attendees + the one thing that matters about each.
**Context** — the 3–5 facts / history you need (each with a source).
**Open loops** — what's owed by/to them (open-loops · wiki · threads).
**Your move** — the ask, 2–3 talking points, the decision you want.
**Risks / landmines** — what could go sideways + how to handle it.
```
## Process
1. **Scope it.** Identify the meeting / person / topic and the user's goal.
2. **Gather (read, don't guess):** `context/` (about-me, business, team, priorities), `wiki/` (past thinking), `decisions/log.md`, open loops (`tools/open_loops.py`), and `/graph-query` to surface non-obvious connections (who/what relates to this).
3. **Pull live where connected.** If calendar / CRM / notes MCPs are wired (`connections.md`), pull the invite, the account, and the last meeting notes. If nothing is connected, work from files and say so.
4. **Synthesize to one page** in the shape above. Cite a source for each fact (Verification Gate); flag anything unconfirmed.
5. **Offer next moves:** `/draft` a pre-read or follow-up; `/decide` if a decision is the point.
## Autonomy
**L2** — assembles the brief; the human runs the meeting. Read-only on external systems.
## Guardrails (from CLAUDE.md)
- **Cite, don't invent** — every fact traces to a source; flag gaps.
- Pull confidential specifics live; never persist them to the repo.
- Respect the sensitive-data line — no PHI/PII in the brief or the repo.
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · alirezarezvani/gaios | 100 | MIT |
| coffeedroplabs/workhunt-claude-plugin | 100 | MIT |
| web3illy/private-second-brain-skills | 100 | MIT |
Database snapshot: 13.11.2026 · package version e5dcc6129e21 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 1 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 90meeting-prep
Prepare for a meeting (who is in it, what was last said with them, what the user owes them and wants from them) as a one-page brief. Use when the user asks to prepare for or get ready for a meeting, a call or a visit; a trigger can run it before every meeting with a client. - 90meeting-prep-brief
Build a pre-meeting brief from a calendar event: attendees, last interactions, open threads, and talking points. Use when the meeting can be found on the calendar, as in 'prep me for my next meeting', 'brief me on the 2pm call', or a sweep of the coming days' external meetings.… - 90meeting-prep
Build a pre-meeting briefing — who's in the room, what they care about, your goal, and the questions to ask. Trigger when the user asks to prep for a meeting or call, "what should I know before", or names an upcoming meeting. - 100minutes-prep
Interactive meeting preparation — builds a relationship brief and talking points before a call. Use when the user says "prep me for my call with", "I'm meeting with X", "prepare me for", "what should I bring up with", "meeting prep", "get ready for my call", or wants to review… - 100minutes-prep
Interactive meeting preparation — builds a relationship brief and talking points before a call. Use when the user says "prep me for my call with", "I'm meeting with X", "prepare me for", "what should I bring up with", "meeting prep", "get ready for my call", or wants to review… - 100call-prep
Pre-call brief for an upcoming meeting - attendees, account history, prior call context from transcripts, open opportunity status, and suggested discovery questions. Use when the user asks "prep me for [meeting/company]", "call prep [company]", "I'm meeting with [company], prep…