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: MIT5metadata:6 author: microsoft7 version: "1.0.0"8 source: https://github.com/microsoft/skills9---1011# Microsoft Skills1213## Overview1415Use 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.1617Compatibility: Azure SDK, .NET, Java, MCP servers, custom agents, and agent instruction files.1819## Workflow20211. Identify the SDK family, target language, package versions, authentication model, and Azure service.222. Read the relevant upstream skill or agent instructions before applying service-specific patterns.233. Prefer official SDK APIs and examples over hand-rolled REST calls unless the SDK lacks coverage.244. Validate with language-native tooling: `dotnet build/test` for .NET and Maven or Gradle tests for Java.255. Document service prerequisites, identity permissions, and environment variables separately from source changes.2627## Guardrails2829- Do not assume Azure credentials, subscriptions, or cloud resources are available locally.30- Keep secret values out of code, generated docs, and command output.31- Match the repository's existing SDK major versions and dependency management approach.32- For migrations, preserve client behavior and retry/error handling semantics.3334## Expected Output3536Return SDK-grounded implementation guidance with package choices, authentication assumptions, validation commands, and source references.
autohandai