Skills are reusable playbooks for agents. A skill packages the instructions, templates, and integrations needed for a kind of work, so the next agent doesn't start from a blank prompt.
You'll find them under Skills in the left icon strip.
Browse skills
The Skills page lists:
- Builtin skills that ship with Kluff
- Workspace skills your team created or forked
Open a skill to read what it's for and when to use it. From an agent thread, you can also load a skill when the task matches.
Create, fork, and edit
Workspace admins and people with the right permission can:
- Fork a builtin skill to customize it for your company without losing the original.
- Create a skill from scratch when you have a workflow that's yours alone.
- Edit a workspace skill as the process changes. The point of a skill is that you update it once.
A good skill is specific: “qualify inbound demos from the CRM and draft the follow-up” beats “be helpful with sales.” Point it at the integrations it should use and the tone it should write in.
Skills vs integrations vs flows
| Piece | Role |
|---|---|
| Integration | A connected app (GitHub, HubSpot, Slack, …) |
| Skill | How an agent should use those apps for a repeatable job |
| Flow | A visual workflow you run by hand or on a schedule, not only inside a chat |
Use a skill when a human is chatting with an agent and you want consistent behavior. Use a flow when the work should run as a pipeline even if nobody is in the thread.
Using a skill in a conversation
In an agent thread, load the skill that matches the job (or mention it in your first message). The agent then follows that skill's instructions and tools for the rest of the task. If it needs extra access, it will still respect the project's tool settings and approvals.

