Register a Cognitum Seed device by endpoint and establish agent bridge
Scanned 9/4/2026
Install to Claude Code
Skills Directorynpx -y skills add ruvnet/claude-flow --skill iot-register --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Iot Register?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/ruvnet-iot-register-ruflo)More formats (shields.io, HTML) on the badges page.
---
name: iot-register
description: Register a Cognitum Seed device by endpoint and establish agent bridge
allowed-tools: Bash(npx *) mcp__plugin_ruflo-core_ruflo__memory_store Read
argument-hint: "[endpoint] [--token PAIRING_TOKEN]"
---
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" })`
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...
