Azure Iot Agent Skill
Expert knowledge for Azure IoT development including decision making, architecture & design patterns, and configuration. Use when managing Azure Device Registry X.509 PKI, ADR policies, IoT Hub cert revocation, or device schema namespaces, and other Azure IoT related development tasks. Not for Azure IoT Central (use azure-iot-central), Azure IoT Edge (use azure-iot-edge), Azure IoT Hub (use azure-iot-hub), Azure Defender For Iot (use azure-defender-for-iot).
Install
one command, takes just this skill from the repositorynpx skills add https://github.com/MicrosoftDocs/Agent-Skills --skill azure-iotThe instruction itself
6 sections, as written by the authorAzure IoT Skill
This skill provides expert guidance for Azure IoT. Covers decision making, architecture & design patterns, and configuration. 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), 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
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 |
|----------|-------|-------------|
| Decision Making | L31-L36 | Guidance on designing Azure Device Registry namespaces and schema registries, including structure, organization, and planning for IoT device data models and metadata. |
| Architecture & Design Patterns | L37-L42 | Designing certificate lifecycle flows for Azure Device Registry and IoT Hub, including issuance, renewal planning, automation, and minimizing downtime for IoT device certificates |
| Configuration | L43-L49 | Configuring Azure Device Registry for X.509 PKI: setting up credentials, creating ADR policies with Microsoft or external root CAs, and revoking certificates/policies for IoT Hub. |
Decision Making
| Topic | URL |
|-------|-----|
| Design and choose Azure Device Registry namespaces | https://learn.microsoft.com/en-us/azure/iot/iot-device-registry-namespace-guidance |
| Plan Azure Device Registry schema registries for IoT | https://learn.microsoft.com/en-us/azure/iot/iot-device-registry-schema-registry-guidance |
Architecture & Design Patterns
| Topic | URL |
|-------|-----|
| Understand certificate issuance flow in ADR and IoT Hub | https://learn.microsoft.com/en-us/azure/iot/concept-certificate-issuance |
| Plan and execute certificate renewal for IoT devices | https://learn.microsoft.com/en-us/azure/iot/concept-certificate-renewal |
Configuration
| Topic | URL |
|-------|-----|
| Configure Azure Device Registry credential for X.509 PKI | https://learn.microsoft.com/en-us/azure/iot/how-to-configure-credential |
| Create policy with Microsoft root CA in ADR | https://learn.microsoft.com/en-us/azure/iot/how-to-create-policy |
| Configure ADR policy with external root CA | https://learn.microsoft.com/en-us/azure/iot/how-to-create-policy-external-certificate |
| Revoke certificates and delete ADR policies for IoT Hub | https://learn.microsoft.com/en-us/azure/iot/how-to-revoke-certificate-delete-policy |
Other skills for the same job
different authors, same section of the catalogue
Workflow automation is the infrastructure that makes AI agents reliable. Without durable execution, a network hiccup during a 10-step payment flow means lost money and angry customers. With it, workflows resume exactly where they left off. This skill covers the platforms (n8n, Temporal, Inngest) and patterns (sequential, parallel, orchestrator-worker) that turn brittle scripts into production-grade automation. Key insight: The platforms make different tradeoffs. n8n optimizes for accessibility
Automate Cloudinary media management including folder organization, upload presets, asset lookup, transformations, and usage monitoring through natural language commands
You are a workflow automation expert specializing in creating efficient CI/CD pipelines, GitHub Actions workflows, and automated development processes. Design automation that reduces manual work, improves consistency, and accelerates delivery while maintaining quality and security.
Server management principles and decision-making. Process management, monitoring strategy, and scaling decisions. Teaches thinking, not commands.
Create a formal specification for an existing GitHub Actions CI/CD workflow, optimized for AI consumption and workflow maintenance.
Build and operate reproducible genomics workloads on DNAnexus with the dx CLI, dxpy, apps/applets, native workflows, dxCompiler, and Nextflow. Use for DNAnexus data transfers, dxapp.json development, execution monitoring, workflow import, and project automation.
Search across company knowledge bases (Confluence, Jira, internal docs) to find and explain internal concepts, processes, and technical details. When an agent needs to: (1) Find or search for information about systems, terminology, processes, deployment, authentication, infrastructure, architecture, or technical concepts, (2) Search internal documentation, knowledge base, company docs, or our docs, (3) Explain what something is, how it works, or look up information, or (4) Synthesize information from multiple sources. Searches in parallel and provides cited answers.
Production deployment principles and decision-making. Safe deployment workflows, rollback strategies, and verification. Teaches thinking, not scripts.
How to use it
Take microsoftdocs/azure-iot from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.