prep
$
npx mdskill add alirezarezvani/gaios/prepChief-of-Staff prep: walk into anything already briefed. Pull the scattered context into one page.
SKILL.md
.github/skills/prepView on GitHub ↗
---
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.
More from alirezarezvani/gaios
- draftUse when the user needs a written communication drafted in their voice — an email, a Slack/Teams message, a team update, an announcement, a reply to a thread, or a post. Produces a ready-to-review draft matching references/voice.md; never auto-sends external. Trigger on "/draft", "draft an email", "write a reply", "draft the update", "draft the announcement", "respond to this thread in my voice".
- exec-cockpitTemplate skill for a leadership-transition / executive cockpit — when someone steps into or covers a leadership role and needs to not drop anything. Produces a handoff doc + decision-rights map, an "open loops" tracker, a team-comms cadence, and a recurring report/update drafter. Trigger on "/exec-cockpit", "handoff doc", "decision-rights map", "open loops tracker", "cover for <role>", "interim <role>". Customize the placeholders to your situation.
- graphUse when the user wants to build, refresh, or visualize the repo's knowledge graph — code structure plus the committed wiki/ — via graphify. Produces an interactive graph + a GRAPH_REPORT.md of God Nodes, surprising connections, and suggested questions. Trigger on "/graph", "build the knowledge graph", "graph the repo", "map the codebase", "refresh the graph", "visualize the second brain".
- graph-ingestUse when the user brings an external source worth keeping — a URL, a paper, a tweet/thread, a blog post, a docs page — and wants it pulled into the second brain. Fetches the source into the git-ignored capture inbox, admits it to the committed wiki through the admission policy, then refreshes the knowledge graph so it joins the rest of your thinking. Trigger on "/graph-ingest", "ingest this url", "add this paper to my knowledge", "add this tweet/page to my knowledge", "capture this source".
- graph-queryUse when the user asks a question about how things in the codebase or wiki relate — what connects two things, how something works end to end, what depends on what, or what a concept means in this repo. Answers from the knowledge graph in graphify-out/graph.json, with source-location citations. Trigger on "/graph-query", "ask the graph", "what connects X to Y", "trace how X works", "explain <concept> from the graph", "shortest path between".
- level-upUse weekly to find and ship one new automation. Walks the 3Ms interview — Mindset (find the candidate) → Method (scope one) → Machine (build it). Trigger on "let's level up", "what should I automate next", "find me leverage this week", or as a Friday ritual. One run = one shipped artifact.
- structureUse when the user brings any fuzzy, half-formed, or interrupt-driven input — an order from a boss, a forwarded email thread, a ticket, a chat message, a "can you look into X", a raw idea — and it needs framing before work starts. Turns the input into a structured brief (Context · Desired outcome · Goal · Owner · Next step · Decision needed). This is the AIOS's front door; run most things through it first. Trigger on "/structure", "frame this", "what's the actual ask here", "structure this", or any vague task that lacks a defined outcome.