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

90%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.

An exemplary configuration reference: dense, fully executable, and free of padding, with hard-won operational warnings (wholesale NVS erase, mock-mode Kconfig bug) that only this project would know. The residual gaps are structural — the flag table belongs in a reference file, and post-flash verification steps are absent.

Suggestions

Move the full provision.py flag table into a references/ file (e.g. references/provision-flags.md) and keep only the most common flags inline in SKILL.md, adding a clearly signaled pointer.

Add a short post-flash verification step to the NVS provisioning workflow (e.g. re-read the serial boot log csi_cfg/adaptive_ctrl lines to confirm the written values), closing the destructive-operation feedback loop.

Verify every referenced path (docs/adr/ ADR numbers, scripts/*.js helpers, sibling skill names like ruview-hardware-setup) actually exists, since unverifiable pointers weaken navigation.

Dimension	Reasoning	Score
Conciseness	The body is lean and every token carries project-specific knowledge Claude cannot already know — flag defaults ("--fall-thresh (15000 → 15.0 rad/s²)"), the Windows cp1252 crash workaround, and issue-linked warnings ("NVS namespace is replaced wholesale (issue #391)"). No filler or concept explanations; matches the "every token earns its place" anchor.	5 / 5
Actionability	Fully executable, copy-paste-ready commands cover the common cases: the variant switch ("cp firmware/esp32-csi-node/sdkconfig.defaults.<variant> ..."), a complete provision.py invocation with real values, five cargo run mode examples, and node scripts with ports. Matches the top anchor.	5 / 5
Workflow Clarity	Sections are clearly organized by config surface and the destructive NVS operation has an explicit pre-flight checkpoint ("Read the device's current values off the serial boot log first"), so it clears the destructive-operation cap. It is not a 5 because there is no post-flash verification step and the seven sections present parallel surfaces rather than an explicitly sequenced workflow with feedback loops.	4 / 5
Progressive Disclosure	Good structure: a well-sectioned overview with one-level-deep, clearly named pointers (docs/adr/, docs/edge-modules/, docs/tutorials/cognitum-seed-pretraining.md, sibling skills) and a consolidated Reference section. Not a 5 because no bundle files exist to offload detail — the large inline provision.py flag table is reference material that belongs in a separate file — and referenced repo paths cannot be verified against an actual bundle.	4 / 5
	Total	18 / 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: specific, third-person, with an explicit Use-when trigger clause and a clearly demarcated niche anchored by unique project names. The only minor gap is that action variety is carried by one verb ("Configure") plus an enumerated object list rather than multiple distinct action verbs.

Dimension	Reasoning	Score
Specificity	The description enumerates seven concrete configuration surfaces ("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"), which matches the anchor for several specific items with minor gaps. It is not a 5 because the only action verb is a single generic "Configure" — the objects are specific but the actions are not varied.	4 / 5
Completeness	It explicitly answers both questions: the "what" is the enumerated list of configurable surfaces, and the "when" is the concrete clause "Use when adjusting how a deployed RuView system behaves without changing code". This matches the top anchor exactly.	5 / 5
Trigger Term Quality	Includes natural terms a RuView user would say — "sdkconfig", "NVS provisioning", "WiFi channel", "MAC filter", "mesh", "sensing-server flags" — giving good keyword coverage per the anchor. It falls short of a 5 because common variations like "node setup", "tuning", or "flag changes" are absent.	4 / 5
Distinctiveness Conflict Risk	"RuView", "Cognitum Seed", and the ESP32/ADR-specific terms define a clear niche with distinct triggers and minimal conflict risk with any other skill. Not a 4 because no closely related skill would plausibly compete for these triggers.	5 / 5
	Total	18 / 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: 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.