CtrlK
BlogDocsLog inGet started
Tessl Logo

onboard

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

65

Quality

78%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

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

Quality

Content

93%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 body is lean, highly actionable, and well-structured with concrete commands per path and appropriate delegation to sibling skills; the only gap is that per-path validation feedback loops are implicit rather than spelled out.

DimensionReasoningScore

Conciseness

The ~25-line body is lean and assumes Claude's competence; the 'not a camera' CSI callout is non-obvious domain knowledge that earns its place, and commands are inline with no padded explanations.

5 / 5

Actionability

Each path ships copy-paste-ready commands (docker run, cargo test, cargo run -- --help) covering the common cases, matching the anchor-5 'fully executable' example.

5 / 5

Workflow Clarity

A clear Pick-a-path → Then sequence with checkpoints present (test pass count, open-localhost verification, claim-check routing), but per-path 'verify it worked' feedback loops are mostly implicit rather than explicit.

4 / 5

Progressive Disclosure

Under 50 lines with no bundle files needed; well-organized sections and clearly signaled one-level-deep cross-skill references (provision-node, calibrate-room, verify), matching the simple-skill exception for a 5.

5 / 5

Total

19

/

20

Passed

Description

62%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 and distinctive with a clear niche and three concrete paths, but it lacks an explicit 'Use when...' trigger clause and relies on technical jargon over natural user phrases, capping completeness and trigger quality.

Suggestions

Add an explicit 'Use when...' clause (e.g., 'Use when onboarding to RuView or setting up WiFi sensing') to lift completeness above 3.

Include natural user-facing trigger terms like 'set up', 'install', or 'get started with RuView' alongside the technical path names.

Keep the three named paths but pair each with a plain-language cue (e.g., 'docker-demo — try it without hardware') to broaden trigger coverage.

DimensionReasoningScore

Specificity

Names three concrete path options (docker-demo, repo-build, live-esp32) plus 'run the next concrete step', listing several specific actions with only minor coverage gaps, matching the anchor-4 example.

4 / 5

Completeness

The 'what' is clear (path picker with three named paths), but there is no 'Use when...' or equivalent explicit trigger guidance, which caps completeness at 3 per the rubric guideline.

3 / 5

Trigger Term Quality

Keywords are mostly project-internal jargon (WiFi-DensePose, live-esp32) rather than natural phrases a user would say; relevant terms exist but common variations/synonyms like 'set up' or 'install' are missing.

3 / 5

Distinctiveness Conflict Risk

Names a specific product (RuView/WiFi-DensePose) with a distinct three-path niche and minimal overlap with other skills, matching the anchor-5 'clear niche' example.

5 / 5

Total

15

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
ruvnet/RuView
Reviewed

Table of Contents

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.