Iot Register
- 648 installs
- 67k repo stars
- Updated August 4, 2026
- ruvnet/ruflo
iot-register is a ruflo agent skill that registers Cognitum Seed IoT devices via cognitum-iot CLI and stores identity in claude-flow memory for developers who connect hardware endpoints to agent workflows.
About
iot-register is a ruflo skill from ruvnet/ruflo with 556 skills.sh installs that registers Cognitum Seed devices through the @claude-flow/plugin-iot-cognitum package. It resolves an endpoint from user input or defaults to http://169.254.42.1/, the Cognitum Seed link-local USB Ethernet address. The workflow runs npx -y -p @claude-flow/plugin-iot-cognitum@latest cognitum-iot register ENDPOINT, optionally pairs with a token via cognitum-iot pair DEVICE_ID, then checks status with cognitum-iot status DEVICE_ID. Registration events persist through mcp__claude-flow__memory_store under the iot-devices namespace with keys like iot-register-DEVICEID. Allowed tools include Bash for npx commands, Read, and claude-flow memory_store. Developers reach for iot-register when onboarding Cognitum Seed hardware into ruflo agentic IoT pipelines.
- Registers IoT devices and services as agent capabilities
- Integrates hardware sensors and actuators into AI workflows
- Exposes device state as queryable context for Claude Code and Cursor
- Supports 430+ active installs across indie IoT projects
- Provides standardized registration pattern for physical-world agents
Iot Register by the numbers
- 648 all-time installs (skills.sh)
- +6 installs in the week ending Aug 5, 2026 (Skillselion tracking)
- Ranked #1,511 of 16,546 AI & Agent Building skills by installs in the Skillselion catalog
- Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/ruvnet/ruflo --skill iot-registerAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 648 |
|---|---|
| repo stars | ★ 67k |
| Last updated | August 4, 2026 |
| Repository | ruvnet/ruflo ↗ |
How do you register Cognitum Seed IoT devices?
Register IoT devices and services with an agentic workflow using the ruflo framework.
Who is it for?
Developers using ruflo and claude-flow who onboard Cognitum Seed hardware over USB Ethernet into agent-managed IoT workflows.
Skip if: Cloud-only SaaS projects without physical Cognitum Seed devices or teams not using the ruflo claude-flow IoT plugin stack.
When should I use this skill?
A Cognitum Seed endpoint must be registered, paired with a token, or checked for status inside a ruflo agent session.
What you get
Registered SeedClient connection, device identity with trust level, pairing status, and iot-devices memory_store registration record.
- Registered device identity with trust level
- Pairing status output from cognitum-iot status
- iot-devices namespace memory_store record
By the numbers
- 556 skills.sh installs for ruvnet/ruflo iot-register
- Default endpoint http://169.254.42.1/ for Cognitum Seed USB Ethernet
- Four-step register, pair, status, and memory_store workflow
Files
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__claude-flow__memory_store({ key: "iot-register-DEVICEID", value: "Registered at ENDPOINT", namespace: "iot-devices" })
Related skills
Setup Matt Pocock SkillsScaffold the per-repo configuration that Matt Pocock’s engineering agent skills rely on so they understand the issue tracker, triage labels, and domain documentation la495k196k
Lark AppsConnect Claude, Cursor or custom agents directly to Lark (Feishu) for messaging, document automation, approval workflows and enterprise data access.402k
CavemanSlash token usage by roughly 75% while keeping every technical detail intact when working with Claude Code, Cursor or similar agents.391k94.7k
Lark Skill MakerQuickly turn any Lark/Feishu OpenAPI call or multi-step workflow into a reusable agent skill with its own SKILL.md.386k16k
Running Claude Code Via Litellm CopilotRun Claude Code at a fraction of the cost by routing requests through LiteLLM to the GitHub Copilot Chat API.270k72
Codex PetGenerate a complete Codex Pet spritesheet and metadata from one reference image without needing an OpenAI key or Codex Pro.246k10How it compares
Use iot-register for Cognitum Seed hardware onboarding; use general API integration skills for cloud-only device provisioning.
FAQ
What is the default endpoint for iot-register in ruflo?
iot-register defaults to http://169.254.42.1/, the Cognitum Seed link-local USB Ethernet address, when the user does not supply an explicit endpoint argument.
Which CLI package does iot-register invoke?
iot-register runs npx -y -p @claude-flow/plugin-iot-cognitum@latest with cognitum-iot subcommands for register, pair, and status against the resolved device endpoint.
Where does iot-register persist registration events?
iot-register stores registration via mcp__claude-flow__memory_store with keys like iot-register-DEVICEID in the iot-devices namespace for later agent retrieval.