OpenParable
Skip to content
← Back to skills

Meeting Prep

Productivity
meeting-prep

Meeting Prep is an Agent Skill for productivity published in the MODSetter/SurfSense repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Pull together briefing materials before a scheduled meeting

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/MODSetter/SurfSense/blob/HEAD/surfsense_backend/app/agents/chat/multi_agent_chat/main_agent/skills/builtin/meeting-prep/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/meeting-prep, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

Meeting preparation

When to use this skill

The user mentions an upcoming meeting, call, or interview and asks you to "prep", "brief me", "pull background", or "what do I need to know about X before tomorrow".

Output structure

Always produce these sections (omit any with no signal — don't pad):

  1. Attendees & context — who's in the room, their roles, what they care about. Pull from KB notes about prior interactions; supplement with public profile facts via task(google_search, ...) when names or companies are unfamiliar.
  2. Open threads — outstanding action items, unresolved decisions, last-mentioned blockers from prior conversation history.
  3. Recent moves — within the last 30 days: relevant launches, hires, news. Cite KB chunks when present, otherwise external sources.
  4. Suggested questions — 3-5 questions the user could ask, tailored to the open threads and the attendees' likely priorities.

Source ordering

  • Always check the user's KB first for prior meeting notes, internal docs, or Slack threads about these attendees.
  • Only fall back to task(google_search, ...) for publicly verifiable facts — never to fabricate a participant's preferences or relationships.