> ## Documentation Index
> Fetch the complete documentation index at: https://docs.cloudthinker.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Commands

> Save reusable prompts as slash commands and run them in any chat by typing / instead of retyping instructions

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](/guide/workspace-users) to create, edit, import, or delete commands

## Create a command

<Steps>
  <Step title="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.
  </Step>

  <Step title="Click New Command">
    Fill in the form:

    | Field      | What to enter                                                                                                                                                      |
    | ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
    | **Title**  | A human-readable name, e.g. `Weekly cost review`                                                                                                                   |
    | **Slug**   | The `/name` users type. Auto-generated from the title; edit it before saving if you want a shorter one                                                             |
    | **Prompt** | The full instruction inserted when the command runs, up to 1,000 characters. Mention agents with `@` — e.g. start with `@alex` so the right specialist picks it up |
  </Step>

  <Step title="Click Create Command">
    **Success state:** the command appears under **Your Commands**, and typing `/` plus its slug in any chat in the workspace suggests it.
  </Step>
</Steps>

<Tip>
  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.
</Tip>

## Run a command

<Steps>
  <Step title="Type / at the start of a message">
    A picker opens listing your commands, built-in commands, and enabled [skills](/guide/skills/overview) — packaged instructions agents follow — together. Keep typing to filter the list.
  </Step>

  <Step title="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.

    ```text theme={null}
    /security-configuration-audit focus on the production AWS account
    ```

    **Success state:** the agent responds to the expanded prompt — not to the literal `/slug` text.
  </Step>
</Steps>

<Note>
  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.
</Note>

## Built-in commands

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

| Command                          | What it does                                                                                      |
| -------------------------------- | ------------------------------------------------------------------------------------------------- |
| `/create-agent`                  | Interviews you and helps design a new custom agent for the workspace                              |
| `/create-skill`                  | Interviews you and helps create a new custom skill                                                |
| `/create-automation`             | Clarifies the trigger and the prompt, then creates an [automation](/guide/automation/automations) |
| `/resource-rightsizing-analysis` | Finds underutilized resources by analyzing CPU, memory, and storage usage                         |
| `/automated-backup-strategy`     | Reviews backup schedules and retention policies for cost and coverage                             |
| `/monitoring-alerting-setup`     | Configures monitoring and alerting for utilization, performance, and cost anomalies               |
| `/security-configuration-audit`  | Audits access controls, encryption settings, and security best practices                          |
| `/cost-allocation-tagging`       | Implements consistent resource tagging for cost allocation and budget visibility                  |

## Move commands between workspaces

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

<Steps>
  <Step title="Export from the source workspace">
    On **Settings → Commands**, click **Export File**. CloudThinker downloads a JSON file containing your commands.
  </Step>

  <Step title="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.
  </Step>
</Steps>

## Next steps

<CardGroup cols={2}>
  <Card title="CloudThinker Language" icon="message" href="/guide/language">
    Learn the full prompt syntax the `/` token belongs to — agent mentions, tool tags, and credentials
  </Card>

  <Card title="Skills" icon="sparkles" href="/guide/skills/overview">
    Package multi-step procedures that share the `/` picker with your commands
  </Card>

  <Card title="Automations" icon="calendar-check" href="/guide/automation/automations">
    Run a saved prompt on a schedule instead of typing it — no chat required
  </Card>

  <Card title="Multi-Account AWS Operations" icon="layer-group" href="/guide/use-cases/multi-aws-accounts">
    See commands in practice: one slash command per AWS account to switch context instantly
  </Card>
</CardGroup>