@ picks an agent, # picks a connection, and / runs a skill, command, or chat action. A command is a saved prompt: type / plus its name and CloudThinker sends the full instruction for you.
Prerequisites
- Developers and Admins can run commands. Commands run in the chat box, and Viewers can’t chat with CloudThinker, so a Viewer can’t run one.
- To create, edit, import, or delete commands, you need the Developer or Admin workspace role.
/ menu, and any Developer or Admin can edit or delete any command that isn’t built in.
Prompt syntax
A plain sentence with none of the symbols works. Add
#connection when the workspace has several accounts and the answer depends on which one CloudThinker reads.
# picker selects connections and knowledge bases only, not output types.
What the / menu shows
Type/ in the CloudThinker chat box to open the menu. It has two groups, and typing after the / filters both.
Built-in commands
Every workspace includes these commands. You can run and view them, but you can’t edit or delete them.Setup helpers
These interview you or check your setup, then create or propose something./create-policy and /find-rules appear only where CloudThinker can write approval rules for you. A rule you accept there only records what it would decide until CloudThinker turns on Rule enforcement for your workspace, which is off by default, so set the Approval mode for the behavior you need today. If the commands are missing from your / menu, contact CloudThinker support, or whoever runs CloudThinker for your company. See Rules troubleshooting.
Cloud analysis prompts
These are saved prompts with no fixed output format. CloudThinker runs them against the workspace’s connected cloud accounts, so connect at least one first, and add#connection when you want one account.
Create a command
1
Open the Commands page
Switch to the right workspace in the workspace switcher at the top of the sidebar, then go to More → Workspace settings → Commands. The page lists only this workspace’s commands. Tabs split the list into All, Your Commands (the ones your workspace created), and CloudThinker’s Commands (built in), and Search commands… filters by name.
2
Click New Command
The Create Command dialog opens. Fill in the three fields:
3
Click Create Command
Success state: the command appears under Your Commands, and typing
/ plus the first letters of its slug in any chat in the workspace shows it.Run a command
1
Type / and pick the command
Type
/ in the chat box, keep typing to filter, and select the command. The /slug token stays in your message.2
Add context and send
Type anything extra after the token, then send:CloudThinker replaces
/security-configuration-audit with the command’s full prompt before the agent reads your message. Slugs match without regard to case.Success state: the reply answers the saved instruction plus your added context, not the literal slug text.Edit or delete a command
On More → Workspace settings → Commands, hover over the command’s card and click the … menu (Open actions).- Edit opens the Edit Command dialog. Change the fields and click Update Command.
- Delete asks you to confirm in a Delete Command dialog. The slug stops expanding at once.
cloudthinker chat -p), so one saved instruction can serve chat, schedules, and scripts.
Move commands between workspaces
Commands belong to one workspace. To reuse a set in another workspace:1
Export from the source workspace
On More → Workspace settings → Commands, click Export File. CloudThinker downloads The file uses the product’s older internal names:
shortcuts-export-<date>.json with every command under Your Commands. Built-in commands are left out, and the active tab and search don’t limit the export.2
Import into the target workspace
Switch to the other workspace, open More → Workspace settings → Commands, click Upload File, and pick the JSON file. One file imports up to 100 commands.Success state: the commands appear under Your Commands. A command whose slug is already taken in that workspace gets a new slug automatically, so check the list before you share the names.
Troubleshooting
A command doesn't expand when I send it
A command doesn't expand when I send it
An enabled skill whose name matches the slug, ignoring case, wins the slug. The menu hides the command, and
/name invokes the skill instead. Rename the command’s slug on More → Workspace settings → Commands, or turn off the skill if you meant the command.I don't see New Command or Upload File
I don't see New Command or Upload File
Your workspace role is Viewer. Ask a workspace Admin to give you the Developer role, or ask a Developer to create the command.
The prompt won't save
The prompt won't save
The Prompt field holds up to 1,000 characters, and Title, Slug, and Prompt are all required. For longer procedures, build a custom skill instead.
Next steps
Skills
Package multi-step procedures that share the / menu with your commands
Automations
Run a saved prompt on a schedule instead of typing it
Slack integration
Ask CloudThinker the same questions from a Slack channel
Multi-account AWS
Target the right AWS account with
#connection in multi-account setups