ruview-cli-api

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.

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

82%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-built reference skill: lean, well-sectioned, and immediately actionable for the CLI and WASM surfaces, with appropriate pointers to deeper repo documentation. The weaker spots are the underspecified `mat zones` subcommands and the API section, which gestures at routes instead of listing them or pointing to one concrete file.

Suggestions

List the flags for `mat zones add/remove/update` in the subcommand table (or one example command) the way `mat scan` is documented, so the zones workflow is executable without reading crate source.

Replace "see the API module / docs for routes" with the concrete route list or a single named file (e.g. the router definition in wifi-densepose-api/src/lib.rs), and ideally add one curl example against the Docker image on :3000.

Dimension	Reasoning	Score
Conciseness	The body is lean and dense — compact subcommand and routing tables, copy-paste commands, and pointers to deeper docs, with no explanation of concepts Claude already knows. Every section earns its place, matching the anchor-5 example.	5 / 5
Actionability	Concrete executable commands for all main paths (cargo run with real flags, docker run -p 3000:3000, wasm-pack build --target web), but two gaps keep it below anchor 5: `mat zones` collapses add/remove/update into "plus add/remove/update" with no flags, and the API section defers routes to a vague "see the API module / docs for routes".	4 / 5
Workflow Clarity	Each surface has a clear build/run sequence and the skill closes with an explicit validation command ("cd v2 && cargo test -p … --no-default-features"). There are no error-recovery feedback loops, so it sits at anchor 4 rather than 5; no destructive or batch operations apply that would cap it lower.	4 / 5
Progressive Disclosure	No bundle files exist, and the body is a well-organized overview with one-level-deep, clearly signaled references (docs/wifi-mat-user-guide.md, v2/crates/wifi-densepose-wasm/README.md). The vague API pointer and inline subcommand-flag detail that could live in a separate reference file keep it at anchor 4 rather than 5.	4 / 5
	Total	17 / 20 Passed

Description

87%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description: it names the concrete surfaces and subcommands, gives an explicit multi-scenario "Use when…" trigger clause, and is scoped to an unmistakable product niche. The only weakness is that it describes tools to use rather than actions those tools perform, and lacks a few common trigger synonyms.

Dimension	Reasoning	Score
Specificity	Enumerates the three programmatic surfaces plus the six MAT subcommands ("scan/status/zones/survivors/alerts/export"), giving several specific capabilities. It stops short of anchor 5 because it names what to use rather than the actions performed — e.g. it never says what MAT does (detect survivors, export scan data).	4 / 5
Completeness	Explicitly answers both questions: the "what" is the CLI binary (with subcommands), the REST API, and the WASM builds, and the "when" is a concrete "Use when…" clause listing four trigger scenarios. This matches the anchor-5 example structure directly.	5 / 5
Trigger Term Quality	"scripting it from the shell", "exposing it over HTTP", "shipping it to the browser / ESP32-WASM3", and "integrating RuView into another program" are natural trigger phrases. Common variations like "command line", "embed", or "HTTP endpoints" are missing, so it falls short of comprehensive anchor-5 coverage.	4 / 5
Distinctiveness Conflict Risk	The description is tightly scoped to the RuView / wifi-densepose niche with product-specific binary and crate names, so it has a clear niche with distinct triggers and minimal conflict risk with other skills.	5 / 5
	Total	18 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: ruvnet/RuView
Path: plugins/ruview/skills/ruview-cli-api/SKILL.md
Commit: 5ef001b

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

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.