Skip to main content
skill CX Codex

iot-register — Claude Code skill: register a Cognitum Seed device

Registers a Cognitum Seed device by endpoint and sets up an agent bridge. Useful when wiring the device into Claude.

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add ruvnet/ruflo --skill iot-register -a claude-code
Open on GitHub

What iot-register does

The skill opens a SeedClient connection, pulls the device identity and assigns an initial trust level. With no endpoint supplied it falls back to http://169.254.42.1/, the link-local USB Ethernet address of the Cognitum Seed.

Everything runs through npx: cognitum-iot register ENDPOINT first, then cognitum-iot pair DEVICE_ID when a pairing token is present, then cognitum-iot status DEVICE_ID. The registration event goes into memory via mcp__plugin_ruflo-core_ruflo__memory_store under the iot-devices namespace.

Arguments follow [endpoint] [--token PAIRING_TOKEN]. Skip the token and the pairing step never runs, so the device stays unpaired — have the token ready before you start.

What it helps with

  • How to install iot-register in Claude?
  • What does the iot-register skill do?
  • What endpoint does it use by default?
  • What do you need to pair the device?

Example prompts for the agent

  • Register the Cognitum Seed at http://169.254.42.1/.
  • Pair the device with --token PAIRING_TOKEN.
  • Show the status of the registered device.

How to install iot-register

1Skills CLI (Vercel)

npx skills add ruvnet/ruflo --skill iot-register -a claude-code

2Manually: put the files in place

~/.claude/skills/iot-register/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/iot-register/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about iot-register

How to install iot-register in Claude Code?

Run npx skills add ruvnet/ruflo --skill iot-register -a claude-code; the skill file then lands at ~/.claude/skills/iot-register/SKILL.md.

What does iot-register do?

It registers a Cognitum Seed device by endpoint, creates a SeedClient connection, fetches the identity and assigns an initial trust level.

What endpoint does it use by default?

http://169.254.42.1/, the link-local USB Ethernet address of the Cognitum Seed. It is used when no endpoint is passed.

What do you need to pair the device?

A pairing token, passed as --token PAIRING_TOKEN. Without it the cognitum-iot pair DEVICE_ID step does not run.

Source text

SKILL.md · MIT
---
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/[email protected] cognitum-iot register ENDPOINT`
3. If pairing token provided: `npx -y -p @claude-flow/[email protected] cognitum-iot pair DEVICE_ID`
4. Show device status: `npx -y -p @claude-flow/[email protected] 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" })`

© ruvnet · MIT · ruvnet/ruflo

Similar skills

All skills for Agent setup: memory, context, orchestration →

From the same set146

ddd-context Scaffolds a standard DDD bounded context directory structure with domain, application, and infrastructure layers. Useful when splitting monoliths. CX Codex +1 738installs adr-index Builds an index of architecture decisions plus the graph of links between them, all in one run of scripts/import.mjs. Useful when the ADR files on disk drifted from what the agent remembers. CX Codex +1 737installs trader-train Trains neural network models on market data using the neural-trader CLI. Prepares market forecasts with confidence intervals for specific tickers. CX Codex +1 736installs market-pattern Scans ingested OHLCV data for candlestick patterns, classifies each by type and reliability, and stores the result in memory. CX Codex +1 736installs ddd-validate Checks bounded context integrity in TypeScript projects and flags domain boundary leaks. Useful for DDD architecture audits and pre-merge CI checks. CX Codex +1 736installs sparc-implement A skill that runs SPARC design phases: writes algorithm pseudocode, defines module boundaries and API contracts, then generates working code. Use it if you're developing with SPARC methodology and want to automate the architecture stage. CX Codex +1 734installs observe-metrics Aggregates agent swarm counters, gauges, and histograms over a time window to detect metric anomalies against baselines. CX Codex +1 733installs sparc-spec Runs the first SPARC phase: turns a feature description into requirements, acceptance criteria and constraints, then keeps the spec in ruflo memory. CX Codex +1 732installs

Project sponsors

Companies that keep this analytics open
Gold sponsor

Impressions, clicks and code copies — open statistics. We keep the numbers public for the same reason NeBlask itself is public. Become a sponsor