Microsoft Skills
Overview
Use this skill when work needs Microsoft SDK grounding for coding agents, especially Azure SDK tasks across .NET and Java. The upstream microsoft/skills repository includes skills, MCP servers, custom agents, and agent instructions for SDK-focused development.
Compatibility: Azure SDK, .NET, Java, MCP servers, custom agents, and agent instruction files.
Workflow
- Identify the SDK family, target language, package versions, authentication model, and Azure service.
- Read the relevant upstream skill or agent instructions before applying service-specific patterns.
- Prefer official SDK APIs and examples over hand-rolled REST calls unless the SDK lacks coverage.
- Validate with language-native tooling:
dotnet build/test for .NET and Maven or Gradle tests for Java.
- Document service prerequisites, identity permissions, and environment variables separately from source changes.
Guardrails
- Do not assume Azure credentials, subscriptions, or cloud resources are available locally.
- Keep secret values out of code, generated docs, and command output.
- Match the repository's existing SDK major versions and dependency management approach.
- For migrations, preserve client behavior and retry/error handling semantics.
Expected Output
Return SDK-grounded implementation guidance with package choices, authentication assumptions, validation commands, and source references.
1---2name: microsoft-skills3description: Use microsoft/skills for Azure SDK grounding across .NET and Java agent coding workflows.4license: MIT5---67# Microsoft Skills89## Overview1011Use this skill when work needs Microsoft SDK grounding for coding agents, especially Azure SDK tasks across .NET and Java. The upstream [microsoft/skills](https://github.com/microsoft/skills) repository includes skills, MCP servers, custom agents, and agent instructions for SDK-focused development.1213Compatibility: Azure SDK, .NET, Java, MCP servers, custom agents, and agent instruction files.1415## Workflow16171. Identify the SDK family, target language, package versions, authentication model, and Azure service.182. Read the relevant upstream skill or agent instructions before applying service-specific patterns.193. Prefer official SDK APIs and examples over hand-rolled REST calls unless the SDK lacks coverage.204. Validate with language-native tooling: `dotnet build/test` for .NET and Maven or Gradle tests for Java.215. Document service prerequisites, identity permissions, and environment variables separately from source changes.2223## Guardrails2425- Do not assume Azure credentials, subscriptions, or cloud resources are available locally.26- Keep secret values out of code, generated docs, and command output.27- Match the repository's existing SDK major versions and dependency management approach.28- For migrations, preserve client behavior and retry/error handling semantics.2930## Expected Output3132Return SDK-grounded implementation guidance with package choices, authentication assumptions, validation commands, and source references.
autohandai