CtrlK
BlogDocsLog inGet started
Tessl Logo

ruview-applications

Run RuView sensing applications — presence/occupancy, breathing & heart rate, activity & fall detection, 17-keypoint pose estimation (WiFlow), sleep monitoring & apnea screening, environment mapping, Mass Casualty Assessment (MAT), and the 3D point-cloud fusion demo. Use when someone wants to actually *do* something with a working RuView setup.

70

Quality

86%

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

SKILL.md
Quality
Evals
Security

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 efficient, highly actionable catalogue skill with executable recipes and clear modality-selection guidance. The only gaps are the lack of an explicit sequenced workflow (not really needed for a reference catalogue) and slightly dense reference listings.

DimensionReasoningScore

Conciseness

Lean and information-dense: a compact catalogue table and direct executable commands with no concept over-explanation; every line earns its place.

5 / 5

Actionability

Copy-paste ready commands (docker run, cargo run, node scripts, python) with concrete crate/entry-point references covering the common run cases.

5 / 5

Workflow Clarity

'Picking the right modality' gives clear scenario-to-app decision guidance, but the recipes are independent reference commands rather than a sequenced multi-step workflow with checkpoints (none needed here as there are no destructive/batch ops).

4 / 5

Progressive Disclosure

Well-organized sections with clearly signaled one-level-deep references to examples/docs/ADRs/sibling skills; the dense ADR/path enumeration in the Reference section is the only minor organization gap.

4 / 5

Total

18

/

20

Passed

Description

83%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, specific description with comprehensive coverage of concrete capabilities and a clear niche. Its main weakness is the generic 'Use when someone wants to actually do something' trigger, which lacks concrete user-facing trigger phrases.

Suggestions

Replace 'Use when someone wants to actually do something with a working RuView setup' with concrete trigger phrases, e.g. 'Use when detecting presence through walls, measuring breathing/heart rate contactlessly, or running WiFlow pose estimation on a live ESP32 setup'.

Add common natural synonyms/variants users might say (e.g. 'through-wall sensing', 'contactless vitals', 'WiFi pose') to broaden trigger-term coverage.

DimensionReasoningScore

Specificity

Lists many concrete sensing applications with specifics (breathing 6-30 BPM, 17-keypoint pose, fall detection, MAT, 3D fusion) — comprehensive coverage of concrete actions.

5 / 5

Completeness

Clear 'what' (full app catalogue) and explicit 'when' clause, but the 'when' ('do something with a working RuView setup') is vague rather than concrete trigger phrases.

4 / 5

Trigger Term Quality

Good natural terms ('breathing & heart rate', 'fall detection', 'pose estimation', 'apnea screening') but the trigger clause 'wants to actually do something' is generic and misses synonyms/variants.

4 / 5

Distinctiveness Conflict Risk

A clearly defined niche with named RuView apps and a hardware precondition ('working RuView setup'); minimal overlap with other skills.

5 / 5

Total

18

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

referenced_paths_exist

Referenced path issues: 8 missing

Warning

Total

15

/

16

Passed

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.