Actions

The actions list surfaces the skills and workflow files Palette finds in your workspace.

What an action is

An action is a set of instructions you can run inside a chat. How it runs depends on the agent:

• Claude Code can resolve compatible commands natively through /.
• Other agents can run a filesystem action from Palette's list. Palette sends that action's instructions into the active chat as the prompt.
• Automatic skill discovery or invocation depends on the underlying agent. Do not assume every agent will discover the same skill on its own.

The source instructions live as files in your workspace, commonly in agent-specific command or skill folders.

The actions list

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

• Compatible commands defined in your workspace
• Skills and filesystem actions 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. Click an action to run it from the active chat. With Claude Code, you can also use / for compatible commands. Whether an agent discovers a skill without you choosing it depends on that agent.

In the folder, not your account

Most AI tools (Claude.ai, ChatGPT, and nearly all others) 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. Marketplace workflows. A workflow such as Accounts can add actions for recurring work.
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. Claude Code can run compatible commands by name through /.
• A skill describes a capability and when to use it. Native discovery varies by agent, while Palette can still send a selected filesystem action's instructions into the chat.

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
• Marketplace, install folder systems and workflows
• Chats, where actions run