Skip to main content
A skill is a named, reusable set of instructions for a task you do more than once. Instead of writing the same context and steps into the composer every time, you save them once as a skill and bring them into any thread. This page covers running a skill, creating one, and managing it once it exists.

Run a skill

Type / in any composer and pick a skill from the list. Its instructions become part of the thread, the same as if you’d typed them yourself.

Create a skill

1

Start from scratch

Give the skill a name and write its instructions directly: what it’s for and how it should approach the task.
2

Or import one you already have

Drag a folder or a .zip in instead of writing from scratch. Sidekick looks inside for a SKILL.md file and uses it to fill in the skill.
3

Paste it directly if import can't find one

If Sidekick can’t find a SKILL.md in what you dropped, paste its contents in directly instead.

Look inside a skill

Open a skill to see four tabs:
  • Instructions: the text that runs when the skill is used.
  • Files: supporting files bundled with the skill.
  • Runs: the history of past runs of this skill.
  • Versions: every saved edit to the skill, in order.

Restore a version

1

Open the versions tab

Find the version you want to go back to.
2

Restore it

Restoring makes that version the current one. The versions in between aren’t lost; they stay in the history.

Share and pin

Share a skill so teammates can run it too, not just you. Pin the skills you use most so they sit at the top of the list instead of getting buried under everything else.

Where to go next

Govern skills

How admins approve and manage the skills available across the workspace.

Thread and composer

The anatomy of a thread and how the composer sends work to it.