Iot Firmware
Run canary-gated firmware rollouts across an IoT fleet with deploy, advance, rollback, and status commands from your coding agent.
Overview
Iot-firmware is an agent skill for the Operate phase that orchestrates canary firmware rollouts across IoT fleets using cognitum-iot CLI workflows.
Install
npx skills add https://github.com/ruvnet/ruflo --skill iot-firmwareWhat is this skill?
- CLI-driven deploy, advance, rollback, status, and list via cognitum-iot firmware
- Canary rollout progression: pending → canary → rolling → complete (or rolled-back)
- Anomaly-gated advancement between rollout stages
- Integrates with Claude Flow memory store/search for rollout context
- Explicit npx @claude-flow/plugin-iot-cognitum command templates per action
- Rollout stages: pending → canary → rolling → complete (or rolled-back)
- 5 firmware subcommands: deploy, advance, rollback, status, list
Adoption & trust: 1 installs on skills.sh; 58.6k GitHub stars; 1/3 security scanners passed (skills.sh audits).
What problem does it solve?
You need to push firmware to many devices without a safe, staged rollout path or quick rollback when canary metrics go wrong.
Who is it for?
Builders already on Claude Flow / Cognitum IoT who manage OTA updates and want anomaly-gated canary promotion from the terminal.
Skip if: Greenfield embedded firmware authoring, unrelated mobile app releases, or fleets not using the cognitum-iot plugin toolchain.
When should I use this skill?
Manage firmware rollouts across device fleets (deploy, advance, rollback, status, or list).
What do I get? / Deliverables
You can deploy a version to a fleet, advance or rollback rollouts by ID, and list or status-check campaigns with copy-paste npx commands from the agent.
- Executed or documented firmware deploy to a fleet
- Rollout advancement or rollback tied to rollout ID
- Status or list output for ongoing OTA campaigns
Recommended Skills
Journey fit
How it compares
Fleet OTA orchestration skill with staged gates—not a generic CI YAML generator or local flasher utility.
Common Questions / FAQ
Who is iot-firmware for?
Solo and indie operators of IoT device fleets who deploy firmware through the Cognitum IoT plugin and want agent-assisted rollout control.
When should I use iot-firmware?
During Operate when deploying a new firmware version, advancing after a healthy canary, rolling back a bad release, or auditing rollout status across fleets.
Is iot-firmware safe to install?
Commands mutate live fleet firmware; review the Security Audits panel on this Prism page, confirm fleet IDs and versions, and test canary scope before full rollout.
SKILL.md
READMESKILL.md - Iot Firmware
Manage firmware rollouts across device fleets. **deploy**: `npx -y -p @claude-flow/plugin-iot-cognitum@latest cognitum-iot firmware deploy FLEET_ID --version VERSION` **advance**: `npx -y -p @claude-flow/plugin-iot-cognitum@latest cognitum-iot firmware advance ROLLOUT_ID` **rollback**: `npx -y -p @claude-flow/plugin-iot-cognitum@latest cognitum-iot firmware rollback ROLLOUT_ID` **status**: `npx -y -p @claude-flow/plugin-iot-cognitum@latest cognitum-iot firmware status ROLLOUT_ID` **list**: `npx -y -p @claude-flow/plugin-iot-cognitum@latest cognitum-iot firmware list` Rollout stages: pending → canary → rolling → complete (or rolled-back)