<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>High Availability on Top AI Skills</title><link>https://topaiskills.com/tags/high-availability/</link><description>Recent content in High Availability on Top AI Skills</description><generator>Hugo</generator><language>en</language><lastBuildDate>Fri, 18 Sep 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://topaiskills.com/tags/high-availability/index.xml" rel="self" type="application/rss+xml"/><item><title>I Ran Azure's Reliability Checks and Its Multi-Region Query Missed Its Own Setup</title><link>https://topaiskills.com/tutorials/guides/azure-reliability-narrative-experience/</link><pubDate>Fri, 18 Sep 2026 00:00:00 +0000</pubDate><guid>https://topaiskills.com/tutorials/guides/azure-reliability-narrative-experience/</guid><description>&lt;p&gt;I spent the morning walking Microsoft&amp;rsquo;s &lt;code&gt;azure-reliability&lt;/code&gt; skill (v1.1.1) end to end — reading all 12 reference files, then stress-testing its queries against its own example resource names. The skill promises an assessment you can act on, and the assessment machinery is genuinely thoughtful. But I found its multi-region detection query fails on the exact naming pattern the skill&amp;rsquo;s own CLI setup generates. 268,656 installs, rank 218 on skills.sh as of 2026-09-18, weekly curve [16828, 16060, 15873, 14817, 13263, 13449, 11966, 12666] — the same pack-level lockstep signature as the rest of microsoft/azure-skills.&lt;/p&gt;</description></item></channel></rss>