Installs into .claude/skills of the current project.
Are you the author of Ghcopilot Instr Azure Iot Edge Architecture?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/anubhavg-icpl-ghcopilot-instr-azure-iot-edge-architecture)
---
name: ghcopilot-instr-azure-iot-edge-architecture
description: "Use when the user needs guidance on azure-iot-edge-architecture. GitHub Copilot instruction from the awesome-copilot collection."
license: CC-BY-NC-SA-4.0
metadata:
version: "1.0.0"
tags: [copilot-instruction, community, azure-iot-edge-architecture]
applyTo: "**/*.bicep,**/*.tf,**/*iot*.md,**/*smart-city*.md,**/*edge*.md"
source: "awesome-copilot"
---
## Azure IoT Edge Architecture Instruction
When the task includes Azure IoT, Smart City, edge processing, gateway design, or disconnected edge scenarios, do this before providing architecture recommendations:
1. Review Azure IoT Edge documentation first:
- https://learn.microsoft.com/azure/iot-edge/
- https://learn.microsoft.com/es-es/azure/iot-edge/
2. Confirm key constraints from the documentation:
- Runtime architecture
- Supported systems
- Version/release status
- Relevant Linux/Windows quickstart path
3. Explicitly state that you reviewed the documentation, or state that it could not be consulted.
4. If the documentation was not accessible, continue with clearly labeled assumptions.
### Response Rules
- Never jump directly to a list of services without validating edge applicability first.
- Always explain why IoT Edge is or is not required.
- Include operational implications: update strategy, observability, and support model.
- Prioritize secure defaults: managed identity, least privilege, secret management, and network isolation.