iot-register
Register a Cognitum Seed device by endpoint and establish agent bridge
Profile →npx skills add ruvnet/ruflo --skill iot-register --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.
Register a Cognitum Seed device. Creates a SeedClient connection, fetches identity, and assigns initial trust level. Default endpoint: `http://169.254.42.1/` — the Cognitum Seed link-local USB Ethernet address. Use this when no endpoint is supplied. Steps: 1. Resolve ENDPOINT: use the user-supplied value, or default to `http://169.254.42.1/`. 2. `npx -y -p @claude-flow/plugin-iot-cognitum@latest cognitum-iot register ENDPOINT` 3. If pairing token provided: `npx -y -p @claude-flow/plugin-iot-cognitum@latest cognitum-iot pair DEVICE_ID` 4. Show device status: `npx -y -p @claude-flow/plugin-iot-cognitum@latest cognitum-iot status DEVICE_ID` Store registration event: `mcp__plugin_ruflo-core_ruflo__memory_store({ key: "iot-register-DEVICEID", value: "Registered at ENDPOINT", namespace: "iot-devices" })`
What does the iot-register skill do?
Register a Cognitum Seed device by endpoint and establish agent bridge
How do I install it?
Run `npx skills add ruvnet/ruflo --skill iot-register --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.