Agent skill

RuView CLI, API and WASM

by ruvnet in ruvnet/RuView

Covers the RuView `wifi-densepose` command line binary, its Axum REST API and the WebAssembly builds for browsers and ESP32, for embedding or scripting RuView.

MITAuto-check: notesBackend & APIs

Install RuView CLI, API and WASM

skills CLI
$ npx skills add ruvnet/RuView --skill ruview-cli-api -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install ruvnet/RuView ruview-cli-api --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/ruvnet/RuView.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/ruview/skills/ruview-cli-api .claude/skills/ruview-cli-api && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
ruview-cli-api
GitHub stars
97k
Token cost
~1.2k tokens
SKILL.md length
334 words
Files
1
Skills in repo
24
Repo updated
First seen
Licence
MIT

At a glance

Covers the RuView `wifi-densepose` command line binary, its Axum REST API and the WebAssembly builds for browsers and ESP32, for embedding or scripting RuView.

  • Works in 4 steps: The wifi-densepose CLI binary… → REST API (wifi-densepose-api, Axum) → WASM / browser & ESP32-WASM3 → …
  • Calling RuView from another program through the CLI or HTTP API
  • SKILL.md covers 1. The wifi-densepose CLI…, 2. REST API…, 3. WASM / browser & ESP32-WASM3 and 4. Where it fits, plus 1 more section
  • Calls cargo and docker

What it does

RuView exposes three programmatic surfaces and this skill explains each. The `wifi-densepose` binary has a `version` command and a `mat` group for disaster survivor detection, with subcommands to scan a zone, check status, manage zones, list survivors with triage status, view alerts and export data as JSON or CSV. Scanning takes flags for disaster type, sensitivity, maximum depth and continuous mode, and `--simulate` lets you test without hardware.

The REST API lives in the `wifi-densepose-api` crate, an Axum router configured through `wifi-densepose-config`. It is wired into the server binaries rather than run on its own, so the easiest way to try it is the Docker image, which serves the API and a dashboard on port 3000. For the browser, `wifi-densepose-wasm` compiles the stack to `wasm32-unknown-unknown` with a JavaScript-friendly API, and a `wifi-densepose-wasm-edge` build targets ESP32-WASM3.

When your agent uses it

  • Calling RuView from another program through the CLI or HTTP API
  • Scripting survivor scans and data exports from the shell
  • Running the RuView API and dashboard from the Docker image
  • Shipping the RuView stack to a browser or an ESP32 target as WebAssembly

Example prompts

  • “Show me how to run a continuous earthquake scan on zone rubble-A with the wifi-densepose CLI and export the survivors to CSV.”
  • “Start the RuView Docker image and tell me how to reach the API on port 3000.”
  • “Test the mat scan flow without any hardware attached.”

Requirements

  • Cargo (Rust toolchain) to build the CLI from the `v2` folder
  • Docker to run the API and dashboard image
  • Pre-approved tools (allowed-tools): Bash, Read, Write, Edit, Glob, Grep

Workflow steps

4 steps, taken from the step headings in SKILL.md.

  1. The wifi-densepose CLI binary (wifi-densepose-cli)
  2. REST API (wifi-densepose-api, Axum)
  3. WASM / browser & ESP32-WASM3
  4. Where it fits

What it can do on your machine

Read from SKILL.md and the folder at commit 0ef6b96. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Bash
    • Read
    • Write
    • Edit
    • Glob
    • Grep

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • cargo
    • docker

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use docker, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

RuView CLI, API and WASM loads about 1.2k tokens when it runs. Until then it costs about 99 tokens; SKILL.md has 334 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~99
When it runs · the whole SKILL.md, loaded when a task matches
~1.2k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

  • NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
    allowed-tools: Bash, Read, Write, Edit, Glob, Grep

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from ruvnet/RuView at commit 0ef6b96, republished under its MIT licence (© ruvnet). 334 words, ~1,160 tokens.

Download SKILL.mdSave it as .claude/skills/ruview-cli-api/SKILL.md (or your agent's skills folder).
name
ruview-cli-api
description
Use the RuView `wifi-densepose` CLI binary (incl. MAT scan/status/zones/survivors/alerts/export subcommands), the REST API (`wifi-densepose-api`, Axum), and the browser/WASM build (`wifi-densepose-wasm`, `wifi-densepose-wasm-edge`). Use when integrating RuView into another program, scripting it from the shell, exposing it over HTTP, or shipping it to the browser / ESP32-WASM3.
allowed-tools
Bash, Read, Write, Edit, Glob, Grep

RuView CLI, API & WASM

The programmatic surfaces of RuView — the wifi-densepose binary, the HTTP API, and the WebAssembly builds.

1. The wifi-densepose CLI binary (wifi-densepose-cli)

bash
cd v2
cargo run -p wifi-densepose-cli -- --help        # or: cargo build -p wifi-densepose-cli --release  → target/release/wifi-densepose
cargo run -p wifi-densepose-cli -- version

Top-level subcommands: version, and mat (Mass Casualty Assessment Tool).

wifi-densepose mat … — disaster survivor detection
SubcommandPurposeKey flags
mat scan [zone]Start scanning for survivors--disaster-type <…>, --sensitivity 0.0–1.0, --max-depth <m>, --continuous, --interval <ms>, --simulate
mat statusCurrent scan status--detailed, --format <…>, --watch
mat zones …Manage scan zoneszones list [--active-only], plus add/remove/update
mat survivorsList detected survivors with triage status
mat alertsView / manage alerts
mat exportExport scan dataJSON or CSV

Example:

bash
cargo run -p wifi-densepose-cli -- mat scan rubble-A --disaster-type earthquake --sensitivity 0.7 --max-depth 5 --continuous --interval 2000
cargo run -p wifi-densepose-cli -- mat survivors --format json
cargo run -p wifi-densepose-cli -- mat export --format csv > survivors.csv

Use --simulate for testing without hardware. Background and user guide: docs/wifi-mat-user-guide.md, wifi-densepose-mat crate.

2. REST API (wifi-densepose-api, Axum)

Library crate (v2/crates/wifi-densepose-api/src/lib.rs) — the Axum router/handlers; configured via the wifi-densepose-config crate. It's wired into the server binaries (e.g. the sensing server / Docker image), not a standalone cargo run target by itself.

bash
# Easiest way to exercise it: the Docker image exposes the API + dashboard on :3000
docker run -p 3000:3000 ruvnet/wifi-densepose:latest
# Then hit the HTTP endpoints (see the API module / docs for routes) and open http://localhost:3000

# v1 Python service config reference: example.env, pyproject.toml (archive/v1/)

When embedding the API crate in your own binary, take the router from wifi_densepose_api, supply config via wifi-densepose-config, and serve with Axum/Tokio. Keep input validation at the boundary (project rule).

Show full SKILL.md (177 more words)Show less

3. WASM / browser & ESP32-WASM3

  • wifi-densepose-wasm — compiles the stack to wasm32-unknown-unknown with a JS-friendly API:
    bash
    cd v2/crates/wifi-densepose-wasm
    wasm-pack build --target web --features mat        # recommended (produces pkg/)
    cargo build --target wasm32-unknown-unknown --features mat   # plain cargo build
    See v2/crates/wifi-densepose-wasm/README.md for the exported surface.
  • wifi-densepose-wasm-edge — 60 edge modules (609 tests) that compile to wasm32-unknown-unknown and run on ESP32-S3 via WASM3; shared utils in src/vendor_common.rs. These are the ADR-041 edge-intelligence modules in WASM form.
  • Browser demos: pose-fusion (ADR-059), point-cloud (ADR-094) — deployed via GitHub Pages from the WASM build.

4. Where it fits

You want to…Use
Script a survivor scan / export resultswifi-densepose mat …
Expose sensing over HTTPwifi-densepose-api (via a server binary / Docker)
Run sensing in a browserwifi-densepose-wasm → wasm-pack build --target web
Run an edge module on an ESP32 in WASMwifi-densepose-wasm-edge + WASM3
A long-running CSI sink + trainingwifi-densepose-sensing-server (see ruview-applications / ruview-model-training)

Reference

  • Crates: wifi-densepose-cli, wifi-densepose-api, wifi-densepose-config, wifi-densepose-wasm, wifi-densepose-wasm-edge, wifi-densepose-mat
  • ADRs: 041 (edge modules), 059 (live ESP32 pipeline), 094 (point-cloud GitHub Pages)
  • docs/wifi-mat-user-guide.md, docs/edge-modules/, docs/security-audit-wasm-edge-vendor.md
  • Validate after changes: cd v2 && cargo test -p wifi-densepose-cli -p wifi-densepose-api -p wifi-densepose-wasm --no-default-features

© ruvnet, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in plugins/ruview/skills/ruview-cli-api of ruvnet/RuView.

Open the folder on GitHubat commit 0ef6b96

Compare with similar skills

RuView CLI, API and WASM next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

RuView CLI, API and WASM compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
RuView CLI, API and WASM this skillruvnet/RuView97k—~1.2kAutomated safety check: NotesMIT
C64 Meatloaf Debugidolpx/meatloaf128—~12kAutomated safety check: PassGPL-3.0
Flash Displaysjtenniswood/espcontrol1.1k—~2.8kAutomated safety check: PassCustom licence
New APIjustrach/merjs356—~302Automated safety check: PassMIT
Esp32 Test PlanFastLED/FastLED7.5k—~1.9kAutomated safety check: PassMIT
Dr Jskilljdubois/dr-jskill342—~4.6kAutomated safety check: NotesApache-2.0

Similar skills

  • C64 Meatloaf Debug

    idolpx/meatloaf

    Debug Commodore 64 BASIC programs, cc65-compiled C PRGs, and Meatloaf ESP32 firmware in tandem, using the Ultimate 64's REST API and Meatloaf's UART serial debug output.

    128 GitHub stars~12k tokensUpdated yesterday
    DevelopmentAuto-check passed
  • Flash Displays

    jtenniswood/espcontrol

    Flash EspControl display firmware from this repository using ESPHome.

    1.1k GitHub stars~2.8k tokensUpdated today
    Backend & APIsAuto-check passed
  • New API

    justrach/merjs

    Scaffold a new merjs API route. An agent skill from justrach/merjs.

    356 GitHub stars~302 tokensUpdated 1 mo ago
    Backend & APIsAuto-check passed
  • Esp32 Test Plan

    FastLED/FastLED

    Generate a structured multi-layer test plan for FastLED changes targeting ESP32.

    7.5k GitHub stars~1.9k tokensUpdated today
    Testing & QAAuto-check passed
  • Dr Jskill

    jdubois/dr-jskill

    Creates Java + Spring Boot projects: Web applications, full-stack apps with Vue.js or Angular or React or vanilla JS, PostgreSQL, REST APIs, and Docker.

    342 GitHub stars~4.6k tokensUpdated 7 days ago
    Backend & APIsAuto-check: notes
  • Dormice

    BitMiracle-AI/Dormice

    Operate Dormice self-hosted agent sandboxes — acquire a sandbox, run commands, move files, tune lifecycle policy — through the official E2B SDKs, the native HTTP API and SDK, or the dor CLI.

    1.4k GitHub stars~2.7k tokensUpdated 6 days ago
    Backend & APIsAuto-check: notes

More from ruvnet/RuView

All 24 skills in this repo
  • Reference for RuView's research-grade WiFi sensing features: multistatic fusion, cross-viewpoint geometry, persistent field models, RF tomography, intention signals and mesh security.

    97k GitHub stars~1.2k tokensUpdated today
    Auto-check: notes
  • Runs RuView's WiFi sensing applications: presence, vital signs, activity and fall detection, pose estimation, sleep monitoring and environment mapping.

    97k GitHub stars~1.1k tokensUpdated today
    Auto-check: notes
  • Tunes a deployed RuView WiFi-sensing system without changing code: firmware sdkconfig variants, NVS provisioning over serial, channel and MAC filtering, edge processing tiers and mesh slotting.

    97k GitHub stars~1.7k tokensUpdated today
    Auto-check: notes
  • Drives a web browser through the agent-browser CLI, using compact accessibility snapshots with element refs in place of the full DOM to keep context small.

    97k GitHub starsUsed in 4 repos~1.3k tokens
    Auto-check passed
  • Brings a RuView CSI sensing node online by building ESP32-S3 or ESP32-C6 firmware, flashing the board, provisioning WiFi and checking the serial output.

    97k GitHub stars~1.8k tokensUpdated today
    Auto-check: notes
  • Sets up and runs 60 GHz and 24 GHz mmWave radar sensing on ESP32 boards in RuView, alone or fused with WiFi CSI.

    97k GitHub stars~907 tokensUpdated today
    Auto-check: notes

Questions about RuView CLI, API and WASM

What does RuView CLI, API and WASM do?

Covers the RuView `wifi-densepose` command line binary, its Axum REST API and the WebAssembly builds for browsers and ESP32, for embedding or scripting RuView. RuView exposes three programmatic surfaces and this skill explains each. The `wifi-densepose` binary has a `version` command and a `mat` group for disaster survivor detection, with subcommands to scan a zone, check status, manage zones, list survivors with triage status, view alerts and export data as JSON or CSV.

When should I use RuView CLI, API and WASM?

RuView CLI, API and WASM fits situations like: calling RuView from another program through the CLI or HTTP API; scripting survivor scans and data exports from the shell; running the RuView API and dashboard from the Docker image; shipping the RuView stack to a browser or an ESP32 target as WebAssembly.

How do I install RuView CLI, API and WASM in Claude Code?

Run `npx skills add ruvnet/RuView --skill ruview-cli-api -a claude-code`. Or copy the skill folder (plugins/ruview/skills/ruview-cli-api in ruvnet/RuView) into .claude/skills/ruview-cli-api in your project. Claude Code loads it when a task matches its description.

How do I install RuView CLI, API and WASM in Codex?

Run `npx skills add ruvnet/RuView --skill ruview-cli-api -a codex`. Or copy the skill folder (plugins/ruview/skills/ruview-cli-api in ruvnet/RuView) into .agents/skills/ruview-cli-api in your project. Codex loads it when a task matches its description.

Can I use RuView CLI, API and WASM in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add ruvnet/RuView --skill ruview-cli-api -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/ruview-cli-api, .gemini/skills/ruview-cli-api, .github/skills/ruview-cli-api and .opencode/skills/ruview-cli-api in your project.

What does RuView CLI, API and WASM need to run?

Going by SKILL.md and its folder, RuView CLI, API and WASM needs the command-line tools its instructions call (cargo and docker). Our summary lists: Cargo (Rust toolchain) to build the CLI from the `v2` folder; Docker to run the API and dashboard image. Its frontmatter pre-approves these tools: Bash, Read, Write, Edit, Glob, Grep.

Does RuView CLI, API and WASM access the network?

SKILL.md contains no URLs. Its commands use docker, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is RuView CLI, API and WASM safe to install?

Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does RuView CLI, API and WASM use?

RuView CLI, API and WASM is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does RuView CLI, API and WASM use?

About 1.2k tokens (SKILL.md is roughly 4.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to RuView CLI, API and WASM?

Skills that share tags, products or a category with RuView CLI, API and WASM: C64 Meatloaf Debug (idolpx/meatloaf, 128 stars), Flash Displays (jtenniswood/espcontrol, 1.1k stars), New API (justrach/merjs, 356 stars) and Esp32 Test Plan (FastLED/FastLED, 7.5k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains RuView CLI, API and WASM?

ruvnet (a GitHub user) maintains it in ruvnet/RuView, which has 96,741 GitHub stars. The repository holds 24 skills in this directory. The repository was last updated on October 7, 2026.

Source: ruvnet/RuView on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.