directus-content

Installation
SKILL.md

Directus content editing

Change content in an existing Directus project: the jobs an editor does in the Studio, done through the MCP items and files tools or REST. The project's schema already exists; this skill is about writing into it without breaking relations, translations, or what's live.

Verified against Directus v12.6.0 (api/src/ai/tools, api/src/services) and live instances.

First checks

  1. Version. GET /server/info returns data.version. Older than 12.6: read the version notes for its major in the directus skill (references/versions-v<major>.md).
  2. Read the schema for what you'll touch. MCP: schema({ keys: ["pages"] }). Note required fields, the status field's choices, which fields are relations, and each text field's interface.
  3. Find the item by what the user named (title, slug, permalink) with a filter. Never guess an id. Read it with the fields you're about to change, including the ids of related rows.
  4. Versioned collection (meta.versioning: true)? Ask whether the change should go live now. See the first trap.
  5. The tools run as the connected user. A 403 means that user can't do it. Say so; don't look for another way in.
Installs
17
GitHub Stars
6
First Seen
13 days ago