Summary

This skill provides expert guidance for Azure IoT Edge development, including troubleshooting, best practices, architecture patterns, security, configuration, integrations, and deployment. It functions as a reference index that directs agents to fetch Microsoft Learn documentation via network-based tools (mcp_microsoftdocs or fetch_webpage), supplemented by a comprehensive category-based navigation structure with line-range references and direct URLs to official Microsoft documentation.

Detected Capabilities

Trigger Keywords

Phrases that MCP clients use to match this skill to user intent.

Risk Signals

Referenced Domains

External domains referenced in skill content, detected by static analysis.

Use Cases

• .com/en-us/azure/iot-edge/how-to-troubleshoot-monitoring-and-faq
• Troubleshoot Azure IoT Edge runtime errors, monitoring issues, and EFLOW networking problems
• Configure IoT Edge devices with DPS provisioning, X.509 certificates, and TPM-based authentication
• Design gateway patterns for downstream device connectivity and offline operation scenarios
• Deploy IoT Edge modules at scale using CI/CD pipelines and Azure CLI manifests
• Set up confidential computing and security hardening for production IoT Edge deployments
• Configure EFLOW (IoT Edge for Linux on Windows) with networking, GPU acceleration, and metrics collection
• Manage nested IoT Edge device hierarchies and transparent gateway topologies

Quality Notes

• Strengths: Well-organized category index with clear line ranges and descriptive topic titles. Comprehensive coverage of IoT Edge domains (troubleshooting, security, configuration, deployment). Explicit instructions for agents on how to use reference files and when to fetch remote docs. Clear distinction between local reference and remote content. Fallback strategy documented (mcp_microsoftdocs preferred, fetch_webpage as fallback). Helpful metadata check (generated_at timestamp) prompts users to update outdated versions.
• Strengths: URLs are specific and authoritative (all point to learn.microsoft.com/en-us/azure/iot-edge). Category descriptions are concise and actionable. Scope boundaries are clear (explicitly excludes Azure IoT Hub, Central, Operations, Stack Edge).
• Weaknesses: No supporting reference files present in the directory (only LICENSE). The skill promises to direct agents to line ranges (e.g., 'L37-L47') but no corresponding .md files exist for agents to read. This breaks the documented workflow — agents will fail when instructed to 'use read_file with specified lines' on non-existent files.
• Weaknesses: No examples or sample outputs showing what a successful navigation looks like. No error handling guidance for when mcp_microsoftdocs is unavailable or network requests fail. No guidance on how agents should handle rate limiting or timeouts from Microsoft Learn fetches.
• Weaknesses: The skill is primarily a link directory with minimal local content. While this is appropriate for a reference skill, there is limited actionable guidance for common decision-making scenarios (e.g., 'When should I use DPS vs manual provisioning?'). Most value is deferred to remote docs.
• Weaknesses: No documented limitations on the scope of mcp_microsoftdocs queries or expected response formats. No guidance on handling stale or cached documentation.