Apex Azure Bicep Patterns
jonathan-vella/apex
UTILITY SKILL — Reusable Azure Bicep patterns: hub-spoke, private endpoints, diagnostics, AVM composition.
Expert knowledge for Azure Firmware Analysis development including best practices, security, integrations & coding patterns, and deployment.
Install Azure Firmware Analysis
$ npx skills add MicrosoftDocs/Agent-Skills --skill azure-firmware-analysis -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install MicrosoftDocs/Agent-Skills azure-firmware-analysis --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/MicrosoftDocs/Agent-Skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/azure-firmware-analysis .claude/skills/azure-firmware-analysis && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "azure-firmware-analysis" agent skill from https://github.com/MicrosoftDocs/Agent-Skills/tree/main/skills/azure-firmware-analysis into .claude/skills/azure-firmware-analysis/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "azure-firmware-analysis", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/MicrosoftDocs/Agent-Skills/tree/main/skills/azure-firmware-analysisType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add MicrosoftDocs/Agent-Skills --skill azure-firmware-analysis -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install MicrosoftDocs/Agent-Skills azure-firmware-analysis --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/MicrosoftDocs/Agent-Skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/azure-firmware-analysis .agents/skills/azure-firmware-analysis && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "azure-firmware-analysis" agent skill from https://github.com/MicrosoftDocs/Agent-Skills/tree/main/skills/azure-firmware-analysis into .agents/skills/azure-firmware-analysis/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "azure-firmware-analysis", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add MicrosoftDocs/Agent-Skills --skill azure-firmware-analysis -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install MicrosoftDocs/Agent-Skills azure-firmware-analysis --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/MicrosoftDocs/Agent-Skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/azure-firmware-analysis .cursor/skills/azure-firmware-analysis && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "azure-firmware-analysis" agent skill from https://github.com/MicrosoftDocs/Agent-Skills/tree/main/skills/azure-firmware-analysis into .cursor/skills/azure-firmware-analysis/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "azure-firmware-analysis", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/MicrosoftDocs/Agent-Skills.git --path skills/azure-firmware-analysis--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add MicrosoftDocs/Agent-Skills --skill azure-firmware-analysis -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install MicrosoftDocs/Agent-Skills azure-firmware-analysis --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/MicrosoftDocs/Agent-Skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/azure-firmware-analysis .gemini/skills/azure-firmware-analysis && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "azure-firmware-analysis" agent skill from https://github.com/MicrosoftDocs/Agent-Skills/tree/main/skills/azure-firmware-analysis into .gemini/skills/azure-firmware-analysis/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "azure-firmware-analysis", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install MicrosoftDocs/Agent-Skills azure-firmware-analysisInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add MicrosoftDocs/Agent-Skills --skill azure-firmware-analysis -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/MicrosoftDocs/Agent-Skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/azure-firmware-analysis .github/skills/azure-firmware-analysis && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "azure-firmware-analysis" agent skill from https://github.com/MicrosoftDocs/Agent-Skills/tree/main/skills/azure-firmware-analysis into .github/skills/azure-firmware-analysis/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "azure-firmware-analysis", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add MicrosoftDocs/Agent-Skills --skill azure-firmware-analysis -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install MicrosoftDocs/Agent-Skills azure-firmware-analysis --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/MicrosoftDocs/Agent-Skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/azure-firmware-analysis .opencode/skills/azure-firmware-analysis && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "azure-firmware-analysis" agent skill from https://github.com/MicrosoftDocs/Agent-Skills/tree/main/skills/azure-firmware-analysis into .opencode/skills/azure-firmware-analysis/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "azure-firmware-analysis", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
azure-firmware-analysis- GitHub stars
- 775
- Token cost
- ~1.2k tokens
- SKILL.md length
- 348 words
- Files
- 1
- Skills in repo
- 149
- Repo updated
- First seen
- Licence
- CC-BY-4.0
At a glance
Expert knowledge for Azure Firmware Analysis development including best practices, security, integrations & coding patterns, and deployment.
- Configuring RBAC/service principals
- SKILL.md covers How to Use This Skill and Category Index
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Uploading firmware via CLI/PowerShell/Python
What it does
Azure Firmware Analysis is an agent skill from MicrosoftDocs/Agent-Skills, published by the product's own GitHub organization. Expert knowledge for Azure Firmware Analysis development including best practices, security, integrations & coding patterns, and deployment. Use when configuring RBAC/service principals, uploading firmware via CLI/PowerShell/Python, mapping results to Device Registry, reading SBOM paths, or deploying workspaces with ARM/Bicep/Terraform, 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…
Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts. Compatibility notes: Requires network access. Uses mcpmicrosoftdocs:microsoftdocsfetch or fetchwebpage to retrieve documentation.
It sits in DevOps & Cloud, covering Reverse engineering and malware, Infrastructure as code and Authorization and RBAC. It works with Microsoft Azure, Bicep, Terraform and PowerShell. The repository describes itself as: Curated Agent Skills for Microsoft & Azure – giving AI coding assistants structured, real-time expertise from Microsoft Learn docs. The licence is CC-BY-4.0.
When your agent uses it
- Configuring RBAC/service principals
- Uploading firmware via CLI/PowerShell/Python
- Mapping results to Device Registry
- Reading SBOM paths
Example prompts
- “/azure-firmware-analysis”
Requirements
- Python 3
- Compatibility (from SKILL.md): Requires network access. Uses mcp_microsoftdocs:microsoft_docs_fetch or fetch_webpage to retrieve documentation.
What it can do on your machine
Read from SKILL.md and the folder at commit ba74e8f. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
Links to these hosts (documentation or services it may open):
learn.microsoft.comgithub.com
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Compatibility
Requires network access. Uses mcp_microsoftdocs:microsoft_docs_fetch or fetch_webpage to retrieve documentation.
From compatibility in the SKILL.md frontmatter.
Context cost
Azure Firmware Analysis loads about 1.2k tokens when it runs. Until then it costs about 155 tokens; SKILL.md has 348 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from MicrosoftDocs/Agent-Skills at commit ba74e8f, republished under its CC-BY-4.0 licence (© MicrosoftDocs). 348 words, ~1,248 tokens.
Download SKILL.mdSave it as
.claude/skills/azure-firmware-analysis/SKILL.md (or your agent's skills folder).- name
- azure-firmware-analysis
- description
- Expert knowledge for Azure Firmware Analysis development including best practices, security, integrations & coding patterns, and deployment. Use when configuring RBAC/service principals, uploading firmware via CLI/PowerShell/Python, mapping results to Device Registry, reading SBOM paths, or deploying workspaces with ARM/Bicep/Terraform, 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-09-27
- metadata.generator
- docs2skills/1.0.0
Azure Firmware Analysis Skill
This skill provides expert guidance for Azure Firmware Analysis. Covers 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), 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:
- Preferred: Use
mcp_microsoftdocs:microsoft_docs_fetchwith query stringfrom=learn-agent-skill. Returns Markdown. - Fallback: Use
fetch_webpagewith query stringfrom=learn-agent-skill&accept=text/markdown. Returns Markdown.
Category Index
| Category | Lines | Description |
|---|---|---|
| Best Practices | L32-L38 | Guidance on reading firmware SBOM paths, understanding unsafe function call alerts, and interpreting/prioritizing firmware weakness findings for security analysis. |
| Security | L39-L44 | 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 | L45-L52 | CLI, PowerShell, and Python examples for uploading firmware to Azure Firmware Analysis and mapping scan results to Azure Device Registry devices and assets. |
| Deployment | L53-L58 | How to provision and deploy an Azure Firmware Analysis workspace using infrastructure-as-code tools: ARM templates, Bicep, and Terraform configuration and setup. |
Best Practices
| Topic | URL |
|---|---|
| Interpret SBOM extractor paths in firmware analysis | https://learn.microsoft.com/en-us/azure/firmware-analysis/interpreting-extractor-paths |
| Interpret unsafe function call findings 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 |
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 |
|---|---|
| Map firmware analysis results to Azure Device Registry assets | 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. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/azure-firmware-analysis of MicrosoftDocs/Agent-Skills.
Open the folder on GitHubat commit ba74e8f
Compare with similar skills
Azure Firmware Analysis next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Azure Firmware Analysis this skillMicrosoftDocs/Agent-Skills | 775 | — | ~1.2k | Automated safety check: Pass | CC-BY-4.0 | |
| Apex Azure Bicep Patternsjonathan-vella/apex | 217 | — | ~2.5k | Automated safety check: Pass | MIT | |
| Azure Preparemicrosoft/GitHub-Copilot-for-Azure | 255 | 1 repos | ~3.2k | Automated safety check: Pass | MIT | |
| Azure Validatemicrosoft/GitHub-Copilot-for-Azure | 255 | 1 repos | ~880 | Automated safety check: Pass | MIT | |
| Apex Terraform Patternsjonathan-vella/apex | 217 | — | ~2.2k | Automated safety check: Pass | MIT | |
| Apex Azure Rbacjonathan-vella/apex | 217 | — | ~1.8k | Automated safety check: Pass | MIT |
Similar skills
- Official
Azure Prepare
microsoft/GitHub-Copilot-for-Azure
Prepare azd-based Azure projects for deployment: generates azure.yaml, infrastructure (Bicep/Terraform), and Dockerfiles for the Azure Developer CLI (azd) workflow.
- Official
Azure Validate
microsoft/GitHub-Copilot-for-Azure
Pre-deployment validation for Azure readiness. An agent skill from microsoft/GitHub-Copilot-for-Azure.
Apex Terraform Patterns
jonathan-vella/apex
UTILITY SKILL — Reusable Azure Terraform patterns: hub-spoke, private endpoints, diagnostics, AVM-TF modules.
Apex Azure Rbac
jonathan-vella/apex
ANALYSIS SKILL — Find the right Azure RBAC role for an identity with least-privilege access; generate CLI, Bicep, and Terraform code to assign it.
- Official
Azure Architecture Autopilot
github/awesome-copilot
Designs Azure infrastructure from a natural-language description, or diagrams an existing resource group, then refines the design through conversation and deploys it with Bicep.
More from MicrosoftDocs/Agent-Skills
All 149 skills in this repo- Official
Azure Personalizer
MicrosoftDocs/Agent-Skills
Expert knowledge for Azure AI Personalizer development including troubleshooting, decision making, security, configuration, and integrations & coding patterns.
- Official
Azure Architecture Advisor
MicrosoftDocs/Agent-Skills
Guides Azure solution design by category, from reference architectures and design patterns to technology choices and migrations, fetching current Microsoft Learn pages over the network.
- Official
Azure Advisor Guidance
MicrosoftDocs/Agent-Skills
Reference guidance for Azure Advisor work: recommendations, alerts and digests, workbooks, RBAC access and sovereign-cloud limits, fetched from Microsoft Learn.
- Official
Azure AI Vision Reference
MicrosoftDocs/Agent-Skills
Looks up Microsoft Learn guidance for Azure AI Vision: Image Analysis, Read OCR containers, smart-crop thumbnails, background removal and video frame analysis, plus limits and deployment.
- Official
Azure Analysis Services
MicrosoftDocs/Agent-Skills
Expert knowledge for Azure Analysis Services development including troubleshooting.
- Official
Azure Anomaly Detector
MicrosoftDocs/Agent-Skills
Expert knowledge for Azure AI Anomaly Detector development including troubleshooting, best practices, limits & quotas, configuration, and deployment.
Related
Categories
Questions about Azure Firmware Analysis
What does Azure Firmware Analysis do?
Expert knowledge for Azure Firmware Analysis development including best practices, security, integrations & coding patterns, and deployment. Azure Firmware Analysis is an agent skill from MicrosoftDocs/Agent-Skills, published by the product's own GitHub organization. Expert knowledge for Azure Firmware Analysis development including best practices, security, integrations & coding patterns, and deployment.
When should I use Azure Firmware Analysis?
Azure Firmware Analysis fits situations like: configuring RBAC/service principals; uploading firmware via CLI/PowerShell/Python; mapping results to Device Registry; reading SBOM paths.
How do I install Azure Firmware Analysis in Claude Code?
Run `npx skills add MicrosoftDocs/Agent-Skills --skill azure-firmware-analysis -a claude-code`. Or copy the skill folder (skills/azure-firmware-analysis in MicrosoftDocs/Agent-Skills) into .claude/skills/azure-firmware-analysis in your project. Claude Code loads it when a task matches its description.
How do I install Azure Firmware Analysis in Codex?
Run `npx skills add MicrosoftDocs/Agent-Skills --skill azure-firmware-analysis -a codex`. Or copy the skill folder (skills/azure-firmware-analysis in MicrosoftDocs/Agent-Skills) into .agents/skills/azure-firmware-analysis in your project. Codex loads it when a task matches its description.
Can I use Azure Firmware Analysis in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add MicrosoftDocs/Agent-Skills --skill azure-firmware-analysis -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/azure-firmware-analysis, .gemini/skills/azure-firmware-analysis, .github/skills/azure-firmware-analysis and .opencode/skills/azure-firmware-analysis in your project.
What does Azure Firmware Analysis need to run?
SKILL.md names no scripts, command-line tools or credentials: Azure Firmware Analysis is instructions for the agent only. Our summary lists: Python 3. Compatibility (from SKILL.md): Requires network access. Uses mcp_microsoftdocs:microsoft_docs_fetch or fetch_webpage to retrieve documentation..
Does Azure Firmware Analysis access the network?
SKILL.md names 2 domains. As links in the text: learn.microsoft.com and github.com. This is read from the text; nothing was executed.
Is Azure Firmware Analysis safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Azure Firmware Analysis use?
Azure Firmware Analysis is published under the CC-BY-4.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Azure Firmware Analysis use?
About 1.2k tokens (SKILL.md is roughly 5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Azure Firmware Analysis?
Skills that share tags, products or a category with Azure Firmware Analysis: Apex Azure Bicep Patterns (jonathan-vella/apex, 217 stars), Azure Prepare (microsoft/GitHub-Copilot-for-Azure, 255 stars), Azure Validate (microsoft/GitHub-Copilot-for-Azure, 255 stars) and Apex Terraform Patterns (jonathan-vella/apex, 217 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Azure Firmware Analysis?
MicrosoftDocs (a GitHub organization, an official publisher) maintains it in MicrosoftDocs/Agent-Skills, which has 775 GitHub stars. The repository holds 149 skills in this directory. The repository was last updated on October 5, 2026.
Source: MicrosoftDocs/Agent-Skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.