> ## Documentation Index
> Fetch the complete documentation index at: https://docs.findtempo.co/llms.txt
> Use this file to discover all available pages before exploring further.

# Skills

> Run Tempo's packaged commands, and publish your own for the team.

A skill is a packaged command you run instead of writing the prompt yourself — meeting prep, a follow-up draft, a pipeline review. The **Skills** library is where you find them, favorite the ones you use, and publish your own.

## Find a command

Open the Skills library and filter by role to narrow it to the work you actually do.

Commands come from two places:

| Source          | What it is                                  |
| --------------- | ------------------------------------------- |
| **Default**     | Shipped by Tempo and available to everyone. |
| **Marketplace** | Published for your organization, or by you. |

Favorite a command to keep it close, or add it so it's available where you work.

## What a command runs on

Tempo data is the operational source of truth — your deals, artifacts, observations, and tasks. Connected tools can contribute optional supporting evidence, but they do not replace what Tempo holds.

This is why a command's output stays consistent whether or not a given integration is connected: connecting more sources adds evidence, it does not change which record is authoritative.

## What you can run

The library covers the recurring work of a deal cycle:

* **Preparation** — walking into a call knowing where the deal stands
* **Follow-through** — turning what was said into next steps
* **Messaging** — drafting in your own voice, grounded in the deal
* **Pipeline** — reviewing across deals rather than one at a time
* **Coaching** — reviewing how a deal or a rep is progressing
* **Admin** — the configuration work behind the above

## Publish your own

<Steps>
  <Step title="Create or duplicate">
    Start a new command, or duplicate an existing one when it is close to what you want. Choose whether it belongs to you or to your organization.
  </Step>

  <Step title="Edit it">
    Change the command and describe what it should produce.
  </Step>

  <Step title="Publish a version">
    Publishing makes the current state available to its audience. Earlier versions are kept.
  </Step>
</Steps>

To go back, restore a prior version. Restoring does not discard the versions after it.

## When a command asks you to confirm

Some commands pause and ask before they act, rather than running straight through. Read what it proposes before confirming.