Systematic diagnosis and remediation for Azure production issues using AppLens, Azure Monitor, and resource health checks.
Automate repetitive workflows and reduce manual effort
Example: Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Learn new skills, understand complex topics, get expert guidance
Example: Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Enhance output quality through reviews, suggestions, and refinements
Example: Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
Time estimate: 15-45 minutes depending on use case complexity
Prerequisites
Submit your Claude Code skill and start earning
epx add microsoft/GitHub-Copilot-for-Azure --skill azure-diagnosticsCompatible with
Supported agents
Covers Container Apps, Function Apps, and AKS clusters with service-specific troubleshooting guides for image pulls, cold starts, health probes, invocation failures, and node/pod issues
Includes AppLens MCP integration for AI-powered root cause analysis and Azure Monitor MCP for KQL-based log and metric queries
Provides a five-step diagnostic flow: identify sympt
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionazure-diagnosticsExecute the skills CLI command in your project's root directory to begin installation:
epx add microsoft/GitHub-Copilot-for-Azure --skill azure-diagnosticsFetches azure-diagnostics from microsoft/GitHub-Copilot-for-Azure and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
.cursor/skills/azure-diagnostics
Restart Cursor to activate azure-diagnostics. Access via /azure-diagnosticsin your agent's command palette.
Learn more:View source on GitHubSkills CLI docsAbout CursorWhat are agent skills?
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid when
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
azure-storage
microsoft/GitHub-Copilot-for-Azure · Cloud · same repo
azure-hosted-copilot-sdk
microsoft/GitHub-Copilot-for-Azure · Cloud · same repo
azure-ai
microsoft/azure-skills · Cloud · tag: azure
azure-compliance
microsoft/azure-skills · Cloud · tag: azure
microsoft-sharepoint
membranedev/application-skills · Productivity · tag: microsoft
offensive-windows-mitigations
SnailSploit/Claude-Red · infrastructure · tag: infrastructure
azure-diagnostics fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
azure-diagnostics is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Solid pick for teams standardizing on skills: azure-diagnostics is focused, and the summary matches what you get after install.
azure-diagnostics has been reliable in day-to-day use. Documentation quality is above average for community skills.
Registry listing for azure-diagnostics matched our evaluation — installs cleanly and behaves as described in the markdown.
Registry listing for azure-diagnostics matched our evaluation — installs cleanly and behaves as described in the markdown.
Solid pick for teams standardizing on skills: azure-diagnostics is focused, and the summary matches what you get after install.
azure-diagnostics reduced setup friction for our internal harness; good balance of opinion and flexibility.
azure-diagnostics reduced setup friction for our internal harness; good balance of opinion and flexibility.
I recommend azure-diagnostics for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
showing 1-10 of 37