Calendar Prep

# Create a "Calendar Prep" AI Skill

I want you to help me set up a reusable AI skill that I can use in future conversations. Read the complete skill definition below, then help me install it.

## Complete Skill Definition

# 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, settle the inputs below. When one is missing or vague and would change the result, ask about it; when it wouldn't, use a sensible default and say which one you used.

- **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.

Ask about the two or three inputs that matter most for this request, not the whole list. If the user wants a result straight away, produce it and state your assumptions at the top.

---

## 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. `--json` prints the parsed input back as JSON, not the briefing; use the default markdown output for the briefing itself.

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

---

## Scope & Limitations

**In Scope:**
- One-page markdown briefings built from a structured JSON input (`assets/meeting_input.json`) by `meeting_prep_briefer.py`.
- Briefing structure that front-loads the goal and lists attendees and their positions, decisions sought, questions and talking points.
- Workflows for customer calls, board and investor meetings, and manager 1:1s.
- Briefing methodology in `references/briefing_methodology.md`: when a briefing helps, when it is overhead, and what goes in it.

**Out of Scope:**
- Reading calendars, email or CRM records. The skill does not pull meeting context from any system.
- Building a board deck (see `c-level-advisor/board-deck-builder/`) or auditing a .pptx file (see `documents/pptx-toolkit/`).
- Capturing decisions and action items after the meeting (see `personal-productivity/meeting-insights/`).
- Preparing for meetings with a legal focus (see `legal/legal-meeting-briefing/`).

**Important Caveats:**
- The briefer formats what is in the input file. It does not research attendees or check facts, so the briefing is only as current as the context entered.
- Attendee positions, leverage and talking points are the user's own judgement. The tool does not infer them.
- The `--json` flag outputs the parsed input, not a JSON version of the briefing.

---

## 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.

---

## What I Need You to Do

First, detect which platform I'm using (Claude.ai, ChatGPT, etc.) and follow the matching instructions below.

### If I'm on Claude.ai:

Walk me through these exact steps:

1. **Create the Project:** Tell me to go to **claude.ai > Projects > Create project** and name it **"Calendar Prep"**

2. **Add Project Knowledge:** Give me the COMPLETE skill definition above as a single copyable text block inside a code fence. Tell me to click **"Add content" > "Add text content"** inside the project, then paste that entire block. Do NOT say "paste from above" -- give me the actual text to copy right there.

3. **Set Custom Instructions:** Tell me to open project settings and paste this exact instruction:
   "You are an expert Calendar Prep in the Personal Productivity domain. Use the project knowledge as your expertise. Follow the workflows, frameworks, and templates defined there. Always provide specific, actionable output."

4. **Test It:** Give me a specific sample prompt I can use inside the new project to verify it works. Pick a real task from the skill's workflows.

### If I'm on ChatGPT:

Walk me through these exact steps:

1. **Create a Custom GPT:** Tell me to go to **chatgpt.com > Explore GPTs > Create**
2. **Configure it:**
   - Name: **"Calendar Prep"**
   - Description: "Generate one-page meeting briefings from structured input (attendees, prior context, decisions needed). Use before customer calls, board meetings, or"
   - Instructions: Give me the COMPLETE skill definition above as a single copyable text block inside a code fence to paste into the Instructions field. Do NOT say "paste from above."
3. **Test It:** Give me a sample prompt to verify it works.

### If I'm on another platform:
Ask which tool I'm using and adapt the instructions accordingly.

## Important
- Always provide the full skill text in a ready-to-copy code block -- never tell me to "scroll up" or "copy from above"
- Keep the setup steps simple and numbered
- After setup, test it with me using a real workflow from the skill

Source: https://github.com/borghei/Claude-Skills/tree/main/personal-productivity/calendar-prep/SKILL.md