What Skills Are, and How to Make Them

If you've used AI for more than a month, you've felt this: you ask for the same thing twice and get two different answers. Different format, different sources, different tone. You spend the time you saved fixing it.

That's not the AI being bad. It's the AI guessing, because you never wrote down how you want the job done.

A skill fixes that.

What a skill is

A skill is a written procedure for a job you do more than once. It lives in a folder on your computer, and your AI loads it when that job comes up.

No code. It's a recipe card. The same thing you'd write for a new assistant on their first day.

Claude and Codex both support them. In Claude, each skill is a folder with one file called SKILL.md inside it.

What goes in one

Here's a real one, the Monday report I'd set up for most service businesses:

---
name: weekly-report
description: Build my Monday business report. Use when I say
  "weekly report", "Monday numbers" or "how did last week go".
---

# Weekly report

## What good looks like
One page. Top: three numbers that matter. Then what changed
and why. Then one decision I need to make.

## Steps
1. Pull last week's booked calls from my calendar.
2. Pull new leads from the inbox label "Leads".
3. Pull revenue from the "Revenue 2026" sheet in Drive.
4. Compare each to the week before.
5. Write it in my voice. Point form.

## Checks before you show me
- Every number says where it came from.
- If a source is missing, say so. Never guess a number.

## Never
- Never send it to anyone. Show me first.

Five parts:

• Description. The words you actually say. This is how the AI knows when to use it, so it matters most.
• What good looks like. The finished result, described plainly.
• Steps. In order.
• Checks. What it verifies before showing you.
• Never. The lines it doesn't cross.

How to make your first one

Don't write it from scratch. Do the job once, then turn it into a skill.

1. Do it once. Do the real job with your AI, in the chat. Your actual weekly report.
2. Fix it. Correct it until it's what you'd actually use.
3. Save it. Say: "Turn what we just did into a skill. Include the steps, what good looks like, the checks, and anything I corrected."
4. Run it. Next week, one line: "Weekly report."
5. Improve it. When it's off, fix it and say "update the skill."

That last step is the whole game. Every correction goes into the skill, so it gets better every week instead of making the same mistake forever.

What makes a good skill

• Specific. "Follow up with leads who didn't book" beats "help with sales."
• Repeated. Weekly or more. A once-a-year job isn't worth it.
• Checkable. You can look at the output and know if it's right.
• Safe by default. It drafts and shows you. It doesn't send, pay or delete without asking.

Run a new skill with you watching for two or three weeks before you let it do anything on its own. Same as a new hire.

Five to start with

Once your email, calendar, call notes and task manager are connected, these are the five I'd set up first. Four each do one job. The fifth ties them together.

1. Inbox triage. Every email gets one of four states. New stays in the inbox. Open means you owe them something, and a task exists for it. Pending means you're waiting on them, chased after three business days. Resolved gets filed. It goes one email at a time with a recommendation, and replies are drafts you send.
2. After the call. It reads your Fathom recording or Wispr Flow notes and gives you a five-line summary, the action items on both sides, tasks in your task manager (ClickUp, Trello, Asana, Notion or your own list) once you approve them, and a follow-up email drafted in your voice.
3. Call prep. Half a page on everyone you're meeting today: the last emails, past call notes, what's still open, and two questions worth asking.
4. Weekly review. Your three numbers against last week, what closed, what slipped, and one decision to make.
5. Blitz. One door into your week. Say "blitz" and pick: plan my week (the review, then your real capacity against what's due), start my day (inbox to zero, calls prepped, today's three things), work the queue (one task at a time, with a recommendation on each), or just capacity (before you say yes to something new).

The routine

Once they're in, your week runs on four sentences:

• Sunday night: "Blitz, plan my week."
• Every morning: "Blitz, start my day."
• After every call: "Process my last call."
• Any gap: "Blitz, work the queue."

Setting them up

1. Connect first. Gmail, Google Calendar, Fathom or Wispr Flow, and your task manager if it has a connector.
2. Install the five. Each one is a single SKILL.md file.
3. Fill in your setup. Which task manager, which call recorder, your three numbers. Then create three Gmail labels: 01 Open, 02 Pending, 03 Resolved.
4. Run each one with you watching for the first week. Every time it's off, fix it and say "update the skill."

Skills plus memory

Skills are what your AI knows how to do. Memory is what it knows about you: your business, your people, how you write. Put them together and it stops feeling like a tool and starts feeling like someone who works for you.

That's what I put in the AI OS Starter Kit: all five of these skills ready to install, the memory kit, the setup guide you hand to your AI, and a 30-day plan. If you'd rather start free, the setup guide gets you the foundation. Then make your first skill this week.