ruview-mmwave

Set up and run RuView mmWave / FMCW radar sensing — ESP32-C6 + Seeed MR60BHA2 (60 GHz, heart rate / breathing rate / presence) and HLK-LD2410 (24 GHz, presence + distance), plus mmWave↔WiFi-CSI sensor fusion (48-byte fused vitals, MR60BHA2/LD2410 auto-detect, v0.5.0+). Use when the deployment includes a millimetre-wave radar alongside or instead of WiFi CSI.

Quality

93%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

High

Do not use without reviewing

Quality

Content

87%

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

Concise, actionable, and well-structured with copy-paste commands and one-level-deep references. Its only weakness is workflow clarity: the firmware build/flash sequence is delegated externally and validation appears as a trailing reference rather than an inline checkpoint within the fusion workflow.

Suggestions

Inline the key build/flash validation step (e.g., a 'Confirm fused vitals appear on serial monitor before proceeding' checkpoint) in section 1 rather than deferring all validation to the trailing Reference line.

Add an explicit feedback loop for firmware failures (e.g., 'If the serial monitor reports no radar detected, re-check UART wiring/port and re-provision') so the recovery path is concrete.

Briefly state the expected 48-byte fused-vitals output format or a sanity-check command so the 'confirm it worked' step is unambiguous.

Dimension	Reasoning	Score
Conciseness	Lean and information-dense: dense hardware/comparison tables and concrete commands assume Claude's competence with no padding about what radar or CSI is. Every token earns its place.	3 / 3
Actionability	Provides copy-paste-ready commands with real flags and arguments ('python firmware/esp32-csi-node/provision.py --port COM8 --ssid ...', 'python scripts/mmwave_fusion_bridge.py'), fully executable rather than pseudocode.	3 / 3
Workflow Clarity	Sections 1–4 give a sequence, but the firmware/provision workflow delegates the build/flash sequence to an external skill and only mentions validation ('Validate firmware changes with the QEMU helpers and ruview-verify') as a trailing reference rather than an inline checkpoint, so feedback loops are implicit, not at the level-3 'explicit validation steps' anchor.	2 / 3
Progressive Disclosure	A concise overview with well-signaled, one-level-deep references ('README.md', 'docs/user-guide.md', 'scripts/mmwave_fusion_bridge.py', 'examples/medical/README.md', 'ADR-094') and clear section organization; no bundle files exist, so references are external repo paths rather than nested bundles.	3 / 3
	Total	11 / 12 Passed

Description

100%

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, third-person description that names concrete capabilities and hardware, provides natural trigger terms, and includes an explicit 'Use when' clause. It clearly conveys both what the skill does and when to invoke it.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions ('Set up and run RuView mmWave / FMCW radar sensing', 'mmWave↔WiFi-CSI sensor fusion', 'auto-detect') tied to named hardware, matching the 'Lists multiple specific concrete actions' anchor rather than the partial-coverage level 2.	3 / 3
Completeness	Explicitly answers both 'what' (set up/run radar sensing and fusion) and 'when' via 'Use when the deployment includes a millimetre-wave radar alongside or instead of WiFi CSI.'	3 / 3
Trigger Term Quality	Includes natural terms a user would say — 'mmWave radar', 'FMCW radar', 'millimetre-wave radar', 'WiFi CSI' — giving good coverage of common phrasings, not just jargon.	3 / 3
Distinctiveness Conflict Risk	Clear niche (mmWave/FMCW radar + WiFi-CSI fusion) with hardware-specific triggers unlikely to fire for unrelated skills.	3 / 3
	Total	12 / 12 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
referenced_paths_exist	Referenced path issues: 5 missing	Warning

	Total	15 / 16 Passed

Repository: ruvnet/RuView
Path: plugins/ruview/skills/ruview-mmwave/SKILL.md
Commit: d9dfea2

Reviewed: about 13 hours 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.