@latellu/atlas-agent-skills 0.3.0 → 0.3.1

package/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "atlas",
-  "version": "0.3.0",
+  "version": "0.3.1",
   "description": "Work with Atlas CMS from Claude Code: bundles the Atlas MCP server (read/write content via tools) and the atlas-cms skill that teaches agents when and how to use the MCP tools, the @latellu/atlas-sdk delivery/management clients, and the @latellu/atlas-cli type generator.",
   "author": {
     "name": "Latellu",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@latellu/atlas-agent-skills",
-  "version": "0.3.0",
+  "version": "0.3.1",
   "description": "Agent skill + MCP configuration for Atlas CMS. Works as a Claude Code plugin and as plain markdown guidance for any AI coding agent (Cursor, Codex, opencode, Gemini CLI, ...).",
   "license": "MIT",
   "author": "Latellu (https://github.com/tenriajeng)",

package/skills/atlas-cms/references/authoring.md

@@ -113,6 +113,14 @@ The real write shape (`POST/PUT /pages`) differs from what the reading API shows
 - MCP `create_page`/`update_page` extra caveats: the `title` argument is ignored by the
   backend (set `seo.title`), `seo` there accepts only `title`/`description`, and block
   `translations`/`seo_translations` aren't expressible.
+- **A page without blocks cannot be published** — publish returns an error requiring at
+  least one block. Combined with `block_type_id` being undiscoverable, an API-only
+  workflow can create and edit pages but **never publish a new one**; publishing needs
+  someone to add a block in the dashboard first (or block-type UUIDs supplied to you).
+- **The write plane has no reads**, and write responses don't echo `seo_translations` —
+  you cannot fully verify a translation write without a live key for the same workspace.
+  Trick: `PUT /pages/:slug` with body `{}` is a safe no-op that returns the page's
+  current base state (status + seo) — the only "read" available on the management plane.
 
 ## Practical write checklist
 

package/skills/atlas-cms/references/mcp.md

@@ -108,3 +108,7 @@ matters double here because MCP swallows per-field validation errors.
   actually landed (e.g. `get_entry`) before retrying creates.
 - One MCP server = one workspace (the key's). Multi-workspace work needs one server
   registration per workspace.
+- **The server never checks that the live and mgmt keys belong to the same workspace.**
+  A mismatched pair is maximally confusing: schema and reads come from workspace A while
+  every write 404s ("content type not found") against workspace B. If reads succeed but
+  writes 404 on types you just listed, suspect mismatched keys before anything else.

package/skills/atlas-cms/references/sdk-management.md

@@ -67,7 +67,7 @@ All idOrSlug parameters accept either the entry ID or its slug.
 // (seo_translations, block translations, nesting) and the block_type_id caveat.
 await client.pages.create({ slug: "landing", seo: { title: "Landing" }, blocks: [...] });
 await client.pages.update("landing", { seo: { title: "Landing v2" } });
-await client.pages.publish("landing");
+await client.pages.publish("landing");   // fails unless the page has ≥1 block — see authoring.md
 await client.pages.unpublish("landing");   // pages have the FULL lifecycle here
 await client.pages.archive("landing");     //   (unlike the MCP tools)
 await client.pages.schedule("landing", "2026-08-01T09:00:00Z");