Skip to main content
Skills are reusable, named workflows the agent can run on demand wherever you work with it — Analytics Chat, Workbooks, dashboards, and the IDE. Instead of re-typing the same multi-step request every time, you pick a skill and the agent follows the workflow your team has already defined — for example, a Weekly revenue report that totals revenue, breaks it down by region, and calls out week-over-week trends. Skills are authored by your data team as part of the semantic model. This page covers how to find and run them. To create skills, see Skills in the agent configuration docs.
The slash menu in Analytics Chat listing available agent skills, each with a title and description

​
Running a skill

There are three ways to run a skill from the chat input.
1

Skill buttons

When skills are available, they appear as buttons in the chat empty state — one button per skill, labeled with the skill’s title. Click a button to start the skill.
2

Slash menu

Type / in the chat input to open the skill menu. The menu filters as you type and is keyboard-navigable. When skills are available, the input placeholder reads “Type / for skills.”
3

Automatic matching

You don’t always have to pick a skill explicitly. If a free-text request matches a skill’s description, the agent recognizes the intent and runs the matching skill on its own — asking “can I get the weekly revenue summary?” may trigger a weekly revenue report skill.

​
Adding context before you run

Picking a skill — whether from a button or the / menu — does not send the message immediately. Instead, it inserts a styled /skill-name token into the chat input and keeps your cursor there. This lets you add specifics before running. Type any extra context after the token, then send. On send, the message becomes the skill invocation plus whatever you added. For example: 
/weekly-revenue-report for EMEA, last 6 weeks
runs the weekly revenue report skill, scoped to the EMEA region over the last six weeks.
Running skills is available to anyone with chat access, including Explorer and Viewer roles. Authoring skills requires data-model edit access — see Skills in the agent configuration docs.