provision-node

Build, flash, and provision an ESP32-S3/C6 CSI node for RuView — firmware variant choice, ESP-IDF Windows-subprocess flow, NVS/WiFi/channel/MAC-filter overrides.

Quality

78%

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

Fix and improve this skill with Tessl

tessl review fix ./harness/ruview/.claude/skills/provision-node/SKILL.md

Quality

Content

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

The content is highly actionable and well-structured with a final validation gate, scoring strongly across the board. The main lever is converting pinned version strings into a maintainable form and adding a retry loop for the confirm step.

Suggestions

Add a brief "If no callbacks" remediation loop (re-check port/baud, re-flash, then re-confirm) to turn the final checkpoint into a fix-and-retry feedback loop and lift workflow_clarity to 5.

Move or label pinned versions (release v0.8.1-esp32, ESP-IDF v5.4, board rev v0.2) under a clearly dated/pinnable note so they do not penalize conciseness as they age.

Add C6 flash offsets (or a one-line pointer to where they live) so the flashing step is executable for all three listed variants.

Dimension	Reasoning	Score
Conciseness	The body is lean, assumes Claude's competence, and adds only project-specific knowledge (MSYSTEM stripping, PR-fix context); held at 4 rather than 5 because pinned version numbers (v0.8.1-esp32, ESP-IDF v5.4, rev v0.2) are time-sensitive and not placed in a deprecated/old-patterns section.	4 / 5
Actionability	Copy-paste-ready commands are given for the common S3 path — esptool write_flash with exact offsets and provision.py with concrete flags — plus explicit PASS criteria; the missing C6 flash offsets are a minor gap for an edge variant.	5 / 5
Workflow Clarity	A clear four-step sequence (Pick variant → Flash → Provision → Confirm CSI) ends with an explicit validation checkpoint ("No callbacks → the node isn't capturing; do not proceed"), but it lacks a fix-and-retry feedback loop and has no checkpoint between flash and provision.	4 / 5
Progressive Disclosure	This is a sub-50-line single-purpose skill with no external references needed and four well-organized numbered sections, matching the simple-skill exception that allows a 5.	5 / 5
	Total	18 / 20 Passed

Description

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

The description is specific, technically rich, and clearly distinguishable, but it omits an explicit "Use when..." trigger clause, which caps its completeness. Adding a one-line trigger condition would lift the completeness score.

Suggestions

Append an explicit "Use when..." clause naming natural triggers, e.g. "Use when provisioning or flashing an ESP32 CSI node for RuView, or when the user mentions ESP32 CSI, flashing esptool, or NVS/WiFi/channel/MAC overrides."

Add a couple of natural synonyms ("set up", "configure", "deploy") alongside the technical terms to broaden trigger coverage.

Dimension	Reasoning	Score
Specificity	"Build, flash, and provision" name three concrete actions, and "firmware variant choice, ESP-IDF Windows-subprocess flow, NVS/WiFi/channel/MAC-filter overrides" enumerate specific sub-areas; falls short of 5 only because the trailing list reads as topic areas rather than fully enumerated discrete actions.	4 / 5
Completeness	The "what" is clearly stated ("Build, flash, and provision an ESP32-S3/C6 CSI node") but there is no "Use when..." clause or equivalent trigger guidance, which caps completeness at 3 per the judging guidelines.	3 / 5
Trigger Term Quality	Domain-natural terms a user would say (ESP32-S3/C6, flash, provision, CSI, WiFi, NVS, channel, MAC-filter) are well covered; not a 5 because common synonyms like "set up", "configure", or "deploy" are absent.	4 / 5
Distinctiveness Conflict Risk	The RuView-specific ESP32-S3/C6 CSI niche with ESP-IDF Windows-subprocess detail is highly distinct and unlikely to trigger for the wrong skill.	5 / 5
	Total	16 / 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: harness/ruview/.claude/skills/provision-node/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.