Skill
A Skill is a Markdown file that teaches the Agent how to complete specific tasks. Think of it as a "work manual" — once you define the standards and steps, the Agent will automatically apply them in the right scenarios, making repetitive work standardized and reusable.
Type @ in the chat input to bring up the Skill list. After selecting one, the Agent will work according to the patterns defined in that Skill:
Managing Skills
In the Agents Settings > Skills panel, you can view all installed Skills, including manually created User Skills and Plugin Skills installed via plugins.
- Use the toggle switch to enable or disable a Skill
- Click the edit icon to modify Skill content
- Click the delete icon to remove a Skill
- Click Open Folder to open the Skill file directory directly
Skill Types
| Type | Storage Location | Scope |
|---|---|---|
| User Skills | ~/.claude/skills/ | Available across all projects |
| Plugin Skills | Provided by plugins | Automatically available after plugin installation |
| Project Skills | Project's .claude/skills/ | Only effective in the current project |
Creating a Skill
Click + Add User Skill to enter the creation interface with three fields:
| Field | Required | Description |
|---|---|---|
| Name | Required | Unique identifier for the Skill, used for matching and invocation (e.g., explaining-code) |
| Description | Required | Brief summary of purpose and trigger scenarios — Agent auto-matches your requests based on this |
| Details | Required | Complete instructions written in Markdown, defining specific work standards and steps |
Tip: The more precise your description, the better the Agent's auto-matching. Include key trigger phrases like "when users ask how code works".
Editing a Skill
Click the edit icon on an existing Skill to enter the editing interface. You can modify the name, description, and details, or click Edit in VSCode to open the full Markdown file for more detailed editing.
Configuration File Structure
A Skill is essentially a Markdown file with YAML frontmatter and body instructions:
---
name: explaining-code
description: Explain code with visual diagrams and analogies
---
# Code Explanation Standards
When explaining code, always include:
1. **Start with analogies**: Compare code to everyday things
2. **Visual diagrams**: Use ASCII diagrams to show flow
3. **Step-by-step breakdown**: Clearly explain each part
Reference File Support
You can place reference documents in the Skill directory. The Agent only reads them when needed, avoiding unnecessary context consumption:
my-api-guide/
├── SKILL.md # Core instructions
├── api-reference.md # Detailed API documentation
└── examples.md # Usage examples
Usage Methods
| Method | Description |
|---|---|
| Auto-trigger | When your request matches a Skill description, the Agent will ask whether to use it |
| Manual invocation | Type @ in the chat input and select from the Skill list |
FAQ
What's the difference between Plugin Skill and User Skill?
Plugin Skills are provided by plugins and automatically available after installation. User Skills are manually created by you and can be fully customized. If both share the same name, User Skill takes priority.
Can Skills contain code scripts?
Yes. Skills can contain scripts in Python, Node.js, or any other language. The Agent can execute these scripts, and only the script output consumes context, not the script content itself.
How do I share Skills with my team?
Two ways:
- Create a Project Skill and commit it to the repository — team members automatically get it after cloning
- Share the User Skill folder with the team — they copy it to
~/.claude/skills/