CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

camera-provider-eufy

Eufy camera integration — local RTSP streaming and event clips

Quality

61%

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 ./skills/camera-providers/eufy/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

51%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 admirably concise and well-sectioned, but it provides almost no actionable guidance for the skill's actual capabilities and no operational workflow. Referenced capability scripts are partly missing from the bundle, weakening progressive disclosure.

Suggestions

Add concrete, executable examples for each capability (e.g. how to invoke scripts/stream.py to get an RTSP URL, scripts/feed.py to capture clips), not just the venv setup.

Provide a sequenced workflow with validation (e.g. discover cameras → verify RTSP URL reachable → start stream → capture clip → confirm clip exists) since clip capture is a batch/event operation.

Resolve the bundle mismatch: either add scripts/discover.py and scripts/stream.py or correct the frontmatter capability paths so referenced files exist.

DimensionReasoningScore

Conciseness

The body is lean and efficient — a one-line purpose statement plus a minimal setup block — with no padding or over-explanation of concepts Claude already knows, matching the 'every token earns its place' anchor.

5 / 5

Actionability

Only the setup commands are executable; the core capabilities (live stream, discover cameras, event clips) are described at a high level with no concrete code, commands, or invocation examples in the body.

2 / 5

Workflow Clarity

Beyond setup there is no sequenced workflow for the camera operations, and event-clip/streaming operations lack any validation checkpoints, fitting the 'rough sequence, many gaps, validation absent' anchor.

2 / 5

Progressive Disclosure

The body is short and sectioned, but frontmatter references scripts/discover.py and scripts/stream.py that do not exist in the bundle (only feed.py is present), leaving references unclear and structurally incomplete.

3 / 5

Total

12

/

20

Passed

Description

53%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 concise and names a specific vendor niche with two concrete capabilities, but it omits any explicit 'when to use' trigger guidance, which caps completeness and limits trigger-term quality. It is distinctive but under-specified for activation.

Suggestions

Add a 'Use when ...' clause naming natural triggers, e.g. 'Use when integrating Eufy cameras, setting up RTSP live streams, or capturing event clips for analysis.'

Expand action coverage with concrete verbs (discover cameras, pull RTSP URLs, download event-triggered clips) to lift specificity from 3 to 4-5.

Include common synonyms/extensions users might say ('Eufy HomeBase', 'eufy-security', '.mkv/.mp4 clips') to broaden trigger-term coverage.

DimensionReasoningScore

Specificity

Names the domain ('Eufy camera integration') and two concrete actions ('local RTSP streaming', 'event clips'), matching the anchor for 1-2 concrete actions without comprehensive coverage.

3 / 5

Completeness

Provides a clear 'what' (Eufy integration with RTSP streaming and event clips) but has no 'Use when...' or equivalent trigger guidance, so completeness is capped at 3 per the missing-trigger guideline.

3 / 5

Trigger Term Quality

Includes relevant niche terms ('Eufy camera', 'RTSP streaming', 'event clips') but lacks common variations or synonyms a user might naturally say, fitting the 'some relevant keywords' anchor rather than comprehensive coverage.

3 / 5

Distinctiveness Conflict Risk

The Eufy brand plus specific streaming/clip actions carve a mostly distinct niche with only minor overlap risk against generic camera or RTSP skills, sitting above the 'somewhat specific' anchor.

4 / 5

Total

13

/

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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

SharpAI/DeepCamera

Path

skills/camera-providers/eufy/SKILL.md

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.