> ## Documentation Index
> Fetch the complete documentation index at: https://sleekplan.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Skills
> Write down how a task should be done once. Sleekmate follows it whenever it applies, and your connected MCP clients can load it too.
A **skill** is a set of instructions you write once: how to triage a bug, how to write a weekly review, which tone your changelog uses. Sleekmate follows it whenever your request matches, and MCP clients you've connected to your workspace, like Claude or Cursor, can load it too.
Go to [**Settings → My Account → Skills**](https://app.sleekplan.com/settings/skills). **Owner**, **Admin**, and **Member** can all create and use skills. It isn't restricted to any one role.
## Create a skill
Go to [**Settings → My Account → Skills**](https://app.sleekplan.com/settings/skills) and click **New skill**.
Give it a short, descriptive name, for example "Triage new bug reports".
This description is what Sleekmate and your MCP clients read to decide whether the skill applies to a request, so be specific about the trigger, not just the topic.
Bad: "Feedback helper". Good: "Use when someone asks for a weekly recap of new feedback: group it into themes and end with one recommendation."
Add the steps, rules, or examples to follow. Markdown works.
Owners and admins can turn on **Share with workspace** to make the skill visible to everyone. Leave it off to keep it private to you.
Click **Create skill**. It's ready right away, including in a Sleekmate conversation you already have open.
## Limits
A skill has a **name** (up to 100 characters), a **description** (up to 1,024 characters), and **instructions** (up to 50,000 characters). Each person can save up to 50 skills per workspace.
## Sharing skills with your team
Skills are private by default. Owners and admins can turn on **Share with workspace** for any skill they wrote. A shared skill appears in everyone's list, marked **Shared** and labeled with who wrote it. Everyone can read and use it, but only the author can edit or delete it.
If the author of a shared skill leaves the workspace, or their seat is deactivated, the skill stays on this page, but Sleekmate and your MCP clients stop using it.
## How Sleekmate and your MCP clients use skills
**Sleekmate** reads the name and description of every skill you can see on each message you send, and loads the full instructions for the one that matches what you're asking. A new skill, or a change to one, applies from your very next message, even in a conversation you already have open.
**MCP clients** you've connected, like Claude or Cursor, get the same skills over the [Sleekplan MCP server](https://sleekplan.com/docs/mcp-server): the client lists what's available and reads the one it needs, the same way it reads your feedback or changelog. When you ask, they can save or update your skills too. See the MCP server's developer page for the technical details.
## Let Sleekmate write a skill for you
When you have worked through a task with Sleekmate, ask it to keep the approach, for example "Save how we did this as a skill." Sleekmate writes a name, a description and step-by-step instructions from your conversation, then shows them on an [approval card](/help/sleek-intelligence/sleekmate#approving-its-actions) before saving. With **Yolo mode** on, it saves right away.
After a longer task, Sleekmate may offer to save it as a skill. It never saves or changes one without you asking or agreeing. You can ask it to change one of your own skills the same way: it reads the current version first and keeps what you didn't ask to change. A skill Sleekmate saves is private to you; deleting and sharing it stay on the Skills page.
## Related
Your in-app copilot, and the main place skills are put to work.
What owners, admins, and members can each do.
Connect Claude, Cursor, and other AI clients to your workspace.