kvenkatrajan

PR #1244 Review: azure-infra-planner skill

High-Level Suggestions

1. Rename to azure-enterprise-infra-planner

azure-prepare plans infrastructure by analyzing source code and mapping it to one of 5 host types (containerapp, appservice, function, staticwebapp, aks). It has no logic to plan the remaining 43 resource types in this skill — VNets, Firewalls, VPN Gateways, VMs, Service Bus, Key Vault, etc. It cannot look at a workload description and decide "you need a hub-spoke VNet with NSGs and a Firewall."

This skill fills that gap: infrastructure-first planning for platform engineers, where the input is a workload description (not code) and the output covers all 48 resource types. Renaming to azure-enterprise-infra-planner makes this distinction clear.

kvenkatrajan

Progressive Disclosure for MicrosoftDocs/Agent-Skills via azure-skills — single azure-docs skill design with 3-tier loading

Progressive Disclosure for MicrosoftDocs/Agent-Skills

Date: March 12, 2026 Problem: Agent-Skills has 193 service skills, each 100-850 lines. Loading them all is impossible. Loading even one full skill (e.g., Azure Functions at 366 lines / ~135 links) wastes tokens when the user only needs one category. Solution: Restructure Agent-Skills into a three-tier progressive disclosure model with a single router SKILL.md, per-service reference files, and on-demand Microsoft Learn fetching.

---

kvenkatrajan

azure-prepare: Progressive Disclosure Flow

Date: March 12, 2026 Scope: How azure-prepare uses recipes, runtimes, and service references through progressive disclosure Walkthrough prompt: "Create a Node.js Express API with Cosmos DB that I can deploy to Azure Container Apps"

---

1. What Is Progressive Disclosure in azure-prepare?

kvenkatrajan

azure-skills + MicrosoftDocs/Agent-Skills: Full Overlap Analysis

Date: March 11, 2026 Context: Beyond diagnostics/troubleshooting, where else do azure-skills and Agent-Skills overlap? What content from Agent-Skills should azure-skills reference?

---

1. Overlap Map Summary

There are 6 major overlap areas between azure-skills (24 operational skills) and MicrosoftDocs/Agent-Skills (193 service documentation skills):

kvenkatrajan

azure-skills + MicrosoftDocs/Agent-Skills Convergence: Diagnostics & Troubleshooting Strategy

azure-skills + MicrosoftDocs/Agent-Skills Convergence: Diagnostics & Troubleshooting

Date: March 11, 2026 Context: Should azure-skills reference MicrosoftDocs/Agent-Skills content? Should diagnostics be split into diagnostics + troubleshooting?

---

1. The Problem Today

kvenkatrajan

Azure Agent Skills Ecosystem: Three-Repo Analysis (githubcopilotforAzure vs microsoft/skills vs MicrosoftDocs/Agent-Skills)

Azure Agent Skills Ecosystem: Three-Repo Analysis

Date: March 11, 2026 Scope: azure-skills | microsoft/skills | MicrosoftDocs/Agent-Skills Purpose: Strategic comparison, contribution flows, automation gaps, and convergence plan

---

kvenkatrajan

Test comments

⚠️ azure-deploy skill was expected to be used but was not used. ⚠️ azure-validate skill was expected to be used but was not used. ⚠️ azure-prepare skill was expected to be used but was not used.

User Prompt

Create an event-driven function app to process messages and deploy to Azure Functions using my current subscription in eastus2 region.

kvenkatrajan

AI Initiatives Communication Plan

Problem

AI initiatives across the org lack a unified communication mechanism, leading to siloed awareness and limited cross-team collaboration. Teams working on Copilot CLI, Copilot SDK, VSCode, and other AI efforts need a structured way to share updates, learnings, and collaborate.

Goals

• Awareness: Keep all teams informed of AI progress, releases, and learnings
• Collaboration: Drive cross-team contribution and reduce duplication
• Discoverability: Make AI resources, investments, and knowledge easy to find

kvenkatrajan

Why Azure Skills Invoke Unreliably in Claude Sonnet vs Opus 4.6

Analysis of skill description patterns across 24 Azure skills, with concrete recommendations for improving invocation reliability on Sonnet.

---

5 Root Causes (in order of impact)

1. Description Length Overload

kvenkatrajan

Condensed SDK Reference — Change Analysis

Based on the Condensed SDK Reference Process (Hybrid Inline).

Target repo: githubcopilotforAzure/plugin/skills Source repo: microsoft-skills/.github/plugins

Source path structure (by language plugin):

Plugin	Source path