ClickUp Skills: Teach AI to Follow Your Team's Workflow

"Use our format." "Keep it in our tone." "Pull from the Q4 list, not the old one." If that sounds like your last week with AI, the problem isn't the model. It's that the AI forgets how your team works the moment the chat ends. ClickUp Skills fix exactly that.

A Skill is a saved playbook: the steps, context and style for one kind of work, written once and reused forever. In this guide we cover what ClickUp Skills are, how they differ from saved prompts, the first Skills we build for client teams, and how to roll them out without creating chaos.

What are ClickUp Skills?

ClickUp Skills are saved instructions that ClickUp Brain and Super Agents follow whenever a request matches. You define how a task should be done (the steps, the structure, the tone, what "finished" looks like) and the AI applies it automatically or when you call it on demand.

ClickUp describes a Skill as a saved playbook, and that's the right mental model. Think of the onboarding checklist your best ops lead runs from memory, or the 12 things your agency checks before sending creative to a client. Today that knowledge lives in one person's head. As a Skill, it lives in the workspace.

All Skills live in the Skills Hub, which you open from Skills in the Home Sidebar or from the AI Hub. An admin needs to turn on the Custom Skills ClickApp first. Each Skill also gets its own /slash command, so anyone with access can trigger it from any text area where Brain is available. You can read ClickUp's own overview on the official Skills page.

ClickUp Skills vs saved prompts: which do you need?

ClickUp already had saved prompts, so it's fair to ask why Skills exist. The difference is who has to remember. A saved prompt is text you drop into a chat and send yourself. A Skill is a set of instructions Brain and Super Agents can apply on their own whenever it's relevant.

Prompts are great for one person who wants full control each time. ClickUp Skills win when the same output has to look the same no matter who asks. Not sure which one your workflow needs? Run it through the quick check below.

How much time does re-explaining your workflow cost?

The hidden cost of AI without ClickUp Skills isn't the typing. It's the context you re-explain, the output you reformat, and the inconsistency someone has to fix before a client sees it. Plug in your own numbers to estimate it.

Even small numbers add up. Five people losing four minutes six times a week is a full working day every month, and that's before counting the reports that went out in three different formats.

How to create ClickUp Skills in under a minute

You don't write code or fill in a form. You describe the workflow to Brain and it drafts the Skill with you. There are four ways in:

1. From scratch. Open the Skills Hub, click + New Skill, and tell Brain in the sidebar what the Skill should do. Be specific about steps, context and tone, answer its follow-up questions, then review.
2. From a template. Click a template card at the top of the Hub. Persona templates like Write Like Me or Update Like Me scan your activity to match how you already write or report status.
3. From anywhere. In any Brain chat, say you want to create a Skill and describe it. No need to leave the task or Doc you're in.
4. With Skills Miner. Click Find my Skills. Brain scans your tasks, Docs and chats for workflows you repeat and suggests ones worth saving. This is the best starting point if you're not sure what to build.

Once it's saved, you can attach reference files (a brand guide, a report template) and link related Skills so one can build on another. ClickUp's Brain² launch post explains the wider AI upgrade Skills sit on top of.

4 ClickUp Skills worth building first

When we set up ClickUp Skills for client teams, we skip the clever stuff and start with the work people repeat every single week. These four pay off fastest. Pick your role to see where to start.

Notice what these have in common: each has a clear trigger, a fixed output and a real cost when it goes wrong. That's the pattern to look for in your own workspace.

Writing ClickUp Skills that actually work

A vague Skill gives you vague output, just more consistently. The Skills that perform best in the workspaces we manage share three habits.

Be specific about "done"

Don't write "make a status report." Write the sections, the order, the length, and what to do when data is missing. The more detail in the Skill, the more consistent the result.

Point it at real work

When you run a Skill, name the project, List or task it should use. Skills that pull from real workspace data beat generic requests every time, and Brain will tell you if something is missing.

Iterate, don't rebuild

Use Edit with Brain to refine a Skill after a few runs. Description history keeps earlier versions, so you can experiment without losing a version that worked.

Rolling out Skills across your team

Two settings control how ClickUp Skills spread, and mixing them up is the most common mistake we see. Sharing controls who can see and edit a Skill. Enabling controls whose Brain, and which Super Agents, use it automatically. Skills are private when you create them, so nothing reaches the team until you share it.

Each Skill also has a status. Published Skills load automatically for anyone who has them enabled. Draft Skills are visible only to their creator. Disabled Skills are invisible to Brain and Super Agents. Our advice: keep new ClickUp Skills in Draft, test them for a week, then publish and enable them for a Team rather than one person at a time.

On permissions, members, admins and owners can create Skills. Guests and limited members can use one only if a member or admin shares it with them directly, which is handy for client-facing workspaces where you want consistency without handing over edit rights.

ClickUp Skills FAQ