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

83%

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

100%

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

The content is concise, actionable, and well-sequenced with an explicit validation checkpoint, and its organization is appropriate for a short single-purpose skill.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes competence — concrete offsets, pinned commands, and domain-specific notes (#1000, #1107) earn their tokens without explaining concepts Claude already knows.	3 / 3
Actionability	Provides fully executable, copy-paste-ready commands: the esptool write_flash line with exact offsets and the provision.py invocations with named flags.	3 / 3
Workflow Clarity	A clear four-step sequence (Pick variant → Flash → Provision → Confirm CSI) culminates in an explicit validation checkpoint with PASS criteria and a 'do not proceed' guard.	3 / 3
Progressive Disclosure	Under 50 lines with no external references needed; the numbered sections are well-organized, satisfying the rubric's allowance for simple skills to score 3 on structure alone.	3 / 3
	Total	12 / 12 Passed

Description

67%

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 and clearly scoped to a narrow niche with concrete actions, but it lacks an explicit 'Use when' trigger clause and leans on technical jargon over natural user phrasing.

Suggestions

Add an explicit 'Use when ...' trigger clause (e.g., 'Use when provisioning or flashing an ESP32-S3/C6 CSI node for RuView') to raise completeness.

Soften jargon with natural phrasings a user would actually say, such as 'flash an ESP32 board' or 'set up a CSI sensing node'.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'Build, flash, and provision' plus 'firmware variant choice, ESP-IDF Windows-subprocess flow, NVS/WiFi/channel/MAC-filter overrides' — naming specific operations rather than abstract language.	3 / 3
Completeness	Clearly states what the skill does, but there is no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 2 per the rubric.	2 / 3
Trigger Term Quality	Relevant domain keywords exist ('flash', 'provision', 'ESP32-S3/C6', 'CSI node') but the phrasing is heavily jargon-laden and omits common natural variations a user might say.	2 / 3
Distinctiveness Conflict Risk	The niche is highly specific — provisioning an ESP32-S3/C6 CSI node for RuView with named overrides — making it unlikely to trigger for the wrong skill.	3 / 3
	Total	10 / 12 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: 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.