<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Container Apps on Top AI Skills</title><link>https://topaiskills.com/tags/container-apps/</link><description>Recent content in Container Apps on Top AI Skills</description><generator>Hugo</generator><language>en</language><lastBuildDate>Wed, 02 Sep 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://topaiskills.com/tags/container-apps/index.xml" rel="self" type="application/rss+xml"/><item><title>azure-cloud-migrate: Microsoft's 8-Scenario Migration Skill</title><link>https://topaiskills.com/skills/automation/azure-cloud-migrate/</link><pubDate>Wed, 02 Sep 2026 00:00:00 +0000</pubDate><guid>https://topaiskills.com/skills/automation/azure-cloud-migrate/</guid><description>&lt;p&gt;Migrate a Lambda function to Azure and most agents start rewriting handler code from memory. Microsoft&amp;rsquo;s azure-cloud-migrate skill does the opposite: it demands an assessment report &lt;em&gt;before&lt;/em&gt; any code conversion, then routes you into one of eight scenario-specific guides. I read the current SKILL.md (v1.3.2, MIT) plus the full 37-file reference tree — three service families, per-runtime migration rules, and a progress-tracking convention — then pulled install numbers from the skills.sh leaderboard on 2026-09-02.&lt;/p&gt;</description></item></channel></rss>