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

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/camera-providers/eufy/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 content is admirably lean and well-sectioned, but its actionability and structure are undermined by missing bundle files (requirements.txt and two of three capability scripts) and the absence of any concrete usage examples for the capabilities. Fixing the broken references and adding an executable usage example would most improve the score.

Suggestions

Add the missing bundle files referenced in frontmatter (scripts/discover.py, scripts/stream.py) and requirements.txt, or remove the references so navigation resolves.

Include a concrete usage example, e.g. an example RTSP URL format for live_stream and a sample feed.py invocation for clip_feed.

Add a brief verification step after setup (e.g. confirm the stream URL plays or that discover.py lists cameras) to introduce a validation checkpoint into the workflow.

Dimension	Reasoning	Score
Conciseness	The body is lean — a one-line purpose statement and a minimal setup snippet with no padding or explanation of concepts Claude already knows, matching the anchor for lean, efficient content where every token earns its place. Not 2 because there is no unnecessary explanation to tighten.	3 / 3
Actionability	Provides one concrete setup command but it references a missing requirements.txt, and the capability scripts (discover.py, stream.py) referenced in frontmatter do not exist while the body gives no usage example (no RTSP URL format or clip-capture invocation). Matches the anchor for some concrete guidance but incomplete and missing key details; not 3 because it is not copy-paste ready and references are broken, not 1 because at least one concrete command is present.	2 / 3
Workflow Clarity	A two-step setup sequence (venv then pip) is present, but there is no workflow for the actual capabilities and no validation or verification checkpoints. Matches the anchor for a sequence present but with checkpoint gaps; not 1 because setup steps are listed, not 3 because no validation steps or feedback loops exist for the multi-capability skill.	2 / 3
Progressive Disclosure	The body is short and section-organized (intro, setup) and references capability scripts, but only scripts/feed.py actually exists — discover.py, stream.py, and requirements.txt are referenced yet absent, so navigation does not resolve. Matches the anchor for structure present but references not cleanly signaled/resolved; not 3 because referenced paths are broken, not 1 because it is not a monolithic wall of text or deeply nested.	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 clearly names its niche and two concrete capabilities and is highly distinct, but it lacks any "Use when..." trigger clause and offers no synonym variation, which caps completeness and trigger-term quality. Adding an explicit use-when clause and a couple of natural synonyms would lift both dimensions.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user wants to view Eufy camera feeds, pull event clips, or stream Eufy cameras via RTSP."

Include common term variations a user might say ("live view", "video", "footage", "Eufy HomeBase") to broaden trigger-term coverage.

Optionally enumerate the three capabilities (discover, live stream, clip feed) for more comprehensive specificity.

Dimension	Reasoning	Score
Specificity	Names the domain ("Eufy camera integration") and two concrete capabilities ("local RTSP streaming and event clips"), matching the anchor for naming a domain with some but not comprehensive actions. Not 3 because only two actions are listed and they are terse rather than a comprehensive enumeration; not 1 because concrete actions are explicitly stated.	2 / 3
Completeness	States what the skill does ("local RTSP streaming and event clips") but provides no "Use when..." or equivalent trigger guidance, so the "when" is missing entirely. Per the rubric, a missing explicit trigger clause caps completeness at 2; not 1 because the "what" is clearly stated.	2 / 3
Trigger Term Quality	Includes relevant natural terms ("Eufy", "camera", "RTSP", "streaming", "event clips") but offers single phrasings per concept with no common variations (e.g. "live view", "video", "footage", ".rtsp"), matching the anchor for some relevant keywords missing common variations. Not 3 because variation coverage is thin; not 1 because the terms are natural and on-point rather than jargon.	2 / 3
Distinctiveness Conflict Risk	"Eufy camera integration" is a narrow vendor-and-device niche with distinct triggers, making it unlikely to fire for an unrelated skill. Not 2 because the specificity is high rather than merely "somewhat specific"; not applicable below.	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/eufy/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.