# Your first productivity skill

> A meeting-prep skill is the cleanest first win. Build it interactively with Claude, run it before tomorrow's meeting, then improve it

_15 min · beginner · track: personal-productivity · id: meeting-prep-skill_

> **Team:** 
>
> You already met what a [Skill](/course/skills) is. This course turns
> that into your first useful one: a meeting-prep skill that hands you a
> brief before each meeting. It is the cleanest first win in this track.

## Why meeting prep is the right first skill

**Of all the productivity moves Cowork can do, meeting prep is the one with the cleanest before-and-after.** You go from "I will read the email thread on the way to the meeting" to "I have a one-page brief in my inbox before the meeting starts, with the relevant context Cowork pulled from Slack, calendar, email, and Notion."

It is also the skill where the [connectors](/course/wiring-up-connectors) you just turned on pay off most visibly. A meeting brief is the canonical multi-source task: the calendar tells you who and when, the email tells you why, Slack and Notion tell you what has actually been happening since the last meeting. No single connector produces a useful brief on its own. All of them together produce something you wish you had been doing for years.

## What the skill does

**A skill is a short text file that tells Cowork how to do a specific task the right way.** For meeting prep, the instructions are roughly:

1. Identify the meeting. Use the next event on the calendar, or take a meeting title or time from the user.
2. Read the invite description and find the related thread (calendar, email, or Slack).
3. Pull recent context for the topic from Slack channels, Notion pages, and Drive docs.
4. Look up each non-obvious attendee briefly so the brief includes who they are.
5. Output a structured brief: what the meeting is, who is in it, what has happened recently, what decisions are likely needed, and what is open.

That is it. A skill that fits on one screen. The agent does the heavy lifting; the skill just gives it the playbook.

<div class="image-row">
  <img src="/courses/meeting-prep-skill/skill-detail.jpg" alt="Cowork showing the customer-status skill: a description, trigger, and instructional content with bullet points like Recency matters and Respect customer confidentiality" />
</div>

The screenshot above is a different skill (`customer-status`), but the shape is identical: a name, a description, a trigger, and the instructional body. Your meeting-prep skill will look the same.

## Build it, step by step

**Build the skill yourself, with Claude, in one Cowork session.** Do not copy a starter; the result tunes itself to how *you* run meetings, what *you* care about in a brief, and what sources *you* actually read. That fit is the whole reason a personal skill beats a generic one.

1. **Open a new Cowork task and give Claude this prompt:**

> I want to create a meeting-prep skill for myself. Before drafting it, ask me about five questions to understand how I run meetings, what I want out of a brief, and which sources you should pull from. Once you have my answers, draft the skill and save it.

Claude will come back with questions like "do you want a one-paragraph summary or a structured brief with sections?", "should I include a who's-who for non-obvious attendees?", "should I prefer Slack threads or email threads when both exist?". Answer them honestly. The questions are the skill.

2. **Read the draft Claude produces and save it.** Claude can produce skills that are quite long, and that is fine. The first couple of times, read it in detail so you understand what your skill will actually do; once you trust it, skim.

3. **Run it on a real meeting on tomorrow's calendar.** Read the brief that comes back. Notice three things: what it got right, what it missed, what it included that you did not need.

4. **Tell Claude how to improve the skill.** The single most important step in this course: do not patch the output by hand, edit the skill itself. One sentence does it:

> The brief was good but it missed the Notion page for this project. Update the skill so next time it also checks the project's Notion page.

Claude rewrites the skill body, you read the diff, you save. The next run starts at the new bar.

The first version of your skill exists about ten minutes after you start. The third version, after three real meetings and three rounds of feedback, is materially better than anything you would have copied from a starter.

> **Tip:** 
>
> **See how others have written theirs.** The public TechWolf
> [ai-first-toolkit](https://github.com/techwolf-ai/ai-first-toolkit/tree/main/plugins/people-management)
> has worked examples of meeting-prep, one-on-one prep, weekly planner,
> and more. Useful reading once you have your own first version: borrow
> the bits that fit, leave the rest.

## Reflect

- The brief Cowork wrote: would you have produced the same brief by hand if you had the same fifteen minutes? Where did it beat your version, and where did your version still win?
- Which other recurring task in your week looks like meeting prep, same shape but different purpose? That is your second skill.