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

# Skills

> Install Boom's Agent Skills so Claude can run your customer conversations end-to-end over Boom.

Boom publishes a set of **Agent Skills** that teach Claude how to use Boom's
[MCP tools](/use-mcp) for real work: connecting your customer data, building the
audiences you want to reach, designing the [journey](/journeys) that carries a
conversation, launching it over WhatsApp, and reading back
[what customers said as structured data](/extraction).

The job is yours to pick. The same pieces cover winning back customers who
dropped off, support, product research, onboarding, qualifying leads, collecting
documents, and NPS follow-up. The skills themselves are open source, in
[BOOM-TML/skills](https://github.com/BOOM-TML/skills).

<Note>
  The skills run on Boom's [MCP tools](/use-mcp), and the plugin below sets that
  server up for you at `https://www.useboom.ai/mcp`. You sign in with your normal
  Boom login the first time Claude connects, so there's no API key to create or
  store. Already connected Boom by hand? Keep that same URL, and Claude Code
  treats the two as one server rather than loading Boom's tools twice.
</Note>

<Note>
  Options 1 and 2 below need a terminal or Claude Code. Option 3 works from the
  Claude app with no terminal at all.
</Note>

## Install

Pick the path that matches how you use Claude.

### 1. One command (recommended)

```bash theme={null}
npx @useboom/skills-setup
```

It asks who the skills are for, then sets up everything: Boom's marketplace, the
plugin, Boom's MCP server, and **auto-update**, so new skills and fixes reach you
without reinstalling.

Installed Boom's skills before, with `npx skills add`? The installer finds those
older copies, which never update, and moves them into a backup folder, so you
don't end up running each skill twice.

Then start Claude Code. The first time, it asks you to confirm installing the
marketplace and the plugin, and to approve Boom's MCP server. Sign in to Boom
when the window opens, and the skills show up as `boom:<skill-name>`.

<Accordion title="Prefer to set it up by hand?">
  The installer only writes these two keys, so you can paste them yourself:

  ```json theme={null}
  {
    "extraKnownMarketplaces": {
      "boom": {
        "source": { "source": "github", "repo": "BOOM-TML/skills" },
        "autoUpdate": true
      }
    },
    "enabledPlugins": { "boom@boom": true }
  }
  ```

  Use whichever settings file fits, the syntax is the same in all:

  | Where | File | Scope |
  | - | - | - |
  | Just you | `~/.claude/settings.json` | Your machine, every project |
  | A repo / team | `.claude/settings.json` (committed) | Everyone in that repo |
  | Whole org | `managed-settings.json` | Enforced for all members |
</Accordion>

<Note>
  `autoUpdate` is the line that matters. Marketplaces other than Anthropic's own
  arrive with auto-update **off**, so setting it is what keeps you current. Claude
  Code then refreshes the marketplace in the background shortly after each session
  starts, and either offers you `/reload-plugins` or picks up the new version on
  your next launch.
</Note>

### 2. From the `/plugin` menu, no files to edit

Prefer menus? Everything below happens inside Claude Code (terminal, desktop app,
VS Code, or JetBrains):

1. Type **`/plugin`** in the chat and press Enter to open the plugin manager.
2. Go to **Marketplaces → Add marketplace** and enter `BOOM-TML/skills`.
3. Go to **Discover**, find the Boom plugin, and click **Install** (choose "just
   me" or "this project").
4. Back under **Marketplaces**, open **boom** and choose **Enable auto-update**,
   so new skills reach you on their own. If a settings file already sets it, the
   menu shows it as fixed there.
5. Run **`/reload-plugins`** (or restart). The skills appear as
   `boom:<skill-name>`.

### 3. The Claude app (claude.ai, desktop, mobile)

The Claude app doesn't read plugin marketplaces, so there's no auto-update here.
You upload the skills you want, one at a time, and Claude can do most of the work:

1. Ask Claude, in a chat with code execution available:

   > Get the `launch-initiative` skill from github.com/BOOM-TML/skills and give
   > me a ZIP I can upload as a skill. The ZIP's root must be the skill folder
   > itself.

2. Download the ZIP it hands back.

3. Open **Customize → Skills → Add** and upload it.

Swap the skill name for whichever ones you want from [the list below](#the-skills).
You can also skip Claude entirely: download the folder from the repo and zip it
yourself, as long as the skill folder sits at the ZIP's root.

<Note>
  Uploaded skills are private to your account, and the feature needs **code
  execution** enabled. To hand them to a whole team at once, an admin provisions
  them under organization settings (Team and Enterprise).

  Connect the [MCP tools](/use-mcp) too, or the skills will have nothing to call.
</Note>

<Warning>
  These skills can launch initiatives and add participants, which send **real
  WhatsApp messages and emails to real customers**. Review what an agent is about to do
  before letting it run unattended. People on your Do Not Contact list are
  always skipped.
</Warning>

## The skills

Ten of them, and you don't type their names: Claude picks the right one from what
you ask.

| Skill | Use it to |
| - | - |
| `boom-overview` | Get oriented: Boom's object model, lifecycle, and which skill fits what you're doing |
| `onboarding` | A guided first run: build your first journey, send a Hello World, learn the mental model |
| `build-knowledge-base` | Prepare the context your agent works from: brand identity, plus a brief per use case |
| `connect-your-data` | Sync Postgres, MySQL, or Shopify data into Boom's CDP (read-only user, SSH tunnel, mapping SQL) |
| `cdp-and-segments` | Query the CDP and build the segments you'll target |
| `design-journey` | Design or debug the [journey](/journeys) behind an initiative: follow-up rounds, branching, timing, external calls |
| `whatsapp-templates` | Write WhatsApp openers that pass Meta review and earn replies |
| `launch-initiative` | Create and launch an initiative end to end, whatever the job, using the context formula from Boom's best performers |
| `manage-participants` | Add, monitor, and stop the people in an initiative |
| `analyze-results` | Turn a running initiative's [extracted data](/extraction) and transcripts into insight |

## Related

<CardGroup cols={2}>
  <Card title="Use MCP" icon="plug" href="/use-mcp">
    Connect Boom to Claude, Cursor, or any AI tool.
  </Card>

  <Card title="Authentication" icon="key" href="/authentication">
    API keys for scripts and server-to-server calls.
  </Card>
</CardGroup>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.