iot-firmware
Orchestrate firmware rollouts with canary deployment and anomaly-gated advancement
Profile →npx skills add ruvnet/ruflo --skill iot-firmware --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
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)
What does the iot-firmware skill do?
Orchestrate firmware rollouts with canary deployment and anomaly-gated advancement
How do I install it?
Run `npx skills add ruvnet/ruflo --skill iot-firmware --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From ruvnet/ruflo, a repository with 67,015 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.