meeting-prep-cc

Overview of meeting-prep-cc skill

What meeting-prep-cc does

meeting-prep-cc is a Claude Code skill for turning a rough meeting into a usable prep brief. It looks for participant and company context, searches your vault for prior mentions, then organizes the result into an agenda and question list. If you want the meeting-prep-cc skill to replace a blank-page prompt, this is the right fit.

Who should install it

Install meeting-prep-cc if you already keep notes in Obsidian or a similar markdown vault and need faster prep for sales calls, strategy reviews, partnership meetings, interviews, or internal client work. The biggest win is for people who know the meeting matters but do not want to manually search their notes every time.

Why it stands out

The main differentiator in meeting-prep-cc is that it is workflow-oriented, not just a generic “write me meeting notes” prompt. It asks for a specific meeting type, searches for vault history, and produces a brief you can use immediately in Claude Code. It is best when you want the meeting-prep-cc guide to give you a repeatable prep process, not a one-off summary.

How to Use meeting-prep-cc skill

Install and trigger it

For meeting-prep-cc install, add the skill to your Claude Code setup, then open Claude Code inside the vault you want it to search. The repo’s core instruction is simple: invoke the skill with the meeting details in a structured sentence, such as meeting partner, company, type, and time. That context matters because the skill is designed to search and synthesize, not to guess.

Give it the right input

A strong meeting-prep-cc usage prompt includes:

• Participant name
• Company
• Meeting type
• Meeting date or time
• Optional prior notes or the last meeting summary

Example: Run the Meeting Prep skill. Meeting with Maya Chen from Northstar. Type: partnership. Time: Tuesday 2 PM. Prior notes: they asked about pricing and onboarding.
This is better than “prep for my meeting” because it gives the skill enough structure to find the right vault matches and shape the agenda.

Read these files first

For a practical meeting-prep-cc guide, start with SKILL.md. Then inspect any companion files the repo may include, especially README.md, AGENTS.md, metadata.json, and folders like rules/, resources/, references/, or scripts/ if they exist in your copy. In this repository, the main behavior lives in SKILL.md, so that file is the fastest path to understanding how the skill actually runs.

Workflow tips that improve output

Use meeting-prep-cc for Meeting Prep when you already have a target person or company and want a brief that is grounded in your own notes. If the meeting type is missing, provide it before asking for output; the skill explicitly uses that field to choose its framing. Keep your input factual and sparse: name, company, type, time, and one or two known constraints usually produce a cleaner brief than a long freeform paragraph.

meeting-prep-cc skill FAQ

Is meeting-prep-cc only for Obsidian users?

It is most useful if your notes live in an Obsidian vault or another markdown directory Claude Code can search. If your information is stored elsewhere, you can still use the logic, but the meeting-prep-cc skill will be less effective unless you adapt the vault-search step.

How is this different from a normal prompt?

A normal prompt can draft a prep note, but meeting-prep-cc adds a repeatable intake and search flow. That means it is more likely to surface prior mentions, missed context, and better questions instead of producing generic meeting advice. If your main need is “give me a brief from my notes,” the skill is a better fit than starting from scratch.

Is the meeting-prep-cc skill beginner friendly?

Yes, if you can provide basic meeting details and point Claude Code at the right vault. The main beginner mistake is under-specifying the meeting. If you cannot name the participant, company, or meeting type, the brief will be weaker and the skill may need follow-up questions.

When should I not use it?

Do not use meeting-prep-cc if you need live web research, CRM integration, or automated scheduling. It is a prep skill, not a general research agent. It also adds less value when you have no vault history at all, because the strongest part of the workflow is the note search and synthesis.

How to Improve meeting-prep-cc skill

Start with a sharper meeting brief

The best meeting-prep-cc results come from inputs that match the skill’s intake fields. Instead of “prep for a call,” give the person, company, meeting type, and time. If you know the goal, add it: goal: renew contract, goal: qualify fit, or goal: unblock launch. That small detail helps the brief prioritize the right questions.

Include the context the skill cannot infer

If there is a previous thread, include it directly: last meeting summary, open objections, promised follow-up, or a known decision point. The skill can search your vault, but it cannot reliably infer what matters most unless you tell it. This is the biggest quality lever for meeting-prep-cc usage.

Watch for weak search matches

A common failure mode is vague names or inconsistent note titles. If your vault contains multiple people with similar names, add company, project, or team context so the search stays focused. If the first result is noisy, rerun meeting-prep-cc with a narrower prompt such as the exact company name, meeting date, or topic.

Iterate on the brief, not just the prompt

After the first output, improve the next run by telling the skill what was missing: better agenda ordering, stronger questions, more direct risk spotting, or more history from the vault. That feedback loop turns meeting-prep-cc skill output from “useful summary” into a reliable prep habit.