# Claude how to use skills: turn them on, build one, use in Code

> Skills need code execution turned on. Then you toggle them in Customize > Skills, upload your own as a ZIP, or drop a SKILL.md into a folder in Claude Code.

URL: https://claudegpt.si/news/claude-how-to-use-skills  
Published: 2026-10-31T22:52:07.582Z  
Author: ClaudeGPT Si Newsroom  
Section: Guides  
Topics: Claude, Claude Code, How to, Anthropic, AI agents  
Publisher: ClaudeGPT Si

## Key takeaways

- Skills work on Free, Pro, Max, Ultra, Team and Enterprise plans, but code execution must be enabled first.
- A custom skill is a folder with a skill.md file whose name and description frontmatter tell Claude when to use it, zipped and uploaded in Customize > Skills.
- In Claude Code, a skill is a SKILL.md in ~/.claude/skills/<name>/ or .claude/skills/<name>/, started by Claude or by typing /skill-name.

To use skills in Claude, turn on code execution, open Customize > Skills and switch on the skills you want. Claude then loads a skill on its own when your request matches it, as described in Anthropic's [help center article on using skills](https://support.claude.com/en/articles/12512180-using-skills-in-claude). This guide covers how to enable skills, how to build and upload your own, and how to use them in Claude Code. Details are as of October 31, 2026.

A skill is a folder of instructions, and sometimes scripts, that teaches Claude one repeatable task. It is for anyone who keeps pasting the same checklist into a chat. When you finish, you will have a skill switched on, and a custom one if you want it.

## What you need first

Skills are available on the Free, Pro, Max, Ultra, Team and Enterprise plans. They also work in Claude Code, and in beta for API users through the code execution tool.

Code execution has to be on. On individual plans, find it under Settings > Capabilities, where newer layouts call it "Create and edit files". On Team, skills are on by default for the organization. On Enterprise, an owner must enable both code execution and Skills under Organization settings > Plugins & skills, in the Policy tab. If the Skills section is missing or greyed out, code execution is almost always the reason.

## How to turn on skills in Claude

1. Enable code execution as described above.
2. Go to Customize > Skills.
3. Toggle each skill on or off.

Anthropic's built-in skills for Excel, Word, PowerPoint and PDF are included for everyone. With code execution and file creation on, Claude uses them automatically when they fit, so you don't have to call them by name. Disabled skills are unavailable to Claude.

If Claude ignores a skill, check that it is toggled on, then check that its description says clearly when to use it. You can also name the skill in your prompt. Enabled skills also work in the Claude add-ins for Excel, PowerPoint, Word and Outlook, where you can type `/` in the sidebar to pick one.

## How to create a skill

Each skill is a directory with at least a `skill.md` file, per the [help center guide to creating custom skills](https://support.claude.com/en/articles/12512198-how-to-create-custom-skills). The file starts with YAML frontmatter that has two required fields: `name`, up to 64 characters, and `description`, up to 200 characters. The description matters most, because Claude reads it to decide whether the skill applies. Claude reads the body of the file only if it needs it.

Anthropic's own example is a brand guidelines skill, with sections for an overview, colors, typography, logo usage, when to apply it and resources. Put extra material, such as a `REFERENCE.md`, in the same folder and mention it from `skill.md` so Claude knows when to open it.

A skill can also bundle scripts. Claude and Claude Code can install packages from PyPI and npm when loading a skill. Skills used through the API cannot, so every dependency there must already be in the container.

## How to upload a skill

1. Name the folder the same as the skill's `name`.
2. Zip the folder so the folder itself is the root of the archive. Loose files at the root of the ZIP are wrong.
3. In Customize > Skills, click "+", then "+ Create skill", then "Upload a skill", and pick the ZIP.
4. Toggle the skill on.

Custom skills are private to you until you share them. Uploads fail when the ZIP is too large, the folder name does not match the skill name, `skill.md` is missing, or the name or description contains invalid characters.

On Claude for Mac, Cowork can also record a skill. It is available on Pro, Max, Ultra and Team, and it captures your screen and voice for up to about 10 minutes. Claude then proposes a skill from the recording. Don't type passwords or show private conversations while recording.

## Test the skill

Before uploading, reread `skill.md` and confirm every file it references exists. After uploading, try several prompts that should trigger it. Anthropic suggests checking Claude's thinking to confirm the skill loaded, and tightening the description if it did not.

In chat, you can highlight text in a skill file and click "Edit with Claude". For skills with several files, send your edit requests together so Claude applies them in one pass.

## How to use skills in Claude Code

Claude Code reads skills from folders, per the [Claude Code skills docs](https://code.claude.com/docs/en/skills). The file is `SKILL.md`, and every frontmatter field is optional, though `description` is recommended.

| Scope | Path |
| --- | --- |
| Personal | `~/.claude/skills/<name>/SKILL.md` |
| Project | `.claude/skills/<name>/SKILL.md`, committed to share with a team |
| Plugin | `<plugin>/skills/<name>/SKILL.md` |
| Enterprise | `.claude/skills/` in the managed settings directory |

Here is the docs' quick example. Save it as `~/.claude/skills/summarize-changes/SKILL.md`:

```yaml
---
description: Summarizes uncommitted changes and flags anything risky. Use when the user asks what changed, wants a commit message, or asks to review their diff.
---

## Current changes

!`git diff HEAD`

## Instructions

Summarize the changes above in two or three bullet points, then list any risks you notice.
```

Ask "What did I change?" and Claude loads it, or run `/summarize-changes` yourself. The line starting with `!` runs the command and puts its output into the skill before Claude sees it. Keep `SKILL.md` under 500 lines, and use `$ARGUMENTS` to pass arguments into the skill.

Two frontmatter fields control who can start a skill. Set `disable-model-invocation: true` for something like `/deploy`, so only you can run it. Set `user-invocable: false` to hide it from the `/` menu so only Claude uses it. Skills you enabled on claude.ai also appear under "claude.ai sync" in `/skills` on Claude Code v2.1.273 or later. That sync is one-way and does not run when you sign in with an API key or a cloud provider.

## Common problems

- Claude does not use the skill. Make the description name the phrases people really say, and check the frontmatter starts on the first line of the file. Misspelled fields are silently ignored.
- The skill is missing from the `/` menu. The name may contain refused characters such as `<` or `>`. Run `claude --debug` and search for `[names]`.
- A new skills folder is not picked up. Edits to `SKILL.md` reload live, but a new top-level skills directory needs `/reload-skills`.
- Claude stops following the skill later in a session. The skill is added to the conversation once and not re-read. Word standing rules for the whole task, or move must-run rules into a hook.
- Descriptions get cut off when you have many skills. Run `/doctor` to see the cost.

## Stay safe with skills

Skills can run code, so Anthropic advises installing them only from trusted sources. Read the bundled scripts and dependencies of any skill from a less-trusted source, including a colleague's, before enabling it. Never hardcode API keys or passwords in one. Anthropic's [example skills repository](https://github.com/anthropics/skills) is a good place to start from a template.

## Where to go next

Start with one small skill for a task you repeat weekly. Then read Anthropic's skill authoring best practices and the Agent Skills specification at agentskills.io if you want your skill to work across products.

## Frequently asked questions

### How do I create a skill in Claude?

Make a folder with a skill.md file that starts with name and description frontmatter, zip the folder, then upload it under Customize > Skills. Toggle it on and test it with a few prompts.

### Why is the Skills section missing in Claude?

Code execution is not enabled. Turn it on in Settings > Capabilities, or ask an organization owner to enable it in the Policy tab on Team and Enterprise.

### Where do Claude Code skills live?

Personal skills go in ~/.claude/skills/<name>/SKILL.md and project skills in .claude/skills/<name>/SKILL.md. Plugins and managed settings can also provide skills.

### Why does Claude not use my skill?

Check that the skill is toggled on and that its description clearly says when to use it. You can also name the skill in your prompt.

## Sources

- [Using Skills in Claude](https://support.claude.com/en/articles/12512180-using-skills-in-claude), Anthropic
- [How to create custom Skills](https://support.claude.com/en/articles/12512198-how-to-create-custom-skills), Anthropic
- [Extend Claude with skills](https://code.claude.com/docs/en/skills), Anthropic