go2rtc-cameras

Multi-camera RTSP to WebRTC streaming via go2rtc

Quality

75%

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/streaming/go2rtc-cameras/SKILL.md

Quality

Content

87%

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

The body is lean, concrete, and well-organized with executable protocol examples and a real capability script reference. The main gap is the absence of an explicit sequenced workflow with a verification checkpoint for batch stream registration, and a referenced requirements.txt that does not exist.

Suggestions

Add a short numbered workflow (register streams → emit live_stream events → verify go2rtc registered each via connection-info) with an explicit validation/verification checkpoint.

Provide the missing requirements.txt referenced in the Setup block, or remove the reference if the dependency list is trivial.

Optionally confirm a health/ready event (the 'ready' event is shown) should be emitted only after all streams are confirmed registered, to close the validation loop.

Dimension	Reasoning	Score
Conciseness	The ~40-line body is lean: an ASCII diagram, compact lists of supported sources, exact JSONL protocol lines, and a minimal setup block, with no explanation of concepts Claude already knows (RTSP, WebRTC, FFmpeg).	3 / 3
Actionability	It gives copy-paste-ready setup commands, concrete JSONL event examples, exact IPC event names (go2rtc:add-stream, go2rtc:connection-info), and points at the real scripts/stream.py capability — fully executable guidance.	3 / 3
Workflow Clarity	The setup sequence (venv → pip install → run capability) is discernible and the protocol is clear, but there is no explicit step-by-step sequence with a validation checkpoint for this batch stream-registration operation, which the rubric caps at 2.	2 / 3
Progressive Disclosure	This is a simple single-task skill under 50 lines with well-organized sections and a single real bundle reference (scripts/stream.py), so per the rubric's simple-skills note it earns a 3 despite referencing a missing requirements.txt.	3 / 3
	Total	11 / 12 Passed

Description

62%

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 and uses strong trigger terms, but it is an abstract topic phrase rather than a statement of concrete actions and lacks any explicit 'Use when...' trigger clause. Adding concrete verbs and an explicit usage trigger would raise specificity and completeness.

Suggestions

Lead with concrete actions, e.g. 'Registers RTSP camera streams with go2rtc for WebRTC live view in the browser' instead of the topic noun phrase.

Add an explicit trigger clause: 'Use when the user wants live camera streaming, multi-camera RTSP-to-WebRTC playback, or mentions go2rtc/WebRTC camera views.'

Keep the natural trigger terms already present (camera, RTSP, WebRTC, streaming) while folding them into the new 'Use when...' clause.

Dimension	Reasoning	Score
Specificity	The description "Multi-camera RTSP to WebRTC streaming via go2rtc" is a topic noun phrase with no concrete actions (no verbs like Registers, Configures, Streams); it names the domain precisely but states zero actions, so it does not reach the 'names domain and some actions' anchor.	1 / 3
Completeness	The 'what' is present (multi-camera RTSP-to-WebRTC streaming), but there is no 'Use when...' or equivalent explicit trigger guidance, which per the rubric caps completeness at 2.	2 / 3
Trigger Term Quality	It surfaces natural terms a camera-system user would say — "camera", "RTSP", "WebRTC", "streaming" — plus the real product name "go2rtc", giving good coverage of likely trigger phrasing.	3 / 3
Distinctiveness Conflict Risk	The multi-camera RTSP→WebRTC-via-go2rtc niche is narrow and specific, making it unlikely to trigger for or conflict with unrelated skills.	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/streaming/go2rtc-cameras/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.