Adapto publish

Skill adaptocms/adapto-cms-agent-skills/plugin/skills/adapto-publish

A pack of skills for AI coding agents (Claude Code, Cursor) that lets them operate Adapto CMS end-to-end: scaffold projects, design schemas, seed content, translate, run SEO, audit content, roll back.

Install

npx -y skills add adaptocms/adapto-cms-agent-skills --skill adapto-publish

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Take reviewed draft content live — publish Articles, Pages, and collection items (draft → published), or archive them back (published → archived). Discovers drafts, you select, then it publishes under plan-then-apply. Closes the draft-first loop.

SKILL.md

5.8 KB, as published. Nobody here has run it

adapto:publish

The terminal step of the draft-first loop: every other skill writes draft content; this one takes the reviewed drafts live (draft → published), or archives them back (published → archived) as a walk-back. It's stateless — it discovers what's publishable rather than remembering a session.

When to use

"Publish", "publish my drafts", "take it live", "go live", "unpublish/archive this" — typically after reviewing the seeded/translated drafts on the dev server.

When not to use

Creating or editing content → the content pipeline (content-create → content-upload) or adapto:translate.
Just checking the environment → adapto:doctor.

Inputs

Mode: publish (default) or archive (the inverse / walk-back).
Optional filters: type (Articles / Pages / collection items), language, or a specific collection / item set.
Collections enumerated from .adapto/schema.json (if present) or adapto collections list --json.

Outputs

The selected Articles / Pages / collection items moved draft → published (or published → archived).
The ledger updated (acted-on pieces → published) and .adapto/calendar.md refreshed.
A report of acted-on + skipped, with ids.
Next step: the cycle is complete — suggest the next content cycle (adapto:content-research) or adapto:translate to localize what just went live.

Preconditions

Preflight with the adapto:doctor checks.
Hard-block on an authenticated CLI (adapto auth me) and a selected tenant — this skill writes. Confirm the working tenant first; never assume the active one.
adapto CLI >= 0.1.3.

Plan phase

Discover candidates in the relevant status (publish → draft; archive → published):

adapto articles list --status draft --json [--language <lang>]
adapto pages list --status draft --json [--language <lang>]
adapto collections list --json                                  # enumerate collections (or read .adapto/schema.json)
adapto collections items list <collection_id> --status draft --json

Present them as type · title · slug · language · status.
Let the user select — all or a subset (by type, language, or specific items). "Publish everything I just seeded" = select all; targeted = pick a few.
Print a machine-parseable plan: the exact set to act on (count, per type, titles/slugs, languages) and the transition (draft → published or published → archived). List items already in the target state as skipped. Wait for an explicit approve. No cost/token figures. Nothing to act on → say so and stop.

Apply phase

Runs only after approval. Per-item loop (no batch on publish); --json on each. Verified verbs:

# publish (draft → published)
adapto articles publish <id> --json
adapto pages publish <id> --json
adapto collections items publish <collection_id> <item_id> --json
# archive (published → archived) — the walk-back
adapto articles archive <id> --json
adapto pages archive <id> --json
adapto collections items archive <collection_id> <item_id> --json

Idempotent: skip items already in the target state (re-publishing a published item is a no-op skip).
Partial failure: report what was acted on, then stop; re-running is safe.
Collection items require iterating collections (per-collection items list then per-item publish).
Report acted-on + skipped, with ids. ⚠️ articles/pages publish (and archive) print a plain-text confirmation (e.g. Article published.) rather than JSON, even with --json — so judge success by the absence of an error plus a follow-up <type> get <id> --json status check (status: published), not by JSON-parsing the publish output. (Collection-item publish does return JSON.) Never rely on the shell exit code; end the loop exit 0 on success so a clean batch never shows a red Error: Exit code 1 (§8).
Update the ledger. For each acted-on piece tracked in .adapto/ledger.json, set its status → published (or back to its prior state on archive) and refresh .adapto/calendar.md. (Items not in the ledger — e.g. backoffice-created — simply aren't tracked; that's fine.)
Then restart the dev server (stop→start) and keep it running so the now-published content appears — never kill it (starters sync content at startup — §14).

Errors and recovery

No candidates in the requested status → say so; suggest adapto:content-seed / adapto:translate first (publish mode), or note nothing is published yet (archive mode).
Item already in the target state → skip (idempotent); report it, don't error.
Partial failure mid-loop (no batch on publish) → report what was acted on, then stop; re-run is safe.
Not authenticated / no tenant → stop; offer both auth paths — Log in or Register (conventions.md §11) — then tenant selection.

Forbidden actions

Never publish without an approved plan (plan-then-apply) — publishing makes content live.
Never assume the working tenant — confirm it before any write.
Never modify the scaffolded read-client (forbidden-actions.md).