Skills

Agent Skill for Meeting Prep: From Calendar and CRM to a One-Page Brief

Build a Claude skill that turns your calendar and CRM into a one-page meeting brief — in about an hour.

A man writing meeting notes on a notepad beside a laptop while preparing an agent skill for meeting preparation brief
Image: Pixabay / Pixabay Content License

Key Takeaways

  • A meeting-prep skill is a SKILL.md file that produces the same one-page brief for every meeting.
  • Name (max 64 chars, lowercase/hyphens, matches folder) and description (max 1,024 chars) are the two required frontmatter fields.
  • Calendar first, CRM second, email only for gaps — and flag missing data instead of guessing.
  • Test on three real meetings before sharing with the team.

An agent skill for meeting preparation is a reusable set of instructions that turns a calendar invite, CRM notes, and past emails into a one-page brief before every meeting. You build it once as a SKILL.md file, and Claude loads it whenever you ask to prepare — so you walk in knowing who is coming, what they care about, and what you need to decide.

That is the payoff: the skill does the gathering, and you do the thinking.

What a meeting-prep skill actually does

A skill is a folder containing a SKILL.md file with instructions an agent loads on demand. Anthropic describes skills as “organized folders of instructions, scripts, and resources that agents can discover and load dynamically” — and the format is now an open standard at agentskills.io, so the same file works across any skills-compatible agent, not just Claude.

A meeting-prep skill has one job: produce the same one-page brief, the same way, every time. Give it a meeting — “prep me for tomorrow’s 10 a.m. call with Acme Corp” — and it pulls together who is attending and what they care about, what decision the meeting needs to produce, the history (last contact, open deals, unpaid invoices), and what you should say first and ask next. The output is always one page: a five-page dossier never gets read, but a one-page brief gets read in the two minutes before the call starts.

What you need before you start

You need three things, and none of them is technical. First, a place where your meeting facts already live: a calendar (Google Calendar or Outlook) plus a CRM — HubSpot, Zoho, Pipedrive, or even a spreadsheet. The skill cannot invent facts it cannot reach, so if your CRM is empty, the brief will be thin.

Second, a clear idea of a good brief: the five headings it must always have — purpose, attendees, background, talking points, and next steps. If you cannot name them, the skill cannot enforce them.

Third, Claude access where skills work: Claude Code, or claude.ai with skills enabled. In Claude Code, personal skills live in ~/.claude/skills/ and project skills in .claude/skills/ inside the project folder. On claude.ai, you upload the skill folder as a ZIP under Customize > Skills.

Build your meeting-prep skill in 7 steps

Step 1: Name the skill and write its description

Create a folder called meeting-prep. Inside it, create SKILL.md starting with YAML frontmatter:

---
name: meeting-prep
description: Builds a one-page meeting brief from a calendar invite and CRM notes. Use when the user asks to prepare for a meeting, a call, or a client visit.
---

The rules are strict. The name uses lowercase letters, numbers, and hyphens only, is at most 64 characters, and must match the folder name. The description is capped at 1,024 characters, and it is the only part Claude reads before deciding to load the skill — so say what it does and when to use it, in the words you would actually type. A vague description means the skill never fires.

Step 2: Define the one-page output template

Put the brief format in a separate file, assets/brief-template.md. Official guidance says to keep SKILL.md under 500 lines and move templates to files Claude opens only when a step calls for them. The template has five sections: purpose (one sentence), attendee cards (name, role, stance), background (last three interactions), talking points (three maximum), and next steps with owners.

Step 3: Tell the skill where to look

List your sources in order of trust. Calendar first: title, time, attendees, and any agenda in the invite. CRM second: deal stage, last contact, open items. Email third, only for gaps the first two cannot fill. If a source is missing, the skill should say so instead of guessing — “No CRM record found for Acme Corp” beats a confident invention.

Step 4: Set the rules for what goes in — and what stays out

Good briefs are opinionated. Write three rules into the instructions: every claim must come from a named source; no attendee gets more than three bullet points; the brief ends with one recommended outcome, not options. These rules make the tenth brief as good as the first. Without them, the skill drifts — long one day, vague the next.

Step 5: Add the edge cases

Meetings go wrong in predictable ways, so teach the skill to handle them. No agenda? Draft three opening questions. First meeting with a new prospect? Swap history for company background. Internal meeting? Drop the CRM section and pull open tasks instead. Ten minutes of edge cases saves the skill from nonsense when inputs are thin.

Step 6: Test it on three real meetings

Install the skill, then run it on three meetings you have already had: one sales call, one internal review, one first meeting with a stranger. Compare each brief with what you actually needed in the room. If a section went unused, cut it; if you looked something up mid-meeting, add it. Do not share the skill until all three test briefs would have genuinely helped.

Step 7: Share it with your team — safely

A skill folder is plain text, so it goes into version control like any other document. Two safety rules apply. First, never put API keys, passwords, or credentials in a skill: everyone you share it with receives its files, so use a connector and let each person sign in with their own account. Second, only install skills from sources you trust — a skill can direct Claude to run code and call tools in ways that do not match its stated purpose.

Why this skill pays off fast

Meeting prep is the ideal first skill for a small business because it is repetitive, high-stakes, and easy to measure. You repeat the same gathering task before every call, the cost of walking in unprepared is a lost deal or a wasted hour, and the test is simple: did the brief fit on one page, and did you use it?

Frequently asked questions

How is a meeting-prep skill different from just asking Claude to prepare for a meeting?

A plain prompt works once. A skill works the same way every time, for everyone on your team, because the format, the sources, and the rules live in the file — not in whoever wrote the best prompt that morning.

Do I need Claude Code to use this skill?

No. Build and test it in Claude Code by dropping the folder into ~/.claude/skills/, or upload the folder as a ZIP in claude.ai under Customize > Skills. The format is the same either way, because Agent Skills is an open standard.

What if my CRM data is messy?

Start with the calendar only and let the brief say “no CRM record found” where the data is missing. That line is itself useful: it shows you exactly which records need cleaning. Add the CRM as a source once the records are reliable.

The bottom line

A meeting-prep skill turns ten minutes of tab-hopping into a one-page brief you can trust. Build it around a fixed template, name your sources, write the rules down, test it on real meetings, and share it safely. Do that once, and every meeting after it starts with you already knowing what matters.

WebGool Tech Senior AI & Small Business Editor
Verified Contributor

Keep Reading

More in Skills

Explore all

Leave a Comment

Your email address will not be published. Required fields are marked *

Scroll to Top