Skip to main content
A skill is a published set of instructions that an AI tool loads from Tempo over MCP and then follows, calling Tempo’s tools along the way. Tempo stores the instructions as Markdown with their versions. The AI tool does the reasoning. Organization admins manage the skills every member can run. This page covers that work. For how sellers run skills, see Skills.

​
Built-in skills

Tempo ships six skills. Four are enabled for every organization the first time someone opens the Skills page. Two are in the marketplace for you to add. Tempo keeps untouched default skills current. Once you edit or re-enable a default, it becomes your organization’s own copy and stops receiving Tempo’s updates.

​
Scope and permissions

A skill can only use public Tempo MCP tools. A member only sees and can run a skill whose tools are available on their connection.

​
The Skills page

In the sidebar, under Build, click Skills. Your skills lists the skills you and your organization can edit. Use Find skill… to search, and filter by Task, Persona, Owner (All owners, You, Organization), and Status (All statuses, Disabled, Live). Each row’s menu offers Copy as prompt, Duplicate, Enable or Disable, and Delete. The Marketplace panel lists Tempo’s catalog, filtered by Role and Category. Open a skill and click Add to my skills for a personal copy or Add to organization to make it available to everyone. Create your skill starts a new one. Describe the skill you want and Tempo drafts it, or click New for a blank skill. A new skill is personal unless you create it for the organization.

​
Edit a skill

Open a skill to edit it. Switch between Visual and Markdown with the editor mode control. Copy skill text copies the Markdown; Copy as prompt copies it ready to paste into an assistant. The Settings panel holds Skill name, Skill summary, Task, Persona, Owner, and Status. The summary is what sellers and AI tools see when choosing a skill, so say when to use it.

​
Enable, disable, and versions

A skill is Disabled until you enable it. Enabling publishes the current saved version; that snapshot is what AI tools receive. Disabling unpublishes it.
1

Save your changes

Every save is a version. Tempo asks you to save before enabling, disabling, or viewing history.
2

Click Enable

The skill becomes Live and is registered for every member whose connection has the tools it needs.
3

Keep editing if you need to

Later edits do not change what sellers receive until you click Enable again. Until then, they get the last enabled version.
Open the version history to compare the Current Skill Markdown with a Historical Skill Markdown and click Restore this version. Restoring creates a new version and keeps the later ones.

​
How skills reach sellers

  • As MCP prompts. Every enabled organization skill, and each member’s own enabled personal skills, is registered as a prompt on their MCP connection. Clients that support prompts show them by name. The four defaults keep their stable names; other name collisions are prefixed with org_ or personal_.
  • By asking. Tempo’s MCP server routes a request for a morning brief to What needs my attention today? and a request for meeting prep to Prep me for my next call. For other requests, the AI tool can call list_skills to find a skill and use_skill to load it.
  • As native launchers. On the Skills page, open Skill downloads and choose Download for Claude or Download for Codex. The download is a small launcher that calls use_skill; it does not contain the skill text, so updates reach it automatically.
Running a skill needs the member’s MCP connection to include Skills and Build tools. When a member connects Claude, ChatGPT, or another client from Settings → Connections, they check Include Skills and Build tools in the setup dialog. A connection made without it cannot run skills. See Toolsets. Admins can also manage skills over MCP with manage_skills: create a draft, add a marketplace skill, update, publish, or delete. Organization writes need the Admin role. See the MCP tool catalog.

​
What the built-in skills do and do not do

  • Built-in skills treat inbound artifacts as data, not instructions, and do not guess a person’s identity, contact details, or authority.
  • No built-in skill sends email or messages.
  • Review my CRM changes is the only built-in skill that changes anything. It shows each proposed change and acts only on the ones the user confirms.
  • A custom skill follows whatever instructions you write. Review a skill’s instructions before you enable it for the organization.