Skip to main content
Commands are reusable prompts saved to your workspace — type / at the start of a chat message to run one instead of retyping the same instruction. Your workspace ships with a set of built-in commands, and any Developer or Admin can add their own.

​
Prerequisites

  • A CloudThinker workspace — any member can run commands
  • The Developer or Admin workspace role to create, edit, import, or delete commands

​
Create a command

1

Open the Commands page

Go to Settings → Commands. The page lists every command in the workspace, split into All, Your Commands, and CloudThinker’s Commands tabs, with a search box to filter by name.
2

Click New Command

Fill in the form:
3

Click Create Command

Success state: the command appears under Your Commands, and typing / plus its slug in any chat in the workspace suggests it.
Put the stable part of the instruction in the command and leave the variable part for chat. A command that ends mid-sentence — “…then analyze:” — lets each run add its own target.

​
Run a command

1

Type / at the start of a message

A picker opens listing your commands, built-in commands, and enabled skills — packaged instructions agents follow — together. Keep typing to filter the list.
2

Select the command and send

The /slug token stays visible in your message; add any extra context after it, then send. On send, CloudThinker replaces the token with the command’s full prompt before the agent reads it.
Success state: the agent responds to the expanded prompt — not to the literal /slug text.
If an enabled skill has the same name as a command, the skill wins: selecting it invokes the skill, and the command with that slug does not expand.

​
Built-in commands

CloudThinker seeds every workspace with read-only commands. You can run and view them, but not edit or delete them.

​
Move commands between workspaces

Commands belong to one workspace. To reuse a set elsewhere:
1

Export from the source workspace

On Settings → Commands, click Export File. CloudThinker downloads a JSON file containing your commands.
2

Import into the target workspace

Switch workspaces, open Settings → Commands, and click Upload File. Select the JSON file — up to 100 commands import per file.Success state: the imported commands appear under Your Commands. A command whose slug is already taken is imported under an automatically renamed slug.

​
Next steps

CloudThinker Language

Learn the full prompt syntax the / token belongs to — agent mentions, tool tags, and credentials

Skills

Package multi-step procedures that share the / picker with your commands

Automations

Run a saved prompt on a schedule instead of typing it — no chat required

Multi-Account AWS Operations

See commands in practice: one slash command per AWS account to switch context instantly