This maps IoT domain constraints directly to Rust implementation choices. You get rules like "networks fail constantly" translated into concrete patterns: local buffering with persistence, exponential backoff, MQTT QoS levels. It covers the full spectrum from Linux gateways running tokio and rumqttc to no_std MCU code with embassy. The trace-down structure is the real value here, connecting "need power efficiency" to specific crate choices and sleep patterns. Includes working MQTT client code and a comparison table showing when to use std versus no_std stacks. Best used alongside the embedded and concurrency skills when you're building anything that talks to sensors or actuators over unreliable networks.
npx skills add https://github.com/zhanghandong/rust-skills --skill domain-iot