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

# Add skills, agents and MCP servers

The Marketplace is where you find and share what makes an agent more capable:

| Type | Gives the agent |
| --- | --- |
| **Skills** | Know-how for a task, such as a review checklist or a release process |
| **Agents** | A specialised helper with its own instructions, which the main agent can hand work to |
| **MCP servers** | Tools from other services, such as an issue tracker or a database |
| **Plugins** | Claude Code plugins, which bundle commands, agents, skills and MCP servers |
| **Extensions** | Add-ons that change how Haarness itself works |

Anyone can browse the [public catalogue](https://haarness.ai/marketplace). In the Cloud app, **Marketplace** also shows your
account's private items.

## Install into a Cloud workspace

1. Open **Marketplace**, search or filter by type, and open an item.
2. Choose **Install into a workspace** and pick a workspace.
3. The workspace opens on **Capabilities**. Check the version and choose **Install in this workspace**.

You can also start from the workspace: open **Workspace tools → Capabilities** and search the Marketplace there.

All chats in the workspace share what you install. Changes apply as soon as the agent is idle, without restarting the
chat.

## Turn things on and off

In **Workspace tools → Capabilities** you can, for each installed item:

- **Disable** it without losing its settings, and **Enable** it again later;
- choose another version under **Versions and updates**;
- **Remove** it.

To create your own skill, agent or MCP server for one workspace only, open **Add custom** in **Capabilities**. To set the same tools up for every new workspace, put them in a [Cloud agent](https://haarness.ai/docs/cloud/agents.md).

## Install on your own computer

The same catalogue works in the CLI and Desktop. Sign in with `haarness login` to see your private items too.

```sh
haarness marketplace search --kind skill --q review
haarness marketplace install skill RESOURCE_ID --local
haarness marketplace installed
haarness marketplace update RESOURCE_ID --local
haarness marketplace remove RESOURCE_ID --local
```

`RESOURCE_ID` is the item's ID or its `publisher/slug`. `--local` installs for the current project only; without it,
or with `--global`, the item is installed for every project on this computer. `haarness marketplace disable` and `enable` turn an installed item off and
on again without removing it. In Desktop, open **Settings → Marketplace**; in the terminal UI, type `/marketplace`.

You can also just ask the agent, for example "find a code review skill in the marketplace and install it".

## Publish your own

1. In **Marketplace**, choose **Publish a resource**.
2. Pick the **Resource type** and the **Visibility**:
   - **Private:** only members of your account can see and install it. It is available as soon as it passes the
     automatic checks.
   - **Public:** everyone can see it after the Haarness team reviews it.
3. Give it a **Name**, a **Slug** (its short ID) and a one-sentence **Summary**.
4. Add its content, as the table below shows.
5. Choose **Submit resource**.

| Type | What you submit |
| --- | --- |
| Skill | A **ZIP archive** of the skill folder, with its `SKILL.md`, or a **Public GitHub repository** |
| Agent | A ZIP archive with the agent's Markdown file, or a public GitHub repository |
| Plugin | A ZIP archive of a Claude Code plugin, with its `.claude-plugin/plugin.json`, or a public GitHub repository |
| MCP server | The **MCP configuration (JSON)**, pasted into the form, with `${NAME}` placeholders for anything secret |
| Extension | The **Exact npm package version**, such as `@publisher/extension@1.0.0` |

A ZIP archive can be up to 256 MB. For a GitHub repository, give its **Repository URL** and, if you like, a
**Subdirectory** and a **Commit, tag or branch**.

To publish a new version, submit again with the same type and slug. **Never put credentials in a resource.** List
an MCP server's placeholders under **Required configuration values**: each person who installs it fills them in
with their own values.

## Before you install

An installed item can use the same files, commands and network as the agent itself. Install items from publishers
you trust, and read what an item declares on its page before you add it. Every download is checked against the
published version, so it cannot be changed in transit.