A practical guide to adding telemetry to your VS Code extension -- covering setup, data captured, and PII handling.
@vscode/extension-telemetry answers "what are my users doing and what's breaking?" It's built for product analytics and error monitoring -- the 80% case for extension authors.
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.
Progressive Disclosure for MicrosoftDocs/Agent-Skills via azure-skills — single azure-docs skill design with 3-tier loading
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.
Date: March 12, 2026 Scope: How
azure-prepareuses 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"
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?
There are 6 major overlap areas between azure-skills (24 operational skills) and MicrosoftDocs/Agent-Skills (193 service documentation skills):
azure-skills + MicrosoftDocs/Agent-Skills Convergence: Diagnostics & Troubleshooting Strategy
Date: March 11, 2026 Context: Should
azure-skillsreferenceMicrosoftDocs/Agent-Skillscontent? Should diagnostics be split into diagnostics + troubleshooting?
Azure Agent Skills Ecosystem: Three-Repo Analysis (githubcopilotforAzure vs microsoft/skills vs MicrosoftDocs/Agent-Skills)
Date: March 11, 2026 Scope:
azure-skills|microsoft/skills|MicrosoftDocs/Agent-SkillsPurpose: Strategic comparison, contribution flows, automation gaps, and convergence plan
Create an event-driven function app to process messages and deploy to Azure Functions using my current subscription in eastus2 region.
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.