Actions

The actions list is every skill and command in your workspace, surfaced in one place.

What an action is

An action is something runnable inside a chat. Two kinds, with one key difference: who triggers them.

• Commands are triggered by you. Type / in a chat and pick from the list, or call a command by name. A command is a repeatable workflow defined as a markdown file in your workspace.
• Skills are triggered by the agent. You give a skill to the agent as a tool, and the agent decides when to use it based on what you're working on.

Both live as files in your workspace, usually under a .claude/ folder.

The actions list

Inside every chat, you can open the actions list and see what's available. It pulls from:

• Commands defined in your workspace
• Skills installed in your workspace
• Anything a teammate added that synced into the folder

No digging through files, no remembering what's available. You see the full set.

Why this matters

A workspace can build up dozens of actions over time. Sales motions, content workflows, account reviews, weekly recaps. Without a way to see them, they get forgotten.

The actions list keeps them visible. You run commands with a click or /. The agent picks up skills automatically when they fit what you're doing.

In the folder, not your account

Most AI tools (Claude.ai, ChatGPT, almost every other) tie skills and commands to your account. They follow you, not your team. If you build a good workflow, your teammate has to rebuild it.

Palette is the opposite. Actions live in the workspace folder as plain markdown files. They sync with the folder. Anyone who has the folder has them.

That's why shared workspaces get more useful over time. Someone figures out a good outreach flow, drops it in as a command, and the whole team has it the next time their folder syncs. The folder is your team's shared brain for how you work with AI.

Where actions come from

Three sources, in order of how you typically get them:

1. Templates. A template like gtm-os comes with actions built in.
2. You add them. Drop a markdown file in .claude/commands/ or .claude/skills/ in your workspace.
3. Your team adds them. Anyone with access to the workspace folder can add an action. Cloud sync delivers it to everyone else.

Custom commands and skills

Both are markdown files in your workspace. The difference is mostly in how the file is written:

• A command is a prompt template. The file becomes the agent's instructions when you run /command-name.
• A skill is a tool description. The file tells the agent what the skill does and when to use it, so the agent can decide when to invoke it.

You don't need to be a developer to write either one. If you can describe the work in plain English, you can write the file.

The easiest way to start: ask the agent in a chat to suggest commands or skills based on what you do most. It can write the file for you and drop it in the right place.

Next

• Shortcuts, pin your most-used actions for one-click access
• Templates, pre-built actions for common kinds of teams
• Chats, where actions run