Field Study

How to Make Your First Claude Cowork Skill

Build your own AI tool. No coding required. Just a clear idea and 60 minutes.

A Claude Cowork skill is the most powerful thing I’ve built with AI, and it doesn’t require a single line of code.

Here’s what it is: a saved set of instructions that tells Claude exactly how to do a specific job. You write the instructions once — in plain English — and then you can invoke it anytime with a single command.

I’ve built skills that run a 25-person advisory board, plan a week of social content, write client proposals from meeting notes, review websites with a 16-person creative panel, and prep my weekly family meeting agenda. Each one saves me hours every week.

The magic is in the prompt architecture — how you structure the instructions, what context you give Claude, how you define the output. It’s like writing a really good recipe. Anyone can follow it, and the result is consistent every time.

In a 1:1 session, we’ll build your first skill from scratch. You bring the use case — something you do repeatedly that you want to hand off to AI — and I’ll walk you through the entire process. You’ll leave with a working skill and the knowledge to build more on your own.

Intended Audience

This is for you if:

  • You use Claude Cowork and want to build custom skills for your specific workflows
  • You have a repeatable process you want to turn into a one-command AI tool
  • You're curious about building AI tools but don't know where to start
  • You want to create something you can share with your team or community
Curriculum

What you'll learn

Module A

What a Skill Actually Is

A skill is a saved set of instructions that tells Claude how to do a specific job. Think of it as a recipe — you write it once, then Claude follows it every time you invoke it.

Module B

Design Your Skill

Start with the outcome. What does your skill produce? A report? A plan? A piece of content? We'll map the inputs, process, and outputs before writing anything.

Module C

Write the Prompt Architecture

Learn the structure of a good skill file — the frontmatter, the trigger phrases, the instructions, the context gathering. No code, just clear writing.

Module D

Test, Iterate, Ship

Run your skill, see what works, fix what doesn't. The iteration loop is the same as vibe coding — describe, review, adjust, repeat.

Get Started

How it works

Start with a free chat — 20 minutes, no pitch, just figuring out if I can help. Or jump into a 1:1 session and we'll build something real in an hour.

Free

Free Chat

20 min$0

We talk. I learn what you need. You get honest advice. No pitch.

Book now Paid

1:1 Session

60 min$150–200

Hands-on session. You bring the goal, I bring Claude. You leave with something built.

Book now
FAQ

No. Skills are written in plain English with some structured formatting. If you can write a detailed email, you can write a skill.

I built a 25-person advisory board skill that gives me business advice from multiple expert perspectives. I built a content planning skill that creates a week of social posts. I built a proposal writer that turns meeting notes into client proposals. Anything you do repeatedly can be a skill.

That's up to you. Some people build skills for their own use. Some share them with teams. Some sell them as part of their services. You own what you build.

A simple skill takes 30-60 minutes. A complex one (like my advisory board) took a few hours over a couple of sessions. The first one is the hardest — after that, you'll crank them out.

Note

How to Talk to Robots

The newsletter. Weekly from Hazel. AI that makes sense. Marketing that doesn't suck.