pre-meeting-brief

pre-meeting-brief is a skill for Claude Code from chrisblattman/claudeblattman. It costs 23 tokens per session (5,957 once invoked), scanned A, original, MIT.

A meeting-preparation workflow that gathers information from calendars, email, messages, project files, and earlier meeting records into a structured brief.

In plain words
What is it for?
Use it to prepare for a project meeting, review prior discussions, identify attendees and open issues, and optionally send the brief to attendees.
Why use it?
It reduces the time spent searching for background before a meeting. The brief highlights decisions, unresolved follow-ups, and preparation needs so the meeting has clearer starting points.

Skill for Claude Code

Written for Claude Code: $ARGUMENTS substitution. Also seen: reads .claude/ paths; mentions CLAUDE.md.

Good fit Use it to prepare for a project meeting, review prior discussions, identify attendees and open issues, and optionally send the brief to attendees.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/chrisblattman/claudeblattman/pre-meeting-brief
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add chrisblattman/claudeblattman --skill pre-meeting-brief
Clone the repo
git clone --depth 1 https://github.com/chrisblattman/claudeblattman

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for pre-meeting-brief

README.md
[![agentmods](https://agentmods.dev/badge/skills/chrisblattman/claudeblattman/pre-meeting-brief/github.svg)](https://agentmods.dev/skills/chrisblattman/claudeblattman/pre-meeting-brief)
Your own site
<a href="https://agentmods.dev/skills/chrisblattman/claudeblattman/pre-meeting-brief"><img src="https://agentmods.dev/badge/skills/chrisblattman/claudeblattman/pre-meeting-brief/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for pre-meeting-brief

Your own site · 80×15
<a href="https://agentmods.dev/skills/chrisblattman/claudeblattman/pre-meeting-brief"><img src="https://agentmods.dev/badge/skills/chrisblattman/claudeblattman/pre-meeting-brief.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 23 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 5,957 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00023 $0.05957
Opus 5.5 $0.00009 $0.02383
Sonnet 5.5 $0.00005 $0.01191
Haiku 4.5 $0.00002 $0.00596

Measured today against content hash 7a8a29aa0286, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

pre-meeting-brief scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured today.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/pre-meeting-brief/SKILL.md · 417 lines

How it starts

The opening of the file, as written. The whole thing — 417 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Pre-Meeting Brief

v1.3 — Granola health-check simplified after the Granola public-API rewrite. Phase 0f no longer probes transcript content (the upcoming meeting has no transcript yet, and probing an arbitrary prior transcript adds latency without a clean health signal — it was producing false HOLLOW). HOLLOW classification removed for Granola entirely; Granola is now OK / DEGRADED / UNAVAILABLE only. Phase 1c fallback clarified to hunt PRIOR project meetings for context, not the upcoming one. Source-confidence table, circuit breaker, and error-handling table aligned. v1.2 — Generates a structured pre-meeting briefing from project communications. Run from a project directory.

Pulls context from WhatsApp, Gmail, Granola, Google Docs, and local files. Surfaces decisions required, open loops, and preparation needs. Optionally emails the brief to attendees.

Prerequisites

Required:

  • Gmail MCP — for searching and reading message context
  • Google Calendar MCP — for identifying the target meeting and attendees

Recommended:

  • Granola MCP — for pulling meeting transcripts
  • WhatsApp MCP — for picking up project group threads
  • A project .claude/CLAUDE.md with team roster, group JIDs, dashboard doc ID, and folder paths

Optional:

  • A send-email helper script if you want one-step send (otherwise the skill creates a Gmail draft)

First-Time Setup

  1. Create a project config at [project-root]/.claude/CLAUDE.md with at minimum:
    # Project Name
    
    ## Team
    - [Name] <[email protected]> — PI
    - [Name] <[email protected]> — Research Manager
    - [Name] <[email protected]> — RA
    
    ## Folders
    - transcripts: `transcripts/`
    - weekly_reviews: `weekly-reviews/`
    
    ## Config
    ```yaml
    project_keywords: [keyword1, keyword2]
    exclude_keywords: [unrelated_term]
    whatsapp_groups: ["Project Group Name"]
    google_doc_id: "YOUR_DOC_ID"
    granola_folder: "Project Folder Name"   # optional
    

Read the full file on GitHub · 417 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. today First seen · 417 lines · 23 tokens per session scan A 7a8a29aa0286

Subscribe to this mod's changes

pre-meeting-brief is a skill published in the GitHub repository chrisblattman/claudeblattman (476 stars, last pushed yesterday), licensed MIT. It adds 23 tokens to every session and 5,957 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-11-06.

Related

pre-meeting-brief compared with skills from other repositories

pre-meeting-brief next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
pre-meeting-briefchrisblattman/claudeblattmanSkill476yesterdayMITA23Claude Code
skill-builderyusufkaraaslan/Skill_SeekersSkill15k1mo agoMITA38Claude Code, Codex
strategic-revisionflonat/flonat-researchSkill1493d agoMITA66Claude Code
skill-creatorflonat/flonat-researchSkill1493d agoMITA41Claude Code
beamer-deckflonat/flonat-researchSkill1493d agoMITA63Claude Code
numerical-checkflonat/flonat-researchSkill1493d agoMITA65Claude Code
skill-preflightflonat/flonat-researchSkill1493d agoMITA34Claude Code