camera-provider-reolink

Reolink camera integration — RTSP and HTTP API

Quality

61%

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 ./skills/camera-providers/reolink/SKILL.md

Quality

Content

65%

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

The body is commendably concise and well structured, but it stops at setup without showing how to use the camera capabilities, and most of the scripts referenced in the frontmatter are missing. Adding a usage example and resolving the broken script references would substantially improve it.

Suggestions

Add a short usage example showing how a capability is invoked (e.g., the ready/live_stream/snapshot event flow) so the body is actionable beyond initial setup.

Describe the runtime workflow with a verification step (e.g., confirm a snapshot file was emitted) to give the operational sequence explicit checkpoints.

Either add the three missing referenced scripts (scripts/discover.py, scripts/stream.py, scripts/snapshot.py) or remove their frontmatter capability entries so referenced paths resolve.

Dimension	Reasoning	Score
Conciseness	The body is lean and efficient with no padding or explanation of concepts Claude already knows; every line (model list, two setup commands) earns its place.	3 / 3
Actionability	The Setup section gives copy-paste-ready commands, but the body provides no executable example or invocation guidance for the actual capabilities (clip capture, snapshot, live stream), leaving the core usage incomplete.	2 / 3
Workflow Clarity	Setup is a clear two-step sequence, but the body describes no operational workflow for the camera actions themselves and includes no validation or verification checkpoint, matching the "sequence present but checkpoints missing" anchor.	2 / 3
Progressive Disclosure	Sections are well organized and the skill is short, but the body markdown carries no file navigation and the frontmatter references four scripts (feed.py, discover.py, stream.py, snapshot.py) of which only feed.py exists, leaving three broken referenced paths.	2 / 3
	Total	9 / 12 Passed

Description

57%

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 clearly scoped to a distinct Reolink niche, but it lacks concrete action verbs and any explicit "when to use" trigger guidance. Adding a Use-when clause and natural user terms would meaningfully raise it.

Suggestions

Add an explicit trigger clause such as "Use when integrating Reolink cameras, capturing motion clips, taking snapshots, or streaming RTSP feeds" to address the missing "when" and lift completeness.

Replace the abstract word "integration" with concrete action verbs (capture, stream, snapshot, discover) to improve specificity.

Include natural user-facing terms like "security camera", "IP camera", "live stream", and "snapshot" to broaden trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Names the domain ("Reolink camera") and two concrete technologies ("RTSP" and "HTTP API"), but uses the abstract term "integration" with no action verbs like capture, stream, or snapshot, so it falls short of listing multiple specific concrete actions.	2 / 3
Completeness	It states what the skill does (Reolink camera integration via RTSP and HTTP API) but provides no "Use when..." trigger clause or equivalent explicit guidance on when to invoke it, which caps completeness at 2 per the rubric guideline.	2 / 3
Trigger Term Quality	"Reolink camera" is a natural term a user would say, but the description omits common variations such as "security camera", "IP camera", "live stream", or "snapshot", leaving only partial keyword coverage.	2 / 3
Distinctiveness Conflict Risk	The Reolink-specific niche is clearly distinguishable from other skills and unlikely to trigger for the wrong skill, matching the "clear niche with distinct triggers" anchor.	3 / 3
	Total	9 / 12 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
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
Commit: 2264fcb

Reviewed: 1 day 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.