Update to Agility CMS

{
  "description": "Write and stage a blog post, news article, announcement, case study or guide in Agility CMS from a topic or brief. Use when the user asks to write, draft or post an article or blog post. Covers finding the right list, filling author, category and tag fields, the body, an image, the excerpt and SEO description, saving as a draft, and translating.",
  "included_files": [],
  "name": "write-article",
  "skill_md_contents": "---\nname: write-article\ndescription: Write and stage a blog post, news article, announcement, case study or guide in Agility CMS from a topic or brief. Use when the user asks to write, draft or post an article or blog post. Covers finding the right list, filling author, category and tag fields, the body, an image, the excerpt and SEO description, saving as a draft, and translating.\n---\n\n# Write an article in Agility CMS\n\nAn article is a content item in a list such as BlogPosts or News. This skill\ncovers the whole job; the rules for saving fields come from the `edit-content`\nskill, and the voice from the `brand-voice` skill.\n\n## 1. Gather the brief\n\nBefore writing, know:\n\n- the topic, the audience and the one point the article must make\n- the facts to use (a release note, a product page, the user's notes). Do not\n  invent facts, numbers, customer names or quotes. If something is missing, ask\n  or leave a clearly marked placeholder.\n- the brand guidelines, if the user has them (see `brand-voice`)\n- an image: a file the user provides, or an asset already in Agility\n\n## 2. Find where articles live\n\n1. Confirm the instance and locale.\n2. Call `get_containers` and pick the article list. If several could fit\n   (BlogPosts, News, Resources), ask.\n3. Call `get_content_model_details` for its model. Note the body field (rich\n   text or Markdown), the slug, excerpt, image, author, category and tag fields,\n   and which are required.\n4. Read one or two recent articles with `get_content_items` and\n   `get_content_item` to copy how fields are actually used: body format, slug\n   style, excerpt length, how many tags.\n\n## 3. Resolve linked fields to real IDs\n\nAuthor, category and tags are usually links to other lists. Find the IDs with\n`get_content_items` on those lists (or `search_instance`) and use the companion\nfield names shown in the model (for example `Author_ValueField` and\n`Author_TextField`). Use existing categories and tags. Do not create new ones\nunless the user asks.\n\n## 4. Write\n\n- A headline that says what the reader gets, then a body that leads with the\n  point. Use the body format the model expects: HTML for rich text, Markdown for\n  a Markdown field. Use headings for anything longer than a few paragraphs.\n- A slug from the headline: lowercase, hyphens, no dates unless the site uses\n  them.\n- An excerpt of one or two sentences, plain text. Reuse it as the SEO meta\n  description if the item has SEO fields (140 to 160 characters works best).\n- Links inside the site use the `~/` prefix, for example `~/products`.\n\n## 5. Image\n\nUse an asset from `list_media`, or upload the user's file with\n`initialize_media_upload` and use the URL it returns. Give it real alt text in\n`label`.\n\n## 6. Save and check\n\n1. `save_content_items` with `contentID: -1`, every field, and\n   `releaseDate: null`, `pullDate: null`.\n2. Read it back with `get_content_item` and check the body, links and image.\n3. Give the user the editor link and a short summary: title, slug, author,\n   category, tags, and anything left as a placeholder. Say it is a draft.\n\nPublish only if the user asks, using the `publish-and-workflow` skill.\n\n## Translations\n\nIf the user wants other languages, translate after the original is approved.\nSave each translation in its locale with the same container, keep the slug\nconsistent with the site's convention, and do not translate IDs, URLs or code.\nReport each locale's result.\n"
}