Build Your First Claude Code Skill in One Hour (Even If You Don't Code)

Claude Code skills are the single most underrated AI feature of 2026, and the reason is simple: they sound technical. The word "skill" implies code, terminals, configuration files, things solopreneurs back away from.

Here's the truth: a Claude Code skill is just a folder with a markdown file in it. The markdown file tells Claude what to do. That's it. Once you've set it up once, you have a custom command you can run forever, that does any task you can describe in English.

This is the walkthrough I use to take a non-technical person from "I've never touched the terminal" to "I have a working skill that runs on my computer" in about an hour. We'll build a real skill — a "draft my client follow-up email" command — that you'll actually use after this post.

What You'll Need

A Mac running macOS Ventura or newer (Linux/Windows works too but the setup is slightly different)
A Claude account (free tier is enough)
About 60 minutes
Willingness to type four commands into Terminal

That's it. No coding required. We'll write some configuration text but you don't need to know what any of it does — you'll just paste and adjust.

Step 1: Install Claude Code (10 minutes)

Open Terminal. (Cmd-Space, type "Terminal", hit Return.)

Paste this command:

curl -fsSL https://claude.ai/install.sh | sh

It downloads, asks you to log in by opening a browser tab, and you're done. Run claude --version to confirm. You should see something like claude-code 2.x.x.

If you hit any "command not found" errors, your shell PATH needs updating. The installer prints instructions; follow them and reopen Terminal.

Step 2: Find Your Skills Folder (2 minutes)

Run:

mkdir -p ~/.claude/skills/follow-up-email
cd ~/.claude/skills/follow-up-email

This creates a folder called follow-up-email in your skills directory. Every skill is its own folder. Naming convention: lowercase, hyphens, no spaces.

Step 3: Write the Skill (15 minutes)

A skill needs one file: SKILL.md. Let's write it.

Run:

nano SKILL.md

Paste this template:

---
name: follow-up-email
description: Drafts a personalized follow-up email to a client based on the last email in the conversation and your notes about what to say next. Use when the user asks to follow up with someone or send a check-in.
---

# Client Follow-Up Email Skill

## When to use this skill
- The user asks to draft a follow-up email
- The user wants to check in on a stalled conversation
- The user mentions a client name and wants to write to them

## What to do

When invoked, you should:

1. Ask the user to paste the last email in the thread (or summarize it).
2. Ask what specifically they want to say in the follow-up. Possible angles:
   - Status check
   - New information or proposal
   - Gentle nudge after silence
   - Wrap-up before a deadline

3. Draft the email under these constraints:
   - Plain text, under 90 words
   - Open with one specific reference to the previous thread (no generic "Hope you're doing well")
   - One clear ask or next step
   - No exclamation points
   - Sign off with just "— Pete" (the user's name)

4. After drafting, ask if the user wants the model to:
   - Make it shorter
   - Make it more direct
   - Make it warmer
   - Send it as-is (just give them the final text to paste)

## Style notes

- Match the tone of the previous email in the thread. If the client wrote casually, write casually. If formally, formally.
- Avoid corporate verbs: leverage, navigate, circle back, touch base, ping.
- If the client hasn't replied in over two weeks, the email needs to acknowledge that without making it awkward.

Save and exit nano (Ctrl-X, then Y, then Return).

A few notes on what's in there:

The frontmatter name and description — Claude reads the description to decide when to invoke this skill. Be specific about when it applies.
The body — written in your voice, telling Claude exactly how you want it to behave. The more specific, the better the output.
The constraints (90 words, no exclamation points, sign-off) — these are what make the output feel like you wrote it.

You can edit this file any time. Skills are not compiled — they're just markdown that Claude re-reads on every invocation.

Step 4: Test It (10 minutes)

Open Claude in the app or web. In a new chat, type:

Use the follow-up-email skill to help me draft a check-in to a client
who hasn't replied in 10 days about a $4,000 web design project.

Claude should activate the skill and walk you through the questions you put in SKILL.md. Answer them. You'll get a draft.

If the draft is wrong, the fix is almost always in the skill itself. Edit SKILL.md, save, and try again. No restart needed.

Step 5: Make It Yours (15 minutes)

Now go back to SKILL.md and adapt it to your real workflow:

Change the constraints to match your actual email style (word count, sign-off, tone)
Add a Style notes section with phrases you actually use ("looking forward to hearing from you", or "talk soon", or whatever)
Add a Forbidden words section if there are corporate cliches you ban from your writing

Then save it. The next time you ask Claude to draft a follow-up, the output will sound dramatically more like you.

What to Build Next

Once the first skill works, you'll see the pattern. Almost any recurring writing task or research task you do can become a skill. Some I've built and use weekly:

weekly-newsletter — drafts a 6-section weekly digest from a list of links I drop in
proposal-from-call-notes — turns a transcript or notes into a structured client proposal
competitor-audit — given a URL, returns a structured comparison with our positioning
invoice-reminder — drafts a "your invoice is past due" email with the exact tone I use

Each one takes 30-60 minutes to build the first time. After that, it's free leverage forever.

For a more ambitious starter, try our free CEO Briefing Blueprint. It's a fully-built Claude Code skill that emails you a daily executive briefing at 8am. Use it as a template — fork the folder, change the prompt, you have a custom briefing skill in 30 minutes.

The Real Insight

Most "AI productivity" advice tells you to write better prompts. Claude Code skills are the next level: you write the prompt once, save it, and run it forever. Every skill is a piece of compound interest. The investment is one hour. The return is every future invocation, free.

Build one this afternoon. Pick the most boring recurring writing task you do. Make it a skill. By next week you'll have three more.