onboard

Zero-to-sensing path picker for RuView (WiFi-DensePose) — pick docker-demo, repo-build, or live-esp32 and run the next concrete step.

Quality

77%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./harness/ruview/.claude/skills/onboard/SKILL.md

Quality

Content

87%

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

The body is lean, highly actionable with copy-paste commands, and well-structured for a simple router skill; the only gap is workflow_clarity, where a validation checkpoint exists but no explicit feedback loops accompany the build/deploy steps.

Suggestions

Add an explicit verify/feedback step after the docker and cargo paths (e.g. confirm the dashboard loads or tests pass before routing on), to lift workflow_clarity toward a 3.

Note that the '1,031+ tests pass' figure is a moving target; consider framing it as 'tests should pass' with the command as the source of truth.

Dimension	Reasoning	Score
Conciseness	The 30-line body is lean and every section earns its place; the 'First fact to set' paragraph is non-obvious project guardrail (not a camera, measure against baseline) rather than generic concepts Claude already knows. Not a 2 because there is no padding or generic concept explanation to tighten.	3 / 3
Actionability	Provides fully executable, copy-paste-ready commands ('docker run -p 8000:8000 ruvnet/wifi-densepose', 'cd v2 && cargo test --workspace --no-default-features', 'cargo run -p wifi-densepose-cli -- --help', 'ruview_onboard {path}'). Not a 2 because these are concrete executable commands, not pseudocode or vague direction.	3 / 3
Workflow Clarity	A clear sequence exists (pick a path → run → route to next skill) and there is one validation checkpoint ('run ruview_claim_check on any report before you quote a number'), but there are no feedback loops (validate → fix → retry) or checkpoints on the build/docker steps. Not a 3 because it lacks the explicit validation/feedback-loop completeness of the top anchor; not a 1 because steps are clearly sequenced.	2 / 3
Progressive Disclosure	Under 50 lines with no external bundle files needed (references/scripts/assets are absent) and well-organized sections ('## Pick a path', '## Then'), satisfying the simple-skill allowance for a top score. Not a 2 because content is appropriately inline for a router skill and sibling-skill pointers are clearly signaled.	3 / 3
	Total	11 / 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 distinctively scoped to RuView onboarding with concrete path options, but it leans on project jargon and lacks an explicit 'Use when...' trigger clause, capping completeness and trigger-term quality.

Suggestions

Add an explicit trigger clause, e.g. 'Use when onboarding to or setting up RuView (WiFi-DensePose) sensing.'

Include natural user phrasings like 'get started', 'set up', or 'install RuView' alongside the path names to improve trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Names three concrete path options ('docker-demo, repo-build, or live-esp32') plus the action 'run the next concrete step' — multiple specific concrete actions rather than vague language. Not a 2 because the paths are concrete enumerated choices, not just a named domain.	3 / 3
Completeness	Clearly answers 'what' (a path picker that picks among three paths and runs the next step), but 'when' is only implied — there is no 'Use when...' clause or explicit trigger guidance, which the guidelines say caps completeness at 2. Not a 3 because no explicit 'when' triggers are present.	2 / 3
Trigger Term Quality	Includes the project name 'RuView' and path labels, but the dominant vocabulary is technical jargon ('WiFi-DensePose', 'Channel State Information' context, path names) and it omits natural phrasings a user would say like 'onboard', 'set up', 'get started', or 'install RuView'. Not a 3 because common natural variations are missing; not a 1 because 'RuView' is a real keyword a user would say.	2 / 3
Distinctiveness Conflict Risk	Tightly scoped to a single project ('RuView (WiFi-DensePose)') with three named paths, giving it a clear niche unlikely to trigger for unrelated skills. Not a 2 because it is far more specific than generic 'Works with document files'-style overlap.	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/onboard/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.