> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.laposta.org/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.laposta.org/_mcp/server.

# Installing the Laposta skill for your AI assistant

> Give your AI assistant access to the entire Laposta API with a ready-made extension.

A skill is a folder containing instructions for your AI assistant. The Laposta skill includes the entire API: all endpoints, required fields, error codes, and common mistakes. This means you do not have to explain anything before asking a question.

The skill is free, open source, and available at [github.com/laposta/laposta-skill](https://github.com/laposta/laposta-skill). The endpoint reference in the skill is generated from the same source as this documentation. Whenever the API changes, a single script runs to make sure the skill is up to date again.

## Example prompts

You can do everything [the API](/api) can do, using plain language. Here are a few examples of prompts you can use straight away:

* "How many active subscribers are in each of my lists?"
* "Add these twelve email addresses to the newsletter list, putting the first name in the right field."
* "Who unsubscribed last month?"
* "Create a campaign from this HTML file and send me a testmail."
* "Compare the open rate and clickratio of my last five campaigns."

If you ask about an endpoint, the skill looks up the answer in its own reference rather than relying on its memory.

## Installing in Claude Code

The repository also serves as a plugin marketplace. Run these two lines:

```text
/plugin marketplace add laposta/laposta-skill
/plugin install laposta@laposta-skill
```

Next, choose where to install the skill: for yourself, for a single project, or locally only. You can fetch updates later using `/plugin marketplace update laposta-skill`.

> **Note**
>
> If you get a message saying that `/plugin` is not available, this is not caused by the skill. Those slash commands only work in Claude Code in the terminal, not in the desktop app or browser. In those environments, use these regular commands instead:
>
> ```bash
> claude plugin marketplace add laposta/laposta-skill
> claude plugin install laposta@laposta-skill
> ```

If you prefer to place the files yourself, copy the `laposta` folder to your personal skills folder. Claude Code recognises the folder immediately, without you having to restart the application.

**`Handmatig installeren`**

```bash title="Handmatig installeren"
git clone https://github.com/laposta/laposta-skill.git
mkdir -p ~/.claude/skills
cp -r laposta-skill/plugins/laposta/skills/laposta ~/.claude/skills/
```

## Installing on claude.ai

There is no marketplace on claude.ai, so you can upload a zip file there instead. Make sure the `laposta` folder is at the top level of the zip file, otherwise it will not be recognised.

**`Het zipbestand maken`**

```bash title="Het zipbestand maken"
cd laposta-skill/plugins/laposta/skills && zip -r laposta.zip laposta
```

Upload this file in your settings under ‘Skills’.

> **Warning**
>
> Network access must be enabled on claude.ai, otherwise the assistant cannot reach `api.laposta.nl`. Whether you can enable this yourself depends on your own settings and what an administrator allows. Via the Claude API, the skill itself works, but it cannot reach `api.laposta.nl` because that environment has no internet connection.

## Installing in other assistants

The skill only uses the fields from the Agent Skills standard. This means the same folder works in any application that follows this standard, such as Gemini CLI, GitHub Copilot, Codex, and Cursor. The location of the skills folder varies per application. You can find this in the documentation of the application itself.

## Providing your API key

The skill does not ask for your key during the conversation, but reads it from the `LAPOSTA_API_KEY` environment variable. Set it up as follows:

```bash
export LAPOSTA_API_KEY="your-key"
```

You can read how to get a key in [Create an API key](/hoe-kom-ik-aan-een-api-sleutel). Create a separate key for this purpose. You can read why this is important under [Connect an AI assistant](/laposta-gebruiken-met-ai).

## Working safely with the skill

The safety rules are built into the skill itself, so you do not have to worry about them.

| Situation                               | What happens                                                                   |
| --------------------------------------- | ------------------------------------------------------------------------------ |
| Looking something up                    | Happens at once, without a confirmation prompt                                 |
| Deleting, emptying, scheduling, sending | You are asked for confirmation first, including the number of subscribers      |
| Editing many subscribers at once        | Also asks for confirmation first, even if it is a series of regular calls      |
| Sending a campaign                      | Always sends a testmail first                                                  |
| "Remove someone from the list"          | Asks whether you mean to unsubscribe or delete them, as these are not the same |
| Your key                                | Is never shown, saved, or placed in a command                                  |

## Related articles

#### [Connecting an AI assistant to your account](/laposta-gebruiken-met-ai)

Let an AI assistant work safely in your lists and campaigns via the API.

#### [The Laposta API](/api)

Connect Laposta to your own software: synchronise subscribers, send campaigns and…

#### [Creating an API key](/hoe-kom-ik-aan-een-api-sleutel)

You can create and manage your API keys on the Connect page. Please note: a new key can…

#### [Using labels on subscribers](/labels)

Give your subscribers custom labels to filter by, send campaigns to a selection, and…