Skip to main content

Agent-ready headless CMS

Turn Claude Code into your content studio.

Install one plugin. Your coding agent plans, writes on-brand, translates, and publishes your content, working from a project brain that knows your voice. You approve before anything goes live.

Install in Claude Code
Hey Claude, install the Adapto plugin for me: add the marketplace adaptocms/adapto-cms-agent-skills, then install adapto@adaptocms. Once it's set up, let me know what's next.

The problem

Your agent can write the content. Can you trust it to publish it?

An LLM drafts a blog post in seconds. Then you have to check it. Does it sound like your brand or like every other model? Did it invent a stat? Is it about to push straight to your live site with nobody reading it first? Point a bare prompt at a CMS API and you find out after it ships.

Adapto Agent Skills close that gap. Your agent works from a project brain that holds your voice, audience, and glossary. It plans before it acts and leaves every piece as a draft you read. A prose gate catches the AI-tells before they reach you. The agent moves fast; you stay in control of what ships.

Adapto Agent Skills is a content studio your coding agent runs in your repo: one plugin, sixteen skills, one governed pipeline from brain to publish, writing against your Adapto project, and it never takes a step you didn't approve.

How it works

One pipeline, six moves. You approve the gates.

Install once. Then it's the same loop every cycle. Three steps stop for your sign-off.

  1. 1 Setup · once

    Brain

    adapto:project-define

    Your identity, voice, audience, pillars, and glossary. Every step downstream reads it. You build it once.

  2. 2

    Research

    adapto:content-research

    Web, competitor, and keyword research (bring your own Search Console data) into a dated dossier.

  3. 3 Approval gate

    Plan

    adapto:content-plan

    The dossier becomes a slate of per-piece briefs.

  4. 4

    Write

    adapto:content-create

    Each brief becomes an on-brand Markdown draft with SEO and AEO metadata, written by adapto-writer, critiqued by adapto-editor.

  5. 5 Approval gate

    Review

    adapto:content-upload

    You read the drafts as files, then upload pushes the approved ones to Adapto as drafts.

  6. 6 Approval gate

    Publish

    adapto:publish

    Publish takes the reviewed drafts live.

No step in this loop touches your live site on its own. Three gates stop for your approval every cycle (plan, review, publish), plus a one-time setup when you first build the brain, and the drafts sit in your repo where you can read them.

Want the full walkthrough? Read: Headless CMS for AI Agents

On-brand by construction

A project brain, so it sounds like you.

adapto:project-define. Built once, read by every skill.

You start by teaching the agent your project. A short interview plus some research builds a local brain at .adapto/project/: who you are, who you serve, your voice, your do's and don'ts, your glossary, your pillars. Every skill reads it from then on. The agent writes your content, not a generic model's guess at it.

  • Voice & tone rules
  • Audience / ICPs
  • Glossary kept verbatim
  • Content pillars
  • Lives in your repo

You hold the gates

Plan first. Draft first. Publish on purpose.

It shows its work before it does the work.

Every skill prints a plan and waits before it touches anything. Content lands as a reviewable Markdown draft in your repo, not in the CMS, and never on your live site. Publishing is a step you run yourself. Schema changes are idempotent and drift-guarded, so re-running is safe and a backoffice edit never gets clobbered.

  • Plan before every write
  • Drafts you read as files
  • A separate publish step
  • Drift-guarded
  • Idempotent re-runs

The part most tools skip

Anti-slop by construction.

On-brand content still has to not read like AI.

Every draft passes a deterministic prose-standards gate (em dashes, filler, formulaic contrasts, and the rest of the AI-tell ban-list) and an adapto-editor critique for voice, structure, and completeness before it reaches you. Translations run at the top model tier through a structural-parity gate that blocks lost paragraphs, dropped markup, and mangled placeholders. You spend your time approving, not rewriting.

  • Prose-standards gate
  • Editor critique loop
  • Structural-parity translation
  • Top-tier translation only

Every feature, on every plan

Your agent isn't driving a toy.

Every Adapto feature is here, on every plan, including free. The skills just put it in your agent's hands.

  • Custom Collections

    Model any content shape: testimonials, team, products, case studies. You set the fields; the API serves them.

  • Articles, Pages & Categories

    The built-in content types most sites need, ready the day you sign up.

  • Bundled Media CDN

    Every upload serves from media.adaptocms.com. No S3 bucket, no Cloudinary invoice.

  • Image transforms by URL

    Append ?w=800&format=webp to any image. Resize and convert at the edge, no build step.

  • i18n, unlimited

    Ship every language you need. No per-locale charge, no phase two.

  • Microcopies

    Button labels, errors, and tooltips your content team edits without a deploy.

  • Webhooks & GitHub Actions

    Fire a rebuild or a cache purge the moment you publish. Plug into n8n, Zapier, or any endpoint.

  • Custom roles

    Real permissions on every plan. Add a client editor without a re-quote.

  • Asset library

    Upload once, reuse across every project, served from the CDN.

  • REST API + TypeScript SDK

    Framework-agnostic. Works with a single fetch(), or the typed SDK if you want it.

  • Agent-ready CLI

    A write-capable, schema-aware CLI your agent or your terminal drives directly.

  • Flat-rate pricing

    Every feature on every tier, including free. You scale on usage, not capability.

Plus a 99.9% uptime SLA and a fully managed backend: no servers to patch, no plugins to break. See the full feature list

This is you if

  • You build in Claude Code and want the content produced, not just the schema modeled.
  • You've pointed an LLM at a CMS API and got off-brand copy you had to rewrite.
  • You want an agent's speed with a review gate. Nothing live until you say so.
  • You ship content-driven sites and would rather approve drafts than write them from scratch.

Questions and answers

Pricing, features, limits, migrations, and what happens when your usage grows. If your question isn't here, reach out to us at contact@adaptocms.com

Do I have to use AI agents?
No. The adapto CLI and REST API do everything the skills do, for a human or any other agent. The plugin is the Claude-Code-native way to run the same workflow.
Will it go off-brand?
The project brain and the adapto-editor gate exist for exactly that, and you review every draft as a file before anything uploads. On-brand is the default, not a hope.
Does it publish to my live site on its own?
No. Content lands as a draft; adapto:publish is a separate step you run yourself.
Which frameworks?
Astro, Next.js, and SvelteKit, the stacks create-adapto-app scaffolds.
What does it cost?
The plugin is free and open. You need an Adapto project, and the free tier is enough to run the whole loop.
Is it production-ready?
It's early access and improving fast. The pipeline runs end to end today, which is the demo. Expect rough edges, and tell us what breaks.

Let your agent run the studio.

Install the plugin, point it at a free Adapto project, watch it ship a draft you approve.

Install in Claude Code
Hey Claude, install the Adapto plugin for me: add the marketplace adaptocms/adapto-cms-agent-skills, then install adapto@adaptocms. Once it's set up, let me know what's next.