CtrlK
BlogDocsLog inGet started
Tessl Logo

onboard

Zero-to-sensing path picker for RuView (WiFi-DensePose) — pick docker-demo, repo-build, or live-esp32 and run the next concrete step.

65

Quality

77%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./harness/ruview/.claude/skills/onboard/SKILL.md
SKILL.md
Quality
Evals
Security

onboard

Get a newcomer from nothing to a working RuView setup. First fact to set: WiFi sensing infers coarse pose/presence/breathing from Channel State Information — it is not a camera, and any accuracy number must be MEASURED against a baseline (use the verify skill / ruview_claim_check tool). Never present WiFi output as camera-grade.

Pick a path

Run ruview_onboard {path} or decide from:

  1. docker-demo — fastest, no hardware. Replays sample CSI into the dashboard. docker run -p 8000:8000 ruvnet/wifi-densepose → open http://localhost:8000. Use to see what it looks like.
  2. repo-build — for developers. cd v2 && cargo test --workspace --no-default-features (1,031+ tests pass), then cargo run -p wifi-densepose-cli -- --help.
  3. live-esp32 — a real install. Flash a node (provision-node skill), point it at the sensing-server, then calibrate-room. This is the only path that senses a real room.

Then

  • Live sensing → go to provision-node, then calibrate-room.
  • Evaluating a model/claim → go to verify and run ruview_claim_check on any report before you quote a number.
Repository
ruvnet/RuView
Last updated
First committed

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.