An email test often needs several steps: choose devices, start a render, wait for results, and inspect the screenshots. A skill gives your AI client reusable instructions for that workflow, including what to check when a result is incomplete or a connection needs attention.

MailSlurp skills work with the [MailSlurp MCP connection](/docs/mcp/). MCP provides the tools; a skill explains how to use them for a task. Installing a skill does not grant permissions, connect a mailbox, or start sending email.

## Choose a skill

Download the instructions for the workflow you need. Each file is named `SKILL.md`; keep it in a folder with the skill name shown below.

| Workflow | What it helps your AI client do | Skill file |
| --- | --- | --- |
| Check a connection | Confirm the workspace, permissions and available features without starting a test | [mailslurp-connect](/skills/mailslurp-connect/SKILL.md) |
| Render an email | Choose targets, check credits, start a render and inspect screenshots or target failures | [mailslurp-email-rendering](/skills/mailslurp-email-rendering/SKILL.md) |
| Test inbox placement | Prepare a test, use its seed addresses, confirm the send and interpret inbox, spam or pending results | [mailslurp-inbox-placement](/skills/mailslurp-inbox-placement/SKILL.md) |
| Read warmup status | Inspect program readiness, pacing, usage and recorded placement checks | [mailslurp-warmup-status](/skills/mailslurp-warmup-status/SKILL.md) |
| Manage warmup | Create or manage programs with explicit sending permission and recover interrupted operations | [mailslurp-warmup-programs](/skills/mailslurp-warmup-programs/SKILL.md) |
| Manage sending connections | Find existing senders, inspect settings and manage permitted connection or seat changes | [mailslurp-sending-connections](/skills/mailslurp-sending-connections/SKILL.md) |

## Add a skill to your client

First [connect MailSlurp with MCP](/docs/mcp/#install-in-your-ai-client) and approve the permissions needed for your task. Then save the chosen skill in your client's supported skill directory.

### Coding clients

Use a separate folder for each skill:

| Client | Project directory | Client instructions |
| --- | --- | --- |
| Codex | `.agents/skills/<skill-name>/SKILL.md` | [Build skills](https://learn.chatgpt.com/docs/build-skills) |
| Claude Code | `.claude/skills/<skill-name>/SKILL.md` | [Claude Code skills](https://code.claude.com/docs/en/skills) |
| GitHub Copilot in VS Code | `.github/skills/<skill-name>/SKILL.md` | [VS Code Agent Skills](https://code.visualstudio.com/docs/agent-customization/agent-skills) |
| Cursor | `.cursor/skills/<skill-name>/SKILL.md` | [Cursor skills](https://cursor.com/docs/skills) |
| Gemini CLI | `.gemini/skills/<skill-name>/SKILL.md` | [Gemini CLI skills](https://geminicli.com/docs/cli/using-agent-skills/) |

For example, add the rendering skill to a Codex project:

```bash
mkdir -p .agents/skills/mailslurp-email-rendering
curl --fail --location \
  https://www.mailslurp.com/skills/mailslurp-email-rendering/SKILL.md \
  --output .agents/skills/mailslurp-email-rendering/SKILL.md
```

Open the downloaded file and review it before using it. Reload your client's skills if needed, then ask it to use `mailslurp-email-rendering` for your email test.

### ChatGPT and Claude web or desktop

Connect the remote MCP server using the [client setup instructions](/docs/mcp/#install-in-your-ai-client). For reusable skills, use your client's supported skill creation or upload flow when available: [ChatGPT and Codex skills](https://learn.chatgpt.com/docs/build-skills) or [Claude skills](https://support.claude.com/en/articles/12512180-using-skills-in-claude).

If your client does not load skill files, you can still ask it to perform a task through the connected MCP tools. A skill file does not install a directory plugin or change your workspace's policies.

## Try a bounded task

Start with the connection skill:

```text
Use mailslurp-connect to check which MailSlurp workspace is connected and whether I have device-rendering access. Do not start a render, retrieve messages or change anything.
```

For a rendering task, provide the email HTML and tell the client which devices to use. Ask it to check the required credits before starting and to inspect the returned screenshots. For placement, send the intended email to the test's seed addresses and confirm that send before requesting the result.

Warmup management and sender seat changes can enable ongoing sending or recurring charges. Choose those permissions deliberately; use the warmup status skill when you only need to inspect a program. Normal MailSlurp allowances, plan activation and add-on rules apply to authorized product actions.

## When a skill cannot finish

A skill can use only the tools your connected client exposes. If an operation is missing, check the approved permissions and reconnect if needed. A plan upgrade does not grant permission, and a broader permission does not add a missing plan entitlement.

Keep the operation or run ID when a test is still pending or its outcome is uncertain. Ask the client to inspect that existing operation before starting another. See [MCP troubleshooting](/docs/mcp/#troubleshooting) for connection, permission and account setup checks.