Agent skill · software engineering · github
arduino-azure-iot-edge-integration
Design and implement Arduino integration with Azure IoT Hub and IoT Edge, including secure provisioning, resilient telemetry, command handling, and production guardrails.
Why this skill is useful
Provides specific integration patterns and security guidelines for Arduino devices with Azure IoT that the AI wouldn't reliably generate on its own.
What it needs
Requires arduino-cli, azure-iot-sdk installed locally. Requires azure account access. About 3k tokens when loaded. Last updated 2026-08-07. 37,534 stars on the source repository.
What this skill does
Arduino Azure IoT Edge Integration Use this skill when the user needs to connect Arduino-class devices to Azure IoT, especially in edge-heavy scenarios (gateways, intermittent networks, offline buffering, and local actuation). When to use it Use this skill for requests such as: "I want to connect Arduino sensors to Azure" "How do I send MQTT telemetry to IoT Hub?" "I need an edge gateway for field devices" "I want cloud-to-device commands and OTA configuration updates" Mandatory documentation review Before recommending an IoT Edge topology or runtime behavior, review: https://learn.microsoft.com/azure/iot-edge/ If documentation cannot be consulted, proceed with explicit assumptions and highlight them in a dedicated section. Official Arduino references and best practices (required) Before proposing firmware, wiring, or communication implementation details, consult official Arduino sources first: https://www.arduino.cc/en/Guide https://docs.arduino.cc/ https://docs.arduino.cc/language-reference/ references/arduino-official-best-practices.md When choosing between implementation alternatives, prioritize official Arduino guidance over community snippets unless there is a clear technical reason to deviate. Objectives Produce a secure end-to-end reference path from the Arduino device to cloud insights. Handle unstable links (store-and-forward, retries, idempotency). Define an actionable device and cloud backlog. Integration patterns Pattern A: Arduino direct to IoT Hub Use when connectivity is stable and cloud latency is acceptable. Protocol: MQTT over TLS. Identity: per-device credentials (SAS or X.509). Telemetry payload: compact JSON with timestamp, device ID, metrics, and optional quality flags. Pattern B: Arduino to local gateway, then IoT Edge Use when links are constrained, local control is required, or batching improves cost/reliability. Arduino communicates with a local gateway (serial, BLE, local MQTT, RS-485, Modbus bridge). …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills github/arduino-azure-iot-edge-integration