Skip to content
cccskills
FreePublished on GitHub

calendar-prep

Generate one-page meeting briefings from structured input (attendees, prior context, decisions needed). Use before customer calls, board meetings, or 1:1s to prepare a pre-read or briefing.

The English summary is being prepared. Showing the original description.

See how to install

Files included (4)

  • SKILL.md3.3 KB
  • assets/meeting_input.json3.0 KB
  • references/briefing_methodology.md3.0 KB
  • scripts/meeting_prep_briefer.py5.2 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Calendar Prep

Convert structured meeting context into a one-page briefing in seconds.


Keywords

meeting prep, calendar prep, briefing, pre-read, pre-meeting, talking points, agenda, board meeting, customer call, 1:1


Clarify First

Before generating the briefing, confirm these inputs. If any is unknown or vague, ASK — do not assume:

  • Meeting type & attendees — customer call vs board vs 1:1 changes the briefing's structure, tone, and emphasis
  • Your goal / decision sought — this becomes the front-loaded first line of the briefing
  • Prior context — last contact, open issues, current status; without it the briefing is generic and useless

Stop rule: ask only the 2-3 that most change the output. If the user says "just draft it," proceed and list your assumptions at the top of the artifact.


Quick Start

  1. Fill in assets/meeting_input.json with attendees, context, decisions needed, supporting links
  2. Run: python scripts/meeting_prep_briefer.py meeting_input.json
  3. Read the briefing 5 minutes before the meeting

Core Workflows

Workflow 1: Customer Call Prep

  1. Pull the customer's recent activity, last meeting notes, current account status
  2. Fill input JSON with: attendees, last contact, open issues, your goal, decisions you're trying to make
  3. Run briefer
  4. Walk in knowing: what you want, what they want, where you have leverage

Time Estimate: 10-15 minutes per major customer call.

Workflow 2: Board / Investor Meeting Prep

  1. Pull metrics dashboard, prior board deck, last investor update
  2. Build input JSON; emphasize decisions sought from the board
  3. Pair output with documents/pptx-toolkit/ deck audit

Time Estimate: 30-60 minutes per board meeting.

Workflow 3: Manager 1:1 Prep

  1. Compress the past two weeks: top 3 wins, top 3 challenges, top 3 asks
  2. Run briefer
  3. Lead with asks (1:1s default to status; the leverage is in asking)

Time Estimate: 5-10 minutes per 1:1.


Tools

meeting_prep_briefer.py

Reads a structured JSON input describing meeting context and produces a one-page briefing in markdown.

python scripts/meeting_prep_briefer.py meeting_input.json
python scripts/meeting_prep_briefer.py meeting_input.json --json

Reference Guides

  • references/briefing_methodology.md — When briefings help and when they don't, format conventions

Templates

  • assets/meeting_input.json — Input file template

Best Practices

  • One page max. A 3-page briefing is one you won't read.
  • Front-load the decision. The first sentence should be the decision you want.
  • Read the briefing. Generating one without reading it is performance theater.
  • Capture outputs. Pair with personal-productivity/meeting-insights/ post-meeting to convert the briefing's questions into the meeting's decisions.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

This skill should be used when the user asks to "check accessibility", "audit WCAG compliance", "scan HTML for a11y issues", "check color contrast", or "find accessibility violations in web pages".

The English summary is being prepared. Showing the original description.

borghei/Claude-Skills962Updated Oct 7, 2026

Design and run statistically rigorous A/B tests and experiments. Use when planning experiments, calculating sample sizes, designing test variants, selecting metrics, analyzing results, or when someone says "let's test that."

The English summary is being prepared. Showing the original description.

borghei/Claude-Skills962Updated Oct 7, 2026

Design and analyze A/B tests: sample size, test duration, and statistical significance for conversion experiments. Use when setting up an A/B test, calculating sample size, designing an experiment, or analyzing results.

The English summary is being prepared. Showing the original description.

borghei/Claude-Skills962Updated Oct 7, 2026

Sales execution across pipeline, discovery, demos, negotiation, and closing. Use when qualifying opportunities, running MEDDIC discovery, building account plans, handling objections, structuring proposals, or forecasting pipeline.

The English summary is being prepared. Showing the original description.

borghei/Claude-Skills962Updated Oct 7, 2026

Design ad creative across Google, Meta, LinkedIn, Twitter/X, and TikTok with platform format specs, headline formulas, and A/B testing. Use when writing ad copy, generating headline variations, creating ad sets, or validating creative.

The English summary is being prepared. Showing the original description.

borghei/Claude-Skills962Updated Oct 7, 2026

aeo

Free

Answer Engine Optimization (AEO): optimize content to be cited by LLMs (ChatGPT, Claude, Perplexity, Gemini) in their answers. Use when designing content for LLM citation, auditing citability, or structuring Q&A schema.

The English summary is being prepared. Showing the original description.

borghei/Claude-Skills962Updated Oct 7, 2026

See all skills by borghei

Report a problem with this skill