prep-for

name	prep-for
description	Brief the owner before a meeting or conversation with a person, company, or project — sweep what we already know (crm + knowledge, plus slack, calendar, and gmail when connected), anchor to any upcoming meeting with them, and for people or orgs we don't know, widen to a web search for public background. Use for "prep me for my meeting with X", "brief me on X before the call", "what do we know about X".
metadata	{"version":"1.1.0","author":"context","tags":["prep","meeting","briefing","crm","knowledge","slack","web"]}

Prep For

Runtime skill — a playbook the deployed @context agent runs for its owner, invoked in natural language. Not a coding-agent workflow; those live in .agents/skills/.

Pull together a tight pre-meeting brief on a subject — a person, company, or project the owner is about to engage. Read-only: gather and synthesize, never file.

Procedure

1. Identify the subject. Pin down who/what from the request ("my 3pm with Sarah Lee from Acme" → person Sarah Lee, org Acme). If it's genuinely ambiguous and a wrong guess would waste the brief, ask one clarifying question instead of guessing.
2. Sweep what we already know — internal first. Run an entity sweep:
   • query_crm — contacts, notes, projects, and any reminders/meetings tagged to the subject (name, company, tags, meeting attendees). This is our relationship + history.
   • query_knowledge — knowledge-base prose about the subject (runbooks, summaries, "what I know about X").
   • (when connected) — recent threads mentioning the subject; the latest exchanges are often the freshest context in the brief.