Update to Agility CMS

{
  "description": "Explain, design or change the structure of an Agility CMS instance - content models, component models, page models, fields and containers. Use when a developer or architect asks how content is structured, wants to add or change a field, create a new model or container, or plan a content architecture.",
  "included_files": [],
  "name": "content-modeling",
  "skill_md_contents": "---\nname: content-modeling\ndescription: Explain, design or change the structure of an Agility CMS instance - content models, component models, page models, fields and containers. Use when a developer or architect asks how content is structured, wants to add or change a field, create a new model or container, or plan a content architecture.\n---\n\n# Content models, components and containers\n\n## How Agility structures content\n\n- A **content model** defines the fields of a type of content, such as Blog Post.\n- A **container** is a list of items that use one content model, such as\n  BlogPosts. Content items are saved into containers. One model can back several\n  containers.\n- A **component model** defines a module that editors place in a page zone.\n- A **page model** defines a page template and its zones.\n\nTo explain an instance, call `get_content_models`, `get_component_models`,\n`get_page_models` and `get_containers`, then `get_content_model_details` or\n`get_component_model_details` for the ones that matter. Describe how they connect:\nwhich containers use which model, and which fields link to other content.\n\n## Changing a model: read, modify, save the whole thing\n\n1. Read the model with `get_content_model_details` (or\n   `get_component_model_details`).\n2. Change only what the user asked for.\n3. Save the **complete** model: every field, with every setting it had. A save\n   replaces each field's settings, so a setting you leave out is removed.\n4. Read the model again and confirm the change and that the other fields are\n   unchanged.\n\nUse `save_component_model` for components and `save_content_model` for content\nmodels. They take the same shape, but are not interchangeable: saving a component\nthrough `save_content_model` converts it and orphans its content.\n\nChanging or removing a field on a model that already has content affects every\nitem using it. Say this before saving, and say which containers use the model.\n\n## Creating new models and containers\n\n- Check the existing models (`get_content_models`, `get_component_models`) and\n  containers (`get_containers`) first. Reuse or extend before creating.\n- There is no tool to delete a model. A model created by mistake stays in the\n  instance. Confirm the name, reference name and fields with the user before the\n  first save.\n- After creating a content model, create a container for it with `save_container`\n  so editors can add items.\n\n## Field rules\n\n- Linked-content fields (fields that point at other content) do not have\n  `required`, `unique` or \"copy across all languages\" settings in Agility. Do not\n  add them.\n- Field reference names must be unique within the model. Keep the casing\n  consistent; developers' code reads these names.\n- Prefer clear, stable reference names. Renaming a field later breaks the code\n  that reads it. Avoid all-caps abbreviations: the Fetch API lowercases only the\n  first letter, so `URL` arrives as `uRL`. Use `Url` and `Cta` instead.\n- Reference names can be normalized when a container or model is created. After\n  saving, take the name from the save result or from `get_containers`, not from\n  what you asked for.\n- Hide-when (conditional visibility) formulas support only `[eq]`, `[ne]`,\n  `[lt]` and `[gt]`. Anything else fails silently.\n- Single-item containers cannot be created with these tools. Create them in the\n  Agility app, or use a one-item list.\n- Saving a page model with a zone left out removes that zone and the components\n  placed in it. Send every zone.\n\n## Look up the platform docs\n\nFor exact field-type names and settings, search Agility's documentation (the\nAgility Knowledgebase MCP's `search_docs` and `fetch_doc`, if connected, or\nhttps://agilitycms.com/docs) rather than guessing.\n\n## When the user asks for code\n\nThese tools change the CMS, not a codebase. For front-end code, explain the model\nstructure the code will receive, and point developers to the Agility CMS\ndocumentation at https://agilitycms.com/docs for SDK details.\n"
}