What problem does it solve? Agents and addons often have read-only access to a REDAXO installation but still need to change content. This Skill explains how to submit change proposals (Änderungswünsche) that only take effect after an editor approves them, covering the agent tools, the PHP API, and the REST endpoints. ## Core Features & Use Cases - Three submission paths: Use the agent tools (redaxo_describe_change_types, redaxo_read_current, redaxo_propose_change), the PHP ChangeService, or the seven scoped REST routes under /api/ai_platform/changes. - Six change types: Propose updates, creates, and deletions for slices, articles, categories, metainfo, media (with staged uploads), and YForm datasets, with batching and changesets for grouped approval. - Custom change types: Register new Target, Payload, and Handler classes via the AI_PLATFORM_CHANGE_HANDLERS extension point without touching core files. - Use Case: An SEO agent without write access proposes corrected headings across 40 articles as one changeset; an editor reviews the diff and approves all of them with a single action. ## Quick Start Ask the agent to call redaxo_describe_change_types first, then read the current state of the target and submit a proposal with a clear reason for the editor.
