# Save a method as a skill

A skill is a reusable set of instructions for doing a kind of work. It tells teammates how to approach a task, what steps to follow, and what a good result includes.

## Create a useful skill

Open **Workspace → Skills → Add skill**, or ask a teammate to save a method that worked well. Give it a recognizable name and explain when it should be used.

> **Try this**
> Save a skill named Customer interview brief. It should group observations by theme, preserve exact quotes, distinguish interpretation from evidence, and finish with decisions and unanswered questions. Keep customer names and project details out of the reusable instructions.

## Use and improve it

Type `/` in the composer to find available skills, or ask for a skill by name. Inspect the instructions in the skills view when the result needs adjustment.

User-created skills can be edited or deleted. Built-in and plugin skills are read-only. Workspace skills are available to teammates in that workspace.

## Keep the right information in the right place

A skill describes the general method. A [routine](/docs/tools/scheduling) supplies the timing, target account, and task-specific instruction. [Memory](/docs/tools/memory-and-knowledge) stores continuing context and decisions.

You can also teach a task through the [computer](/docs/capabilities/computer). Review taught tasks in the teammate's settings before relying on them for repeat work.