CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

camera-provider-reolink

Reolink camera integration — RTSP and HTTP API

Quality

64%

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/reolink/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

68%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 concise and cleanly structured but thin on operational value: it covers setup well yet gives no usage examples or workflow for the camera capabilities it advertises. The bundle is also incomplete, with three of four referenced scripts missing.

Suggestions

Add a Usage section with executable examples for each capability (e.g. the snapshot HTTP API call and the RTSP URL format), drawing on the patterns already in scripts/feed.py.

Document the provider command/response protocol (stdin commands like 'snapshot'/'stop' and emitted JSON events) so the operational workflow is clear.

Either add the missing scripts (discover.py, stream.py, snapshot.py) or remove their capability entries so advertised references resolve to real files.

DimensionReasoningScore

Conciseness

The body is lean and efficient: a one-line intro, a compact supported-models list, and a minimal setup snippet, with no padding or explanation of concepts Claude already knows.

5 / 5

Actionability

The Setup section gives executable commands (venv, pip install), but the body provides no usage examples or invocation guidance for the actual capabilities (snapshot, live_stream, clip_feed), leaving key execution details missing.

3 / 5

Workflow Clarity

A setup sequence is present, but there is no operational workflow for the provider capabilities and no validation/verification checkpoints, matching the 'steps present but checkpoints missing' anchor.

3 / 5

Progressive Disclosure

The body is well-organized into clear sections (intro, Supported Models, Setup) and stays appropriately brief; the minor gap is that the frontmatter advertises four capability scripts while the bundle only contains feed.py, and the body does not navigate to the detailed materials.

4 / 5

Total

15

/

20

Passed

Description

43%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 distinctive thanks to the Reolink brand but is vague on concrete actions and entirely missing a 'Use when' trigger clause, capping its completeness and specificity. It needs explicit capabilities and trigger guidance.

Suggestions

Add concrete actions, e.g. 'Capture motion clips, take snapshots, stream live RTSP feeds, and discover cameras via ONVIF.'

Add a 'Use when...' clause, e.g. 'Use when the user mentions Reolink cameras, RTSP streams, IP camera snapshots, or camera discovery.'

Include natural synonyms such as 'security camera', 'IP camera', and 'NVR' to broaden trigger coverage.

DimensionReasoningScore

Specificity

The description names the domain ("Reolink camera") and the technologies ("RTSP and HTTP API") but uses the generic action "integration" rather than listing concrete capabilities such as snapshot, live stream, discovery, or clip capture, so it sits below the midpoint.

2 / 5

Completeness

The 'what' is vague ('camera integration' does not say what can be done) and there is no 'when'/'Use when' clause at all, matching the 'vague what and no when' anchor.

2 / 5

Trigger Term Quality

"Reolink camera" and "RTSP" are relevant natural terms, but common variations a user might say (IP camera, security camera, NVR, snapshot, footage) are absent, matching the 'some relevant keywords but missing common variations' anchor.

3 / 5

Distinctiveness Conflict Risk

The "Reolink" brand name plus the RTSP/HTTP API narrowing defines a clear niche with highly distinct triggers and minimal overlap with other skills.

5 / 5

Total

12

/

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/reolink/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.