Update to Misar.Blog

{
  "description": "Audit and improve an existing Misar.Blog article for SEO, AEO, and AI-answer-engine citability. Use for \"improve SEO\", \"why isn't this ranking\", \"meta description\", or \"optimise for AI search\".",
  "included_files": [],
  "name": "seo-optimize-article",
  "skill_md_contents": "---\nname: seo-optimize-article\ndescription: Audit and improve an existing Misar.Blog article for SEO, AEO, and AI-answer-engine citability. Use for \"improve SEO\", \"why isn't this ranking\", \"meta description\", or \"optimise for AI search\".\n---\n\n# Optimise an article\n\n## Read the actual article first\n\n`get_article` by slug. Auditing from the title alone produces generic advice\nthat applies to any post and helps none.\n\n## Audit\n\nReport an SEO score out of 100 **with the reasoning**, then:\n\n- **Keywords** the piece should rank for but never mentions.\n- **Title** — rewritten, under 60 characters, keyword near the front.\n- **Meta description** — rewritten, under 155 characters, written to earn the\n  click rather than to summarise.\n- **Internal links** — use `search_articles` to find *real* published articles\n  to link to. Never invent a URL; a broken internal link is worse than none.\n- **Structure** — headings that pose the question a reader searched for.\n\n## AI answer engines (AEO/GEO)\n\nDistinct from classic SEO and increasingly where the traffic goes:\n\n- Answer the title's question directly in the first paragraph. Engines quote\n  self-contained passages; a piece that builds to its answer never gets cited.\n- Keep each section independently comprehensible — a passage lifted out of\n  context must still make sense.\n- Use concrete specifics (numbers, versions, dates). Vague claims do not get\n  quoted.\n\n## Apply\n\n`update_article` — but ask before changing anything. A title change on a\nranking article can lose position, so flag that trade-off explicitly when the\narticle already gets traffic.\n"
}