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.
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). - The gateway publishes upstream through the IoT Edge runtime and routes data to IoT Hub. - Local modules can filter, aggregate, and trigger actions even during cloud outages. ## Design flow ### 1) Device contract Define: - Sensor catalog and units. - Sampling frequency and expected throughput. - Message schema versioning strategy. - Desired/reported device twin properties to control runtime behavior. ### 2) Security baseline Require: - Unique identity per device. - No hardcoded secrets in source code or firmware artifacts. - Credential rotation strategy. - Signed firmware and a controlled update process when possible. ### 3) Reliability and offline behavior Plan and document: - Backoff with jitter. - Local queue/buffer strategy with bounded size. - Duplicate suppression or downstream idempotent processing. - Fallback to last-known-good configuration. ### 4) Cloud and edge routing Define routes for: - Raw telemetry to cold storage. - Curated telemetry to hot analytics. - Alerts to operations channels. - Commands and configuration back to edge/device. ### 5) Observability Specify minimum operations telemetry: - Device heartbeat and firmware version. - Connectivity state transitions. - Message send success/error counters. - Gateway module health and restart reasons. ## Reuse other skills When relevant, combine with: - `azure-smart-city-iot-solution-builder` for city-wide architecture and phased rollout. - `azure-resource-visualizer` for relationship diagrams. - `appinsights-instrumentation` for app and service telemetry patterns. Also use `references/arduino-official-best-practices.md` as a quality baseline for firmware and hardware recommendations. ## Required output Always provide: 1. Chosen connectivity pattern and rationale. 2. Message contract (fields, units, sample payload). 3. Security checklist for identity/credentials/updates. 4. Reliability plan (retry, buffering, dedupe). 5. Implementation backlog (firmware, gateway, cloud). ## Output template 1. Scenario and assumptions 2. Recommended architecture 3. Device and gateway contract 4. Security and reliability controls 5. Deployment plan and validation tests ## Guidelines - Do not propose production deployments with shared credentials across devices. - Do not assume always-on connectivity in field deployments. - Do not omit command authorization and auditing in actuator scenarios.
Related in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.