Strategy for adding SDK references from microsoft/skills into plugin skills using the Hybrid Inline approach.
Skills are sandboxed — a skill's SKILL.md can only reference files within its own folder tree. Cross-skill file references do not work per the agentskills.io specification. Plugin skills (e.g., azure-storage, azure-ai) need SDK code patterns from microsoft/skills source skills (e.g., azure-storage-blob-py, azure-search-documents-ts) but cannot link to them directly.
Proposal to reorganize 133 flat skills in
microsoft/skillsinto curated plugin bundles for improved discoverability and install experience.
The current structure places all 133 skills in a single .github/skills/ directory. When users run npx skills add microsoft/skills, every skill appears in one flat list — a Python developer scrolls past Java, Rust, and .NET skills they will never use. Discovery is poor, installation is all-or-nothing, and the list will only grow.
Based on the Condensed SDK Reference Process (Hybrid Inline).
Target repo:
githubcopilotforAzure/plugin/skillsSource repo:microsoft-skills/.github/pluginsSource path structure (by language plugin):
Plugin Source path
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.
Create an event-driven function app to process messages and deploy to Azure Functions using my current subscription in eastus2 region.
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
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?
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):
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"