Skills
Package recurring instructions, steps, and reference material into skills that multiple agents can reuse.
A skill is a reusable set of working methods in a workspace. Its main file is SKILL.md, optionally accompanied by scripts, templates, and reference material.
Add a skill to an agent and the agent uses its guidance when executing related tasks. The same method no longer has to be copied into each agent's instructions, and updates are maintained in one place.
Skills and agent instructions
| Agent instructions | Skill | |
|---|---|---|
| Best for | This agent's long-lived responsibilities, boundaries, and delivery requirements | Reusable steps, material, and tools for one kind of work |
| Scope | Belongs to one agent and is provided on every run | Can be added to multiple agents and enabled or disabled individually |
| Example | "Only review frontend code, never modify it directly" | An accessibility checklist and report template |
Creating or importing a skill
On the workspace Skills page, choose "New skill". Three options are available:
| Option | When it fits |
|---|---|
| Create manually | Start writing from a blank SKILL.md. |
| Import from URL | Import a published skill from GitHub, ClawHub, or Skills.sh. |
| Copy from a runtime | Scan skills on a connected computer and copy the selected ones into the workspace. |
Copying from a runtime takes a snapshot of the files at that moment. Later changes to the local files do not update the workspace version automatically; re-import or edit in Kolleague.
With the CLI, you can also import from a .skill or .zip file:
kolleague skill import --file ./review-helper.skillIf a skill with the same name already exists in the workspace, the import can stop, overwrite the existing content, save under a new name, or skip. Overwriting through import is limited to the skill's creator; a workspace admin who can edit the skill in the app still cannot overwrite it via import.
Skill contents
Every skill contains a main file, SKILL.md. Spell out:
- when the skill applies;
- what to check before starting;
- the steps to execute;
- what form the result should take;
- when to stop and check with a member.
You can also add supporting files, for example:
SKILL.md
references/api-conventions.md
templates/review-report.md
scripts/check.shSKILL.md is a reserved path; a supporting file cannot use that name. Supporting files are delivered to the agent together with the main file.
Attaching to an agent
After creating or importing a skill, it still needs to be added to specific agents. Pick agents on the skill page, or manage bindings from the agent's Skills tab.
- One agent can use multiple skills;
- one skill can serve multiple agents;
- when a skill isn't needed for now, disable the binding instead of deleting the skill;
- edits take effect from subsequent runs and don't change tasks already running.
Only members who can modify the agent can add, remove, or disable its skills.
Workspace skills and repository skills
Workspace skills are stored in Kolleague — a fit for skills the team maintains together and adds to different agents.
Some AI coding tools also read project-level skills directly from the code repository, such as .claude/skills/ or .agents/skills/. Those files stay managed by the repository; Kolleague does not automatically register them as workspace skills. Support depends on the tool in use — see AI coding tools comparison.
Runtime-local skills already installed on a connected computer (Claude Code and Codex) show up in the agent's Skills tab and can be disabled per agent. Disabling likewise requires permission to modify the agent.
Edit permissions
Any workspace member can create or import a skill. The creator and workspace owners and admins can modify or delete it; other members can view and use it, but cannot overwrite its content.
Deletion is permanent and removes the skill from all agents at the same time.
Skills imported from external sources may contain scripts, commands, or unsafe instructions. Kolleague does not review, sign, or sandbox them for you. Imported content is handed to agents as-is, so the source needs to be trusted.
Next steps
- Squads — let a leader pick the right member for the work.
- Daemon and runtimes — how skills reach the actual execution environment.
- AI coding tools comparison — how different tools support skills.