Install the Unstoppable Skills

Video coming soon

Lesson notes and steps

The written version of this session, with the commands and templates to copy.

This one is written rather than filmed, because it is six minutes of copying a folder and you would rather read it than watch it. At the end, your agent has a set of written methods it follows on command: a full pre-ship review, a design pass, a debugging method that stops the guessing, and a landing page builder.

What a skill actually is

A skill is one folder with one file in it, called SKILL.md. The file is plain writing: what to check, in what order, what to show you, and what it is not allowed to claim without evidence. Claude Code reads it and follows it.

That is the whole trick. You are not installing software. You are handing your agent a method, in writing, that it did not have to invent while you were waiting.

Step 1: Get the files

Open the skills page, signed in. You will see the ones that are yours: four with a free account, eleven with a plan.

Take the whole pack as a zip, or take them one at a time. The zip already has the right shape inside it, which saves a step.

Step 2: Decide where they live

Two choices, and the difference matters.

• ~/.claude/skills/ puts a skill on this computer, for everything you build.
• .claude/skills/ inside one project puts it in that project only.

Start with the first one. Use the second when a skill is about one client or one codebase and would be noise everywhere else.

Step 3: Copy the folder in

One folder per skill, and the folder name is the command name. So the ship review skill ends up at ~/.claude/skills/ship-review/SKILL.md.

If you took the zip, unzip it and move the inner folders across. If you took a single file, make the folder first and rename the file to SKILL.md as you move it.

Step 4: Use it

Start Claude Code in the folder you want to work in, then type the name with a slash in front:

/ship-review

Your agent opens the file and follows it. You do not have to remember what is in it, and neither does the agent.

Step 5: Check it took

Ask your agent to list the skills it can see. If yours is not there, it is almost always one of three things: the folder is nested one level too deep, the file is not named SKILL.md, or Claude Code was already running when you copied it in. Restart it.

Which four are free

• Ship review. Eight reviewers go through your work, every finding gets checked against your actual code, and it ends in one line: go, or no-go.
• Make it beautiful. Audits the design, shows you two or three directions as real mockups, and applies the one you pick.
• Debug like a pro. Reproduces the bug and names the cause before it changes a line, instead of trying four fixes in a row.
• Landing page in one command. A paragraph about your business becomes a page that is live, with the form wired up and the launch check run.

The other seven come with a plan: security, QA, launch, data safety, copy, brand, and a whole app in an afternoon.

One habit to keep

Leave the approval prompts on, and read what the agent is about to run before you approve it. These skills make your agent more capable, which makes what it can run in one step larger. Never grant blanket approval for a whole session, especially when an email, a downloaded file, or a web page is anywhere in the conversation: an instruction hidden inside outside content is aimed at your agent, not at you.

Members share their results from this session in the community. See what is included.