Agent Skills

Drop-in modules that teach a coding agent the Pombo workflow.

A Skill is a short Markdown file that gives a coding agent (Claude Code, Cursor, or anything that reads project rules) the Pombo playbook up front: the order to do things in, the tool to reach for, and what "done" looks like. It turns "connect the MCP server and hope" into a repeatable workflow.

Skills are the plan. The MCP server does the work.

The skills

Browse and download them at flypombo.com/skills.

Skill	For
`pombo-setup`	Getting an organization to where it can send: connect, verify a domain, get approved, test.
`pombo-migrate`	Moving off another platform: contacts, fields, suppression, templates, automations, in order.
`pombo-events`	Wiring a product event to a lifecycle flow: shape the payload, `POST /api/v1/events`, build the sequence.
`pombo-campaigns`	Drafting a one-off campaign end to end. Sending stays a human click.
`pombo-transactional`	Keyed transactional templates: create, send or bind to an event, test.

Each is a few hundred words. Read them; they are the same advice this documentation gives, compressed and addressed to an agent.

Installing

Claude Code

Save each skill under .claude/skills/<name>/SKILL.md in your repo. Claude loads it automatically when the task is relevant.

mkdir -p .claude/skills/pombo-setup
curl -sL https://flypombo.com/skills/pombo-setup > .claude/skills/pombo-setup/SKILL.md

Cursor, Windsurf, and rules-based agents

Paste the skill body into your rules file (.cursor/rules, AGENTS.md) or into context at the start of a Pombo task.

Every skill at once

The manifest is a JSON catalogue of all skills with their raw URLs:

curl -sL https://flypombo.com/skills/manifest.json

Each entry has a name, a description, and a url that returns the raw SKILL.md. Loop over it to sync all of them into a project.

Already connected over MCP

If your agent is connected to the MCP server, it does not need any of these URLs. Read the resource pombo://skills for the catalogue, then pombo://skills/<name> for one skill in full. Same content, without leaving the session.

Keeping them current

The skills track the product. Re-fetch them when you start a new integration, or pin a copy in your repo and update it deliberately. The manifest carries an updated date.

Something unclear or missing? Tell us.