azure-firmware-analysis — Claude Code skill for firmware analysis
This Claude Code skill guides development tasks for Azure Firmware Analysis. It covers firmware findings, access controls, upload automation, and workspace deployment.
CC-BY-4.0 175 installs ★ 818 updated 2026-11-09
npx skills add MicrosoftDocs/Agent-Skills --skill azure-firmware-analysis -a claude-codeWhat azure-firmware-analysis does
The skill covers troubleshooting failed uploads or scans, reading SBOM paths and CVE or weakness data, and configuring RBAC with service principals. It also describes Azure Device Registry integration and firmware uploads through CLI, PowerShell, or Python.
Workspace deployment guidance covers ARM templates, Bicep, and Terraform. The skill pairs local reference material with Microsoft documentation fetched remotely. Network access is required, along with either mcp_microsoftdocs:microsoft_docs_fetch or fetch_webpage; without a connection, remote documentation cannot be retrieved.
What it helps with
- diagnose a failed firmware upload or scan
- interpret SBOM paths and CVE findings
- configure RBAC for users and applications
- automate firmware uploads with CLI, PowerShell, or Python
- deploy a workspace with ARM templates, Bicep, or Terraform
Example prompts for the agent
- Diagnose this Azure Firmware Analysis scan failure and suggest troubleshooting steps.
- Explain how to read the SBOM paths and CVE findings for this firmware.
- Show me how to upload firmware with Python and configure RBAC for automation.
How to install azure-firmware-analysis
1Skills CLI (Vercel)
npx skills add MicrosoftDocs/Agent-Skills --skill azure-firmware-analysis -a claude-code2Manually: put the files in place
~/.claude/skills/azure-firmware-analysis/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/azure-firmware-analysis/
1Skills CLI (Vercel)
npx skills add MicrosoftDocs/Agent-Skills --skill azure-firmware-analysis -a codex2Manually: put the files in place
.agents/skills/azure-firmware-analysis/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add MicrosoftDocs/Agent-Skills --skill azure-firmware-analysis -a cursor2Manually: put the files in place
.cursor/skills/azure-firmware-analysis/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install MicrosoftDocs/Agent-Skills skills/azure-firmware-analysis2Manually: put the files in place
.github/skills/azure-firmware-analysis/SKILL.md1Skills CLI (Vercel)
npx skills add MicrosoftDocs/Agent-Skills --skill azure-firmware-analysis -a gemini-cli2Platform CLI
gemini skills install https://github.com/MicrosoftDocs/Agent-Skills --path skills/azure-firmware-analysisManually: put the files in place
.devin/skills/azure-firmware-analysis/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add MicrosoftDocs/Agent-Skills --skill azure-firmware-analysis -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about azure-firmware-analysis
How do I install azure-firmware-analysis in Claude Code?
Run npx skills add MicrosoftDocs/Agent-Skills --skill azure-firmware-analysis -a claude-code. The skill file is placed at ~/.claude/skills/azure-firmware-analysis/SKILL.md.
What does azure-firmware-analysis do?
It guides Azure Firmware Analysis development, from troubleshooting firmware scans to interpreting SBOM and CVE data, setting access controls, automating uploads, and deploying workspaces.
Does azure-firmware-analysis need network access?
Yes. It retrieves Microsoft documentation through mcp_microsoftdocs:microsoft_docs_fetch or fetch_webpage, so network access is required for those remote references.
Source text
SKILL.md · CC-BY-4.0
--- name: azure-firmware-analysis description: Expert knowledge for Azure Firmware Analysis development including troubleshooting, best practices, security, integrations & coding patterns, and deployment. Use when configuring AFA RBAC access, analyzing SBOM paths and CVEs, automating uploads, or deploying workspaces via IaC, and other Azure Firmware Analysis related development tasks. Not for Azure Defender For Iot (use azure-defender-for-iot), Azure IoT Edge (use azure-iot-edge), Azure IoT Hub (use azure-iot-hub), Azure Confidential Computing (use azure-confidential-computing). compatibility: Requires network access. Uses mcp_microsoftdocs:microsoft_docs_fetch or fetch_webpage to retrieve documentation. metadata: generated_at: "2026-11-01" generator: "docs2skills/1.0.0" --- # Azure Firmware Analysis Skill This skill provides expert guidance for Azure Firmware Analysis. Covers troubleshooting, best practices, security, integrations & coding patterns, and deployment. It combines local quick-reference content with remote documentation fetching capabilities. ## How to Use This Skill > **IMPORTANT for Agent**: Use the **Category Index** below to locate relevant sections. For categories with line ranges (e.g., `L35-L120`), use `read_file` with the specified lines. For categories with file links (e.g., `[security.md](security.md)`), use `read_file` on the linked reference file > **IMPORTANT for Agent**: If `metadata.generated_at` is more than 3 months old, suggest the user pull the latest version from the repository. If `mcp_microsoftdocs` tools are not available, suggest the user install it: [Installation Guide](https://github.com/MicrosoftDocs/mcp/blob/main/README.md) This skill requires **network access** to fetch documentation content: - **Preferred**: Use `mcp_microsoftdocs:microsoft_docs_fetch` with query string `from=learn-agent-skill`. Returns Markdown. - **Fallback**: Use `fetch_webpage` with query string `from=learn-agent-skill&accept=text/markdown`. Returns Markdown. ## Category Index | Category | Lines | Description | |----------|-------|-------------| | Troubleshooting | L33-L37 | Diagnosing and fixing common Azure Firmware Analysis issues, including job failures, upload/scan problems, and environment or configuration-related errors. | | Best Practices | L38-L45 | Best practices for interpreting firmware SBOM paths, ranking unsafe functions and weaknesses, and understanding evolving CVE data to prioritize and remediate firmware security risks. | | Security | L46-L51 | Managing secure access to Azure Firmware Analysis using service principals and configuring role-based access control (RBAC) permissions for users and apps | | Integrations & Coding Patterns | L52-L59 | How to integrate firmware analysis with Azure Device Registry and programmatically upload firmware using CLI, PowerShell, or Python scripts. | | Deployment | L60-L65 | How to provision and deploy an Azure Firmware Analysis workspace using infrastructure-as-code tools: ARM templates, Bicep, and Terraform configuration and setup. | ### Troubleshooting | Topic | URL | |-------|-----| | Resolve common Azure firmware analysis issues | https://learn.microsoft.com/en-us/azure/firmware-analysis/firmware-analysis-faq | ### Best Practices | Topic | URL | |-------|-----| | Interpret SBOM extractor paths in firmware analysis | https://learn.microsoft.com/en-us/azure/firmware-analysis/interpreting-extractor-paths | | Prioritize unsafe function calls in firmware analysis | https://learn.microsoft.com/en-us/azure/firmware-analysis/understand-unsafe-function-calls | | Interpret and prioritize firmware weaknesses data | https://learn.microsoft.com/en-us/azure/firmware-analysis/understand-weaknesses-data | | Interpret evolving CVE data in firmware analysis | https://learn.microsoft.com/en-us/azure/firmware-analysis/understanding-latest-cves | ### Security | Topic | URL | |-------|-----| | Automate firmware analysis with service principals | https://learn.microsoft.com/en-us/azure/firmware-analysis/automate-firmware-analysis-service-principals | | Configure RBAC access for Azure firmware analysis | https://learn.microsoft.com/en-us/azure/firmware-analysis/firmware-analysis-rbac | ### Integrations & Coding Patterns | Topic | URL | |-------|-----| | Integrate firmware analysis with Azure Device Registry | https://learn.microsoft.com/en-us/azure/firmware-analysis/firmware-analysis-integration-with-azure-device-registry | | Upload firmware to Azure firmware analysis via CLI | https://learn.microsoft.com/en-us/azure/firmware-analysis/quickstart-upload-firmware-using-azure-command-line-interface | | Upload firmware to Azure analysis with PowerShell | https://learn.microsoft.com/en-us/azure/firmware-analysis/quickstart-upload-firmware-using-powershell | | Upload firmware to Azure analysis using Python | https://learn.microsoft.com/en-us/azure/firmware-analysis/quickstart-upload-firmware-using-python | ### Deployment | Topic | URL | |-------|-----| | Deploy firmware analysis workspace via ARM template | https://learn.microsoft.com/en-us/azure/firmware-analysis/quickstart-firmware-analysis-arm | | Deploy firmware analysis workspace with Bicep | https://learn.microsoft.com/en-us/azure/firmware-analysis/quickstart-firmware-analysis-bicep | | Provision firmware analysis workspace using Terraform | https://learn.microsoft.com/en-us/azure/firmware-analysis/quickstart-firmware-analysis-terraform |
© MicrosoftDocs · CC-BY-4.0 · MicrosoftDocs/Agent-Skills