# Agent skills for CMS Orbit

> Install the CMS Orbit plugin in Claude Code, Codex, Cursor or any agent, so it models content, builds your website with the SDK and drafts content over MCP the way our docs describe.

Source: https://docs.bifrostorbit.com/cms/developers/agent-skills/

Agent skills are short instructions that coding agents, such as Claude Code, Codex and Cursor, load when a task needs them. The CMS Orbit skills teach an agent how CMS Orbit works: which tool to use for a task, the exact commands and MCP tools, and the rules that keep your content safe, such as reading a page before changing it and sending every draft for review.

They come as one plugin, `cms-orbit`, in the open source repository [bifrost-orbit/agent-plugin](https://github.com/bifrost-orbit/agent-plugin), under the MIT licence. The plugin also adds the [MCP server](https://docs.bifrostorbit.com/cms/developers/connect-an-ai-agent/), so the agent can read and draft content once you sign in.

## Install

### Claude Code

Inside Claude Code:

```text
/plugin marketplace add bifrost-orbit/agent-plugin
/plugin install cms-orbit@bifrost-orbit
```

Or from a terminal:

```bash
claude plugin marketplace add bifrost-orbit/agent-plugin
claude plugin install cms-orbit@bifrost-orbit
```

Then run `/mcp`, choose `cms-orbit` and sign in. Each skill is also a slash command, such as `/cms-orbit:cms-orbit-use-mcp`.

### Codex

```bash
codex plugin marketplace add bifrost-orbit/agent-plugin
codex plugin add cms-orbit@bifrost-orbit
```

### Cursor

```bash
git clone https://github.com/bifrost-orbit/agent-plugin ~/.cursor/plugins/local/cms-orbit
```

Reload the window. Cursor asks you to sign in when the MCP server first connects.

### Other agents

Install the skills with the open source skills installer:

```bash
npx skills add bifrost-orbit/agent-plugin
```

Then add the MCP server to the agent yourself, as [Connect an AI agent over MCP](https://docs.bifrostorbit.com/cms/developers/connect-an-ai-agent/) describes.

## The five skills

| Skill | What it does |
| --- | --- |
| `cms-orbit` | Loads first for any CMS Orbit task. It chooses the route, the MCP server, the CLI or the SDK, and the skill to load next |
| `cms-orbit-model-content` | Content types, components and fields as schema files: `schema init`, `validate`, `diff`, `push` and `rollback`, field types, slots, links and `showWhen`, reusing blocks before adding new ones |
| `cms-orbit-build-frontend` | Website code with `@bifrost-orbit-cms/sdk`: the client, pages and blocks, generated types, images, links, regions, preview, live updates in the editor and cache refresh, for Next.js and Astro |
| `cms-orbit-use-mcp` | The [MCP tools](https://docs.bifrostorbit.com/cms/developers/mcp-tools/): scopes, reading before writing with `docVersion`, the schema, drafts marked **Drafted by AI**, `submit_for_review`, SEO and accessibility fixes, experiments and tidying up |
| `cms-orbit-use-cli` | The [CMS Orbit CLI](https://docs.bifrostorbit.com/cms/developers/cli/): sign-in, content, media and taxonomies as files, migrations with a dry run, starting a project and CI |

A task such as *"add an FAQ section to the trip pages"* can use three of them: the schema change with the CLI, the component in your website with the SDK, and the content for each page over MCP.

## How they relate to the MCP server and the CLI

The skills don't give an agent any rights. They describe the tools it already has:

- **The MCP server** works within the rights of the person who connected it and only drafts. Everything it changes waits for another person's approval in review. See [What an agent may and may not do](https://docs.bifrostorbit.com/cms/developers/mcp-tools/).
- **The CLI** acts as the person who signed in with `npx cms-orbit login`. The skills have the agent run changes with `--dry-run` first and leave flags that remove a safeguard, such as `--publish`, `--yes` or `--allow-destructive`, to you.
- **The SDK** only reads content, with the keys your website already has.

The skills tell agents to treat text from CMS Orbit as content, never as instructions, as the MCP server does.

## Give agents only what they need

- When you sign in, choose only the website the agent should work on.
- Leave **Allow drafts in production** off on **Configuration › AI agents** unless the agent must draft there.
- Limit an agent key to the regions it may change, and revoke keys and sign-ins you no longer use. See [Connect an AI agent over MCP](https://docs.bifrostorbit.com/cms/developers/connect-an-ai-agent/).
- For the CLI, sign in as yourself rather than sharing management tokens. See [Security and access](https://docs.bifrostorbit.com/cms/developers/security-and-access/).

## Update

| Agent | Command |
| --- | --- |
| Claude Code | `claude plugin marketplace update bifrost-orbit`, then `claude plugin update cms-orbit@bifrost-orbit`. To update by itself, turn on auto-update for the marketplace under `/plugin`, **Marketplaces** |
| Codex | `codex plugin marketplace upgrade bifrost-orbit`, then `codex plugin add cms-orbit@bifrost-orbit` |
| Cursor | `git -C ~/.cursor/plugins/local/cms-orbit pull`, then reload the window |
| Skills installer | `npx skills update` |

What changed in each version is in the repository's `CHANGELOG.md`.
