Add skills to a project's agents
A skill is a short set of instructions an agent loads when a job calls for it, such as how your team writes release notes or the checklist for a code review. There is no place in the console to upload a skill. Skills live in the project's repository, and the agents that work on the project read them from there.
Who can do this: anyone who can change the project's repository, or start tasks on the project.
Add a skillโ
Agents that run on Claude Code load the skills in the repository's Claude Code folder by themselves. Each skill is a folder holding one file named SKILL.md:
.claude/
skills/
release-notes/
SKILL.md
SKILL.md starts with the skill's name and a description that says what it does and when to use it, then the instructions:
---
name: release-notes
description: Use when writing release notes for a version, to follow our format and tone.
---
1. List each change under Added, Changed or Fixed.
2. Write for customers, not engineers.
- Add the folder and its SKILL.md to the repository. You can commit it yourself, or start a task that asks an agent to write the skill and describes what it should say.
- Merge it into the project's integration branch. Tasks that start after the merge have it; a task already running keeps what it started with.
- Name the skill in the project's Agent instructions, so agents other than Claude Code find it too: for example, "For release notes, follow the release-notes skill in the repository." See Tell runners about a project.
A business projectโ
On a business project, the Business Wizard writes skills for you: it interviews you about one business activity and records it in the project with a skill for each recurring job. It keeps them in a skills folder at the top of the repository and lists each one in the project's agent instructions file, which every agent reads first, so any agent finds them there. See Choose a persona for a task.
What you can't doโ
- Add a skill to an agent in the console, or to every project at once. Each repository carries its own skills.
- Give skills to a project with no repository. Write the instructions in its Agent instructions instead.
Other ways to shape what agents do:
- Standing instructions for every task on a project: Tell runners about a project.
- Instructions for one stage of a playbook: Add instructions to a playbook stage.
- A tool the agents can call, such as a service's own server: Give a project's agents an MCP server.
- An agent of your own, built with the Jaah Agent SDK: Build an agent with the SDK.