pre-meeting-brief

Aggregate email threads, Granola history, and vault items into an ephemeral pre-meeting brief.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/yxy23/praxis --skill pre-meeting-brief
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pre-meeting-brief
Source: https://github.com/yxy23/praxis/tree/main/skills/pre-meeting-brief
Command: npx skills add https://github.com/yxy23/praxis --skill pre-meeting-brief

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Pre-meeting preparation is error-prone and time-consuming when it requires pulling attendee context from multiple sources (email, vault memory, calendar). This skill automates ephemeral briefing creation to surface relevant background and talking points before high-stakes meetings.

Core Features & Use Cases

  • On-demand prep for a single upcoming meeting across vault, email, and calendar state, writing an ephemeral brief to briefings/meetings.
  • Reads workspace, North-Star, project-context, and people-context to surface relevant items and prior communications, then distills them into the concise brief.
  • Distillation to durable memory happens later via /post-meeting, which updates people-context.md, workspace.md, and project-context.md while purging the ephemeral brief.

Quick Start

Ask the system to generate a pre-meeting briefing for the next meeting with the specified attendee.

Frequently Asked Questions about pre-meeting-brief

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate a pre-meeting brief from email threads and vault memory?

The skill creates an ephemeral pre-meeting brief by aggregating email threads, Granola history, and active vault items to surface attendee context. It reads workspace, North-Star, project, and people context to distill relevant background into a concise brief for upcoming meetings.

What is the best way to prepare context for high-stakes or first-time meetings?

Automated ephemeral briefing creation prepares context for high-stakes meetings by pulling attendee background from email, vault memory, and calendar state. This surfaces relevant talking points and prior communications to reduce error-prone manual preparation time.

How do I consolidate calendar state and people context into meeting talking points?

You can consolidate calendar state and people context by triggering the skill to read workspace, North-Star, and people-context files. It distills these inputs into a concise brief with attendee context and related materials, written to briefings/meetings as working memory.

Does the pre-meeting brief stay in the vault permanently?

The pre-meeting brief does not stay in the vault permanently; it is written as an ephemeral file to briefings/meetings as working memory. Durable facts are moved to memory later via /post-meeting, which updates people-context, workspace, and project-context files while purging the ephemeral brief.

How does post-meeting distillation update vault memory after a meeting?

Post-meeting distillation updates vault memory by moving durable facts from the ephemeral brief into permanent files. The /post-meeting command updates people-context.md, workspace.md, and project-context.md with new information and then purges the temporary brief from briefings/meetings.

Can I use this meeting prep workflow across project and functional agents?

Yes, you can use this meeting prep workflow across vault, project, and functional agents. It applies to high-stakes or first-time meetings, reading active vault items and prior communications to generate ephemeral briefs that support decision-making across different agent contexts.