ruview-configure

Configure RuView — ESP32 sdkconfig variants, NVS provisioning, WiFi channel / MAC filter overrides (ADR-060), edge intelligence modules (ADR-041), sensing-server flags, multi-node mesh, and Cognitum Seed integration. Use when adjusting how a deployed RuView system behaves without changing code.

Quality

88%

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

92%

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

A concise, highly actionable, well-sequenced configuration reference with explicit safety guidance for the destructive NVS operation. The main weakness is progressive disclosure: most reference material is inline with no dedicated bundle files to offload detail into.

Suggestions

Move dense reference material (e.g., the full NVS flag table, edge-module script listing) into separate bundle files under references/ and link to them one level deep, keeping SKILL.md as an overview.

For referenced paths that live in the repo (docs/adr/, scripts/, firmware/), make clear which are skill-bundled versus repo-relative so navigation expectations are unambiguous.

Dimension	Reasoning	Score
Conciseness	The body is dense and table-driven ('--pres-thresh (50) --fall-thresh (15000 → 15.0 rad/s²)') with almost no explanatory padding of concepts Claude already knows (NVS/CSI/Cognitum), matching the 'lean and efficient; every token earns its place' anchor rather than the unnecessary-explanation case at level 2.	3 / 3
Actionability	Provides copy-paste-ready executable commands ('cp firmware/esp32-csi-node/sdkconfig.defaults.<variant> ...', 'python firmware/esp32-csi-node/provision.py --port COM8 ...', 'cargo run -p wifi-densepose-sensing-server -- --pretrain ...') plus a flag table with defaults, matching the 'fully executable; copy-paste ready' anchor.	3 / 3
Workflow Clarity	Sections are numbered and sequenced (build-time → runtime → server → edge → mesh → integration → app), and the riskiest destructive operation (NVS wholesale replacement) carries explicit validation guidance ('Read the device's current values off the serial boot log first', --dry-run, --force-partial), so it avoids the level-2 cap for missing validation on destructive ops.	3 / 3
Progressive Disclosure	Content is organized into clear sections with a final Reference list, but no bundle files (references/ scripts/ assets/) exist — referenced paths (docs/, scripts/, firmware/) point into the repo, and dense inline reference material (the full NVS flag table, edge-module lists) arguably belongs in separate one-level-deep files, matching the level-2 anchor rather than the well-signaled split structure of level 3.	2 / 3
	Total	11 / 12 Passed

Description

85%

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 specific, well-scoped description that clearly states capabilities and an explicit use trigger for a distinct named system. The main weakness is the trigger clause, which is somewhat abstract rather than naming the concrete situations a user would actually say.

Suggestions

Make the 'Use when' trigger concrete by listing the situations a user would name, e.g. 'Use when provisioning a RuView node over serial, changing WiFi channel/MAC filters, enabling edge modules, or tuning sensing-server flags — without changing code.'

Consider adding common natural phrasings (e.g., 'tune', 'provision', 'set up NVS') so the description matches terms users actually say.

Dimension	Reasoning	Score
Specificity	Enumerates concrete capabilities — 'ESP32 sdkconfig variants, NVS provisioning, WiFi channel / MAC filter overrides (ADR-060), edge intelligence modules (ADR-041), sensing-server flags, multi-node mesh, and Cognitum Seed integration' — matching the 'lists multiple specific concrete actions' anchor rather than the partial coverage at level 2.	3 / 3
Completeness	Both 'what' (the capability list) and 'when' ('Use when adjusting how a deployed RuView system behaves without changing code') are explicitly stated, matching the level-3 anchor and not the level-2 case where 'when' is only implied.	3 / 3
Trigger Term Quality	The 'Use when' clause ('adjusting how a deployed RuView system behaves without changing code') is abstract rather than enumerating the concrete situations a user would name (e.g., provisioning a node, changing a WiFi channel); it has relevant domain terms but misses common natural phrasings, so it sits at level 2 rather than the strong coverage of level 3.	2 / 3
Distinctiveness Conflict Risk	The named RuView system with ESP32/sdkconfig/NVS/Cognitum Seed specifics carves a distinct niche unlikely to trigger for unrelated skills, matching the level-3 anchor.	3 / 3
	Total	11 / 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: 4 missing	Warning

	Total	15 / 16 Passed

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

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