---
title: "Install"
description: "Step by step install for a SKILL.md skill folder in Claude Code, Codex, Cursor, Lovable, Replit and v0, plus Claude Chat, Claude Cowork and ChatGPT."
url: "https://builderbooks.dev/install"
type: "guide"
site: "BuilderBooks.dev"
tools:
  - "Claude Code"
  - "Codex"
  - "Cursor"
  - "Lovable"
  - "Replit"
  - "v0"
  - "Claude Chat"
  - "Claude Cowork"
  - "ChatGPT Chat"
  - "ChatGPT Work"
---

# Install

A skill is a folder: SKILL.md plus reference files the agent loads when it needs them. Only Claude Code runs skills natively. Every other tool below uses the same files with a small manual step: usable, just not the same thing.

## Coding agents

### Claude Code

Recommended. Native skill support.

1. Unzip the folder
2. Move it into ~/.claude/skills/
3. Restart Claude Code
4. Type /command-name

```bash
unzip product-led-onboarding.zip -d ~/.claude/skills/
```

Skills in ~/.claude/skills/ are available in every project.

### Codex

OpenAI’s coding agent. No skill directory, it reads AGENTS.md.

1. Unzip the folder into the repo
2. Point AGENTS.md at the skill
3. Name the skill in your task

```bash
unzip product-led-onboarding.zip -d ./.agents/
echo "Follow ./.agents/product-led-onboarding/SKILL.md when working on onboarding." >> AGENTS.md
```

Codex loads AGENTS.md automatically, so one line in it makes the skill discoverable in every session of that repo. The reference files stay where they are, the agent opens them when it needs them.

[Open Codex](https://chatgpt.com/codex)

### Cursor

Per project, not global.

1. Unzip the folder
2. Copy SKILL.md into .cursor/rules/
3. Keep the reference files in the repo

```bash
mkdir -p .cursor/rules && cp product-led-onboarding/SKILL.md .cursor/rules/
```

**Note:** Rules live per project, so repeat this in every repo that needs the skill.

[Open Cursor](https://cursor.com)

### Lovable

Vibe-coding tool. Add the skill to the project context.

1. Unzip the folder
2. Open the project in Lovable
3. Drag SKILL.md and the reference files into the chat or project context
4. Reference the skill in your prompt

**Note:** Lovable has no global skill directory. The skill lives inside the project, so you must add it to each project that needs it.

[Open Lovable](https://lovable.dev)

### Replit

Agent + deployment. Load the skill as project context.

1. Unzip the folder
2. Upload the folder into your Replit project
3. Tell the Replit Agent to follow SKILL.md
4. Reference the skill in each new task

```bash
unzip product-led-onboarding.zip -d ./product-led-onboarding/
```

**Note:** Replit reads the skill as project files, not as a native rule. Keep the folder in the project root so the agent can find it.

[Open Replit](https://replit.com)

### v0

Vercel’s generative UI agent. The skill rides along as project files.

1. Unzip the folder
2. Open the project in v0
3. Attach SKILL.md and the reference files to the chat
4. Name the skill in the prompt for each new generation

**Note:** v0 has no skill directory either. The files live in the chat you attached them to, so a new chat needs them again.

[Open v0](https://v0.app)

## Other tools

### Claude Chat

Persistent across every conversation in a project.

1. Unzip the folder
2. Create a project in Claude
3. Upload SKILL.md and the reference files into the project knowledge
4. Ask for the skill by name in any chat inside that project

**Note:** The knowledge base caps out at 200K tokens. One project per skill works better than one project holding everything.

[Open Claude](https://claude.ai)

### Claude Cowork

Claude working on a shared folder of files, not a repo.

1. Unzip the folder
2. Put the skill folder in the workspace Claude has access to
3. Tell Claude to follow SKILL.md for this kind of task
4. Keep the reference files next to it, untouched

Cowork reads the folder like any other file in the workspace, so the whole skill, references included, stays available without pasting anything.

[Open Claude](https://claude.ai)

### ChatGPT Chat

Two options, one of them temporary.

1. Unzip the folder
2. Attach SKILL.md and the reference files to the conversation
3. Or build a Custom GPT and put the same files in its knowledge base
4. Reference the skill by name in your prompt

**Note:** An attachment only lasts for that conversation. The Custom GPT keeps the files, so use it for a skill you reach for often.

[Open ChatGPT](https://chatgpt.com)

### ChatGPT Work

The work surface with company files and connectors.

1. Unzip the folder
2. Upload the skill into the shared workspace files
3. Point the task at SKILL.md
4. Repeat for each workspace that needs it

**Note:** Shared files are visible to the workspace, so upload a skill your team is licensed to use, not one bought for a single seat.

[Open ChatGPT](https://chatgpt.com)

## When it doesn't work

### The skill doesn't show up in Claude Code

Two causes, in this order: the folder isn't directly inside ~/.claude/skills/, or Claude Code wasn't restarted after you moved it.

### The ZIP won't extract

Use the shell command above instead of the desktop unarchiver. The archive contains a folder, so it will never scatter files into your current directory.

### The download link is dead

Email links last seven days. Your bookshelf at /my-bookshelf doesn't expire, enter your purchase email and get a fresh link.

### The email never arrived

Same answer: /my-bookshelf delivers everything that email owns, again.

Wondering what SKILL.md is, where the format comes from and why a skill is a folder instead of a prompt? [The FAQ answers that](/faq).