Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →microsoftdocs/azure-stack-edge
Expert knowledge for Azure Stack Edge development including troubleshooting, best practices, decision making, limits & quotas, security, configuration, integrations & coding patterns, and deployment.
Passed 24 of 24 test cases with the skill, and 4 of 24 without it.
and 19 more in the full report
21 fixed4 passed either way0 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 20 test cases the skill fixed. Same model, same prompt, with and without the skill.
When looking up technical documentation on Microsoft Learn for Azure Stack Edge, which tool should be preferentially used to fetch Markdown content, and what fallback tool should be used if the primary tool is missing? Provide both tool names.
| Checked | Without skill | With skill |
|---|---|---|
| Identifies mcp_microsoftdocs:microsoft_docs_fetch as preferred tool | Missed | Passed |
| Identifies fetch_webpage as fallback tool | Missed | Passed |
The instructions your model reads when the skill loads.
This skill provides expert guidance for Azure Stack Edge. Covers troubleshooting, best practices, decision making, limits & quotas, security, configuration, integrations & coding patterns, and deployment. It combines local quick-reference content with remote documentation fetching capabilities.
IMPORTANT for Agent: Use the Category Index below to locate relevant sections. For categories with line ranges (e.g.,
L35-L120), useread_filewith the specified lines. For categories with file links (e.g.,[security.md](security.md)), useread_fileon the linked reference file
IMPORTANT for Agent: If
metadata.generated_atis more than 3 months old, suggest the user pull the latest version from the repository. Ifmcp_microsoftdocstools are not available, suggest the user install it: Installation Guide
This skill requires network access to fetch documentation content:
mcp_microsoftdocs:microsoft_docs_fetch with query string from=learn-agent-skill. Returns Markdown.fetch_webpage with query string from=learn-agent-skill&accept=text/markdown. Returns Markdown.| Category | Lines | Description |
|---|---|---|
| Troubleshooting | L36-L87 | Release-specific known issues, alerts, and fixes for Azure Stack Edge/Data Box Gateway, plus troubleshooting for ordering, activation, certificates, ARM, storage, IoT Edge, VMs, GPU, diagnostics, and logs. |
| Best Practices | L88-L93 | Best practices for Azure Stack Edge Pro: device failure recovery, GPU sharing/partitioning guidance, and operational guidelines for deployment, monitoring, and maintenance. |
| Decision Making | L94-L102 | Guidance on region and data-location choices, resiliency behavior, disconnected deployment planning, and processes for replacing Azure Stack Edge devices. |
| Limits & Quotas | L103-L115 | Limits, capacities, performance, and system requirements for Azure Stack Edge and Data Box Gateway devices, including supported VM sizes, GPU limits, and cross-subscription resource moves. |
| Security | L116-L142 | Securing Azure Stack Edge: user access, certificates/TLS, Key Vault secrets, VPN/BCDR, encryption, secure wipe, Kubernetes RBAC, and built-in security features/policies. |
| Configuration | L143-L195 | Configuring and managing Azure Stack Edge/Data Box Gateway devices: networking, power, storage, Kubernetes/VMs, GPUs, monitoring, automation, and hardware/system requirements. |
| Integrations & Coding Patterns | L196-L207 | How to deploy and integrate workloads on Azure Stack Edge: IoT Edge modules, GPU-sharing/Kubernetes apps, DeepStream, Arc/Kubernetes GitOps, and connecting to local ARM. |
| Deployment | L208-L211 | Predeployment requirements and planning for Azure Stack Edge Pro GPU, including hardware, networking, certificates, capacity, and environment checks before deployment. |
test cases passed, vs 4 / 24 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.