How to build your first Claude Code skill in 10 minutes (step by step)

A Claude Code skill is a reusable workflow that Claude follows the same way every time. Instead of re-explaining what you want in every conversation, you define the process once. Then you say "run the meeting prep skill" and it does exactly what the skill document says.

Skills are what turn Claude Code from a smart assistant into a reliable operator. Without them, every session starts from scratch. With them, Claude Code handles recurring work the same way a well-trained team member would.

You do not need to be a developer to build one. A skill is a markdown file with a clear set of instructions. If you can write a checklist, you can write a skill.

What you need before starting

• Claude Code installed and running. If you have not set this up yet, start with the getting started tutorial.
• A project folder. Any directory where you want Claude Code to work. This will be your workspace.
• A task you repeat at least weekly. Meeting prep, content drafts, email triage, weekly planning. Pick one you know well.

For this tutorial, we will build a meeting prep skill. You tell it who you are meeting with, and it produces a one-page brief with background research, talking points, and follow-up items.

Step 1: Create the skill directory (1 minute)

Inside your project folder, create the skill structure:

mkdir -p .claude/skills/meeting-prep
touch .claude/skills/meeting-prep/SKILL.md

That is the entire structure. A folder and a markdown file. The folder name is the skill name. The SKILL.md file is the process definition.

Step 2: Write the skill definition (5 minutes)

Open SKILL.md and write the process. Here is a working meeting prep skill:

---
name: meeting-prep
description: Prepare a one-page brief for an upcoming meeting
---

# Meeting Prep

## Input
- Who: the person or company you are meeting with
- When: the meeting date and time
- Context: any notes about the meeting purpose

## Process
1. Research the person/company using web search
2. Check if we have any prior notes or history in memory
3. Identify 3-5 relevant talking points based on their business and our services
4. Draft 2-3 questions to ask that show preparation
5. Note any follow-up items from previous interactions

## Output
Write a brief with these sections:
- **Background**: who they are, what they do, recent news
- **Our angle**: why this meeting matters, what we can offer
- **Talking points**: 3-5 specific conversation starters
- **Questions to ask**: 2-3 smart questions
- **Follow-ups**: anything outstanding from past interactions

Save the brief to `notes/meeting-prep-[name]-[date].md`

That is a complete skill. Notice what it includes: clear inputs, a step-by-step process, and a defined output format. Claude Code reads this and knows exactly what to do without you explaining it each time.

Step 3: Test the skill (3 minutes)

Open Claude Code in your project folder and say:

Prep for my meeting with Sarah Chen from Acme Corp, Thursday at 2pm.
She wants to discuss automating their client onboarding process.

Claude Code will find the meeting-prep skill based on the description match, follow the process steps, research Sarah Chen and Acme Corp, and produce a formatted brief saved to your notes folder.

The first time, check the output carefully. Is the format right? Did it research the right things? Are the talking points relevant? If something is off, edit the SKILL.md to be more specific.

Step 4: Refine based on real use (1 minute)

After using the skill a few times, you will notice patterns. Maybe you always want it to check LinkedIn. Maybe you want talking points specific to your industry. Add those details to the skill:

## Process
1. Research the person/company using web search
2. Check their LinkedIn profile for recent posts or job changes
3. Check if we have any prior notes or history in memory
4. Identify 3-5 talking points related to field service automation
   (our core offering)
5. Draft 2-3 questions that demonstrate industry knowledge
6. Note any follow-up items from previous interactions

Each refinement makes the skill better. After a month, it produces meeting briefs that would take you 30 minutes to research and write manually.

Why this beats prompting

You could type detailed instructions every time you need meeting prep. Some people do. Here is why a skill is better:

• Consistency. The skill follows the same process every time. No forgetting to check for prior history. No skipping the research step because you are in a rush.
• Improvement over time. When you edit the SKILL.md, every future execution benefits. With prompts, you improve one conversation and the next one starts from scratch.
• Delegation. Anyone on your team can trigger the skill and get the same quality output. The process knowledge is in the file, not in your head.
• Composability. Skills can reference other skills. Your weekly planning skill can trigger meeting prep for every meeting on next week's calendar.

Five more skills you can build today

Now that you know the pattern, here are five more skills worth building:

• Content writer: Takes a topic and produces a draft in your brand voice, following your style guide and content calendar.
• Email triage: Reads your inbox, categorizes messages by urgency, drafts responses for routine items.
• Weekly review: Pulls data from your task list, calendar, and notes to generate a structured review of the past week and priorities for next week.
• Client onboarding: Takes new client details and produces a welcome email, project setup checklist, and kickoff agenda.
• Daily planner: Checks your calendar, tasks, and priorities to produce a focused plan for the day.

Each of these follows the same pattern: create a folder, write a SKILL.md with inputs, process, and output, then test and refine.

Going further: adding context and memory

A single skill is useful. A skill that reads your business context is powerful.

When you add a business context file (who you are, what you sell, who your clients are) and a memory file (facts Claude has learned over time), every skill benefits. Your meeting prep skill automatically knows your pricing, your services, and your relationship history with each client.

This is context engineering. The skill defines the process. The context files provide the knowledge. Together, they produce output that no generic AI tool can match because it is built on your specific business reality.

The AI OS Quick Start Guide walks through setting up context files alongside your first skill. It takes about 10 more minutes and makes a significant difference in output quality.

Ready-made skills you can use immediately

If building from scratch is not your style, the AI OS Blueprint includes five production-ready business skills: content writing, email triage, meeting prep, daily planning, and weekly reviews. Each one has been refined through real daily use. You clone the repository, fill in your business details, and they work.

Whether you build your own or start with ready-made ones, the key insight is the same: skills turn Claude Code from a tool you talk to into a system that works for you. And the first one takes 10 minutes to build.