What problem does it solve? Updating Weegloo documents over the CMA and ACMA REST APIs often means choosing between PUT and PATCH, and sending full resource bodies when only a few fields changed wastes bandwidth and risks overwriting unrelated data. This Skill provides clear guidance on when and how to use HTTP PATCH with RFC 6902 JSON Patch for smaller, safer partial updates. ## Core Features & Use Cases - PATCH-first update strategy: Default to HTTP PATCH with JSON Patch operations (add, remove, replace, move, copy, test) so only the changed paths are transmitted. - Correct protocol usage: Enforces the mandatory Content-Type: application/json-patch+json header and JSON Pointer (RFC 6901) paths for patch operations. - API-plane awareness: Clarifies which resources accept PATCH on each plane — ContentType, Content, and Media on CMA, but Content only on ACMA (ACMA Media has no update endpoint). - Use Case: When writing an HTTP client that updates a single field of a Weegloo Content entry, use this Skill to construct a minimal JSON Patch body instead of re-sending the entire document with PUT. ## Quick Start Ask the agent to update one field of a Weegloo Content document using an RFC 6902 JSON Patch request against the CMA API.
