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

84%

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

76%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 highly actionable, dense configuration reference with concrete commands throughout. Its main weakness is workflow clarity: it is reference-shaped rather than sequenced, and the destructive NVS overwrite lacks an explicit validation feedback loop.

Suggestions

Add a short sequenced "change a deployed setting" workflow with a validation loop: read current NVS values from the serial boot log → write the full key set with provision.py → re-read the boot log to confirm the keys took effect.

For the destructive NVS overwrite, make the checkpoint explicit (e.g. a checklist: confirm `--force-partial` intent, verify no needed key is omitted) instead of a prose warning.

Consider moving the large provision-flag reference table into a separate bundled reference file linked from section 2, keeping the SKILL.md overview lean.

Dimension	Reasoning	Score
Conciseness	Dense and token-efficient, assuming Claude's competence (no explanations of what ESP32/NVS/CSI are), with mostly earned asides; a few parenthetical notes and the warning callout could be trimmed slightly.	4 / 5
Actionability	Copy-paste-ready commands cover the common cases — `cp .../sdkconfig.defaults.<variant>`, the full `provision.py --port COM8 ...` invocation, `cargo run -p wifi-densepose-sensing-server -- ...` modes, `node scripts/rf-scan.js --port 5006`, and the `docker run` line — with a justified `--help` pointer for the authoritative flag list.	5 / 5
Workflow Clarity	Content is organized as seven reference sections rather than a sequenced workflow, and the destructive NVS-namespace-overwrite operation is flagged with a warning but lacks an explicit validate→fix→retry feedback loop, capping this dimension at 3.	3 / 5
Progressive Disclosure	Well-structured with numbered sections and a Reference list pointing one level deep to ADRs/docs/other skills (no bundle files exist under references/scripts/assets to verify), though the large inlined provision-flag table is dense material that could live in a separate reference file.	4 / 5
	Total	16 / 20 Passed

Description

92%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, specific description that clearly scopes a niche configuration skill and provides an explicit Use-when trigger. Slightly jargon-heavy in its keyword list, but every term is a real natural phrase for the intended user.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete configuration actions — "ESP32 sdkconfig variants, NVS provisioning, WiFi channel / MAC filter overrides", "edge intelligence modules", "sensing-server flags", "multi-node mesh", "Cognitum Seed integration" — giving comprehensive coverage of what can be tuned.	5 / 5
Completeness	Explicitly answers both what ("Configure RuView — ...integration") and when ("Use when adjusting how a deployed RuView system behaves without changing code") with a concrete trigger phrase.	5 / 5
Trigger Term Quality	Includes the natural trigger phrase "Use when adjusting how a deployed RuView system behaves without changing code" plus domain terms users of this system would say (sdkconfig, NVS, channel, mesh), though the term list is jargon-dense and a few common phrasings are absent.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (tuning a deployed RuView system) with distinct, product-specific triggers, so it is unlikely to fire for an unrelated skill.	5 / 5
	Total	19 / 20 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: a76adc3

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