Install your first employee

Time to hire. You take one skill from the library, put it in your project folder and run it on your own text. I use the hook writer for this guide. It writes five opening lines for a post.

Where employees live

A skill is a folder with one file inside called SKILL.md. That file holds the instructions for one job, in plain English.

Claude Code looks for skills in two places:

Place	Path	Works in
Your project	.claude/skills/<name>/SKILL.md inside your project folder	Only that project
Your computer	~/.claude/skills/<name>/SKILL.md in your home folder	Every project on this computer

For your first employee, use the project. Then the skill sits next to the business knowledge it reads. If the same skill exists in both places, the one in your home folder wins.

The .claude folder starts with a dot. Your Mac and Windows hide folders like that by default. In Finder, press Cmd + Shift + . to show them. In Windows File Explorer, turn on Hidden items under View. Or use the terminal commands below, which don’t care.

How Claude finds a skill

The top of every SKILL.md has a short header between two --- lines. It looks like this:

---
name: hook-writer
description: Writes five hook options for a post, based on the brief.
---

• name is the command you type, after a slash: /hook-writer. Without a name, Claude Code uses the folder name.
• description says what the skill does and when to use it. Claude reads it to decide when the skill fits your request.

So there are two ways to use a skill. Ask in normal words, like “write five hooks for this post”, and Claude picks the skill because the description matches. Or call it by name with /hook-writer. Calling it by name is the sure way. I do that while I learn a new skill.

Install the hook writer

The hook writer is BX-003. Comment or DM the keyword HOOKS to get it. You receive a zip file.

1. Unzip it. Double-click the zip. You get a folder BX-003-hook-writer with a README and a hook-writer folder that holds SKILL.md. Read the README first.
2. Make the skills folder. Open your terminal and go to your project. On a Mac:

cd ~/my-ai-company
mkdir -p .claude/skills

On Windows, in PowerShell:

cd $HOME\my-ai-company
mkdir .claude\skills

3. Move the folder in. Move only the hook-writer folder, not the folder around it. If it sits in your Downloads folder, on a Mac:

mv ~/Downloads/BX-003-hook-writer/hook-writer .claude/skills/

On Windows:

Move-Item $HOME\Downloads\BX-003-hook-writer\hook-writer .claude\skills\

Is the folder somewhere else, or named differently? Change the path in the command.

4. Check the result. You should now have this:

my-ai-company/
└── .claude/
    └── skills/
        └── hook-writer/
            └── SKILL.md

5. Open Claude Code. In the project folder, type claude. Then type / and look at the list. You should see hook-writer. You can also type /skills to see every skill Claude Code found.

Common mistake: one folder too many. Unzipping sometimes gives hook-writer/hook-writer/SKILL.md. Claude Code then finds nothing. SKILL.md must sit directly inside .claude/skills/hook-writer/.

Check: was Claude Code already running when you made the .claude/skills folder? Claude Code picks up new skills while it runs, but not a skills folder that did not exist when the session started. Type /reload-skills, or exit and start claude again.

Run it on your own text

Take a real post you plan to publish. Or a rough idea in three lines. Then call the skill and paste your text after it:

/hook-writer write five hooks for this post:

Most of my clients start yoga for their back. They sit all day.
In this post I show the one stretch I give every new client
before their first class.

That example comes from my fictional yoga studio, North Room, from the previous guide. Use your own text. The skill works best on a post you know well, because then you can judge the result.

If your Founder Brain is linked in CLAUDE.md, the hook writer reads your audience and your voice from there. Without it, the skill still writes hooks from your text alone, and the hooks sound more generic.

What you get back

Five hooks, numbered, each from a different angle. At least three of them are delta hooks. A delta hook has three parts:

Part	What it does	Example pattern
-100	Names the pain or the common belief your reader has	“Most founders write every caption from scratch.”
The turn	One word that flips it	“But”
+100	The promise: what works, or what they get	“you need one employee who knows your voice.”

The pain first, then the promise. The distance from -100 to +100 is what makes people stop scrolling. Under each delta hook the skill writes out the three parts, so you see how it is built.

The other hooks (two at most) use a different type, for variety.

How to judge the hooks

Don’t take the first one. Read all five out loud and check each one:

1. Is the -100 true for your reader? Would they say it in their own words? If it sounds like a complaint you made up, cut it.
2. Does the turn deny what is actually there? “But it’s not about more people” only works if the -100 talks about people. Otherwise the hook answers a question nobody asked.
3. Is the +100 concrete? A thing, a step, a number you can prove. Not “the secret to growth”.
4. Is it short? A spoken hook is about 15 words and two sentences at most.
5. Are there numbers you can’t back up? “73% of founders” without a source goes out.
6. Does it sound like you? Would you say it to one person across the table?

Pick one and edit it if you want. It’s your post. The skill gives you options, and you make the choice.

Common mistake: asking the skill to “make it more viral”. It then adds hype and invented numbers. Ask for something specific instead: “shorter”, “start with the pain from line two”, “no question marks”.

What to do next

One employee writes the opening. Two more finish the post.

Number	Employee	What it does	Keyword
BX-018	The caption writer	Writes the full caption under your chosen hook, in your voice, with one call to action	CAPTION
BX-004	The post reviewer	Checks your post against seven fixed rules and gives PASS or FIX per rule, with one suggestion. It never rewrites in secret.	CHECK

Install them the same way: one folder each in .claude/skills/. Then you have a small team: hook, caption, review. The reviewer is the step that turns three skills into an employee you can trust.

All three come together in the starter kit, with the Founder Brain template. Comment or DM START to get it.

Next

Want to know what is inside that SKILL.md, and how to write your own? Read The anatomy of a skill.