meeting-prep-research

name

meeting-prep-research

description

Research and prepare for a meeting by turning a meeting title, agenda, attendee list, transcript, prior notes, linked material, OpenClaw memory context, Obsidian notes, or user-provided context into an actionable Preparation.md with objectives, background, questions, agenda, decisions needed, risks, and follow-up prompts. Use when the user asks to prepare for a meeting, research participants or organizations before a meeting, build a briefing, or create/update preparation notes.

Meeting Prep Research

Use this skill to prepare a useful meeting briefing from the context the user provides or explicitly asks you to gather.

Core Boundary

Keep this skill platform-neutral and privacy-safe. Do not assume a specific calendar, CRM, notes app, vault path, private agent runtime, customer list, personal preference file, or local automation setup.

If a local runtime provides private tools or preferences, treat them as an external overlay. Read references/integration-overlays.md when the task mentions local agent integrations, private notes, CRM context, calendar context, OpenClaw memory, Obsidian vault discovery, or other install-specific data sources.

Inputs To Collect

Collect or infer only what is needed:

• Meeting title or purpose.
• Date/time and expected duration if available.
• Attendees, roles, organizations, or stakeholder groups.
• Agenda, invite text, prior notes, transcript, linked docs, tickets, emails, or user-provided context.
• Obsidian vault path/name or meeting package path if writing to an Obsidian vault.
• Desired output destination, such as an existing Preparation.md, an Obsidian meeting package, or a plain response in chat.
• Research scope: internal context only, public web research, or both.

Ask a brief follow-up only when the missing input would materially change the prep. Otherwise, make a cautious assumption and mark unknowns as TBD.

Research Workflow

1. Start with user-provided and local context. Prioritize agenda, prior notes, existing decisions, open tasks, and the user's explicit goals over generic public information.

2. If OpenClaw memory tools are available and the task asks for prior context, preferences, recurring decisions, or "what do we already know", search memory narrowly before doing public research. Treat memory results as private working context.

3. Use public web research only when the user asks for it, when participants or organizations are public-facing, or when current facts would materially change preparation. Cite sources for public claims.

4. Separate facts from interpretation. Label guesses as hypotheses and unknowns as TBD. Do not invent attendee roles, recent events, budgets, goals, or commitments.

5. Keep private context private. Do not copy private notes, CRM details, emails, customer names, or internal project details into public docs or external tools unless the user explicitly asks for that disclosure.

6. Produce a practical preparation artifact. Optimize for what the user should know, decide, ask, bring, and do next.

Preparation.md Shape

Use this structure for a folder-based meeting package:

# Preparation

## Objective

- What this meeting should accomplish.

## Context Snapshot

- Relevant background, prior decisions, current state, and constraints.

## People And Organizations

- **Name or role**: why they matter for this meeting.

## Agenda

- Topic or sequence.
    - Outcome wanted: decision / alignment / input / update

## Questions To Ask

- Question that would change the outcome.
    - Why it matters: short reason

## Decisions Needed

- Decision to make or clarify.
    - Owner: Name or `TBD`

## Risks And Watchouts

- Risk, dependency, ambiguity, or tension to manage.

## Follow-Up Prompts

- Message, task, document, ticket, or next meeting likely needed after this.

## Sources

- Link, file, note, or user-provided context item used.

For Obsidian meeting packages, use real tabs or at least four spaces for nested Markdown list items. Read ../../docs/obsidian-meeting-package.md when creating or updating a folder-based meeting package. If the vault path is not configured, use that document's vault discovery guidance before writing files.

Output Rules

• Write to Preparation.md when the user points to a meeting package or asks for prep notes in an Obsidian-style folder.
• Do not guess which Obsidian vault to use. Use a configured vault path, a user-provided meeting package path, or ask the user to choose from discovered candidates.
• Use concise bullets, not a long research memo, unless the user asks for depth.
• Keep "nice to know" background out unless it affects questions, risks, decisions, or follow-up.
• Include a Sources section when research uses web pages, external docs, or specific local files.
• If research was not performed, say "Sources: user-provided context" or omit the section if the user wants a lightweight note.
• Preserve uncertainty. Use TBD, Unknown, or Hypothesis instead of filling gaps.