Explore and prototype rvAgent + RVF integration for RuView agentic flows. Use when working on cross-cog coordination, operator-facing agents reading BFLD / pose / vitals events live, or persisting agent state alongside sensing data in the same RVF container.
77%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Low
Low-risk findings worth noting
Fix and improve this skill with Tessl
tessl review fix ./plugins/ruview/skills/ruview-rvagent/SKILL.mdSurface area for wiring vendor/ruvector/crates/rvAgent/ into RuView so the existing sensing pipeline becomes the substrate an agentic flow can read, reason about, and respond to.
@ruvnet/rvagent v0.1.0)Installing this plugin registers @ruvnet/rvagent as an MCP server. On activation, Claude Code spawns npx -y @ruvnet/rvagent and exposes its tools directly:
| Tool | Purpose |
|---|---|
bfld_last_scan | Most recent BFLD event from the sensing server |
bfld_subscribe | Stream BFLD events for a window |
presence_now | Current room-level presence state |
vitals_get_breathing | Latest breathing-rate sample |
vitals_get_heart_rate | Latest heart-rate sample |
vitals_get_all | Composite vitals snapshot |
vitals_fetch | Historical vitals window |
Override the sensing-server URL via the RVAGENT_SENSING_URL env var (default http://localhost:3000). Source lives at tools/ruview-mcp/; ADR-124 captures the design.
Smoke-check the wiring: npm view @ruvnet/rvagent version should return 0.1.0 (or newer).
| Surface | File | Notes |
|---|---|---|
| rvAgent core | vendor/ruvector/crates/rvAgent/rvagent-core/src/agi_container.rs (627 LOC) | RVF-compatible state container |
| rvAgent middleware | vendor/ruvector/crates/rvAgent/rvagent-middleware/ | Witness, sanitizer, SONA, HNSW |
| Agent personas | vendor/ruvector/crates/rvAgent/.ruv/agents/rvagent-{queen,coder,tester,security}.md | Reference patterns |
| RVF container | v2/crates/wifi-densepose-sensing-server/src/rvf_container.rs | Add SEG_AGENT_STATE, SEG_DECISION |
| BFLD event | v2/crates/wifi-densepose-bfld/src/event.rs | BfldEvent::to_json() → ToolOutput |
| BFLD pipeline handle | v2/crates/wifi-densepose-bfld/src/pipeline_handle.rs | BfldPipelineHandle::send |
Full integration analysis lives at docs/research/rvagent-rvf-integration/README.md.
Three shippable touchpoints, each independent:
SEG_AGENT_STATE = 0x08, SEG_DECISION = 0x09) let rvAgent sessions interleave with RuView sensing sessions in the same blob.BfldEvent → ToolOutput shim turns BFLD events into agent context with no new IPC.cog-pose-estimation / cog-person-count / cog-ha-matter / cog-bfld register as rvAgent subagents under a queen-agent router.vendor/ruvector/crates/rvAgent/ (path dep vs published crate)Publish is sync, rvAgent backends are tokio)PrivacyClass?)SoulMatchOracle bridgeBfldPipelineHandle::send lands as a public MCP tool via rvagent-mcpADR-124 (proposed) — "rvAgent + RVF integration for RuView agentic flows" — would capture segment assignments, cog-subagent contract, and the privacy-class composition rule. Land before scaffolding v2/crates/wifi-densepose-agent.
ruvnet/RuView
3bae24a
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.