Capture frames or clips from RTSP/ONVIF cameras.
74
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillEvaluation — 100%
↑ 4.00xAgent success when using this skill
Validation for skill structure
Discovery
40%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 identifies a clear technical niche (RTSP/ONVIF cameras) which provides good distinctiveness, but it's too terse overall. It lacks explicit trigger guidance ('Use when...') and misses common user-friendly terms that would help Claude match this skill to natural user requests about IP cameras or video streams.
Suggestions
Add a 'Use when...' clause specifying trigger scenarios, e.g., 'Use when the user wants to capture video or images from IP cameras, security cameras, or video streams.'
Include common user-friendly synonyms alongside technical terms: 'IP camera', 'security camera', 'video stream', 'network camera', 'surveillance'.
Expand the capability list to include more specific actions like 'save snapshots', 'record video segments', or 'connect to camera streams'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (RTSP/ONVIF cameras) and two actions (capture frames, capture clips), but lacks comprehensive detail about what else the skill can do or specific capabilities like resolution settings, scheduling, or output formats. | 2 / 3 |
Completeness | Describes what the skill does but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. Per rubric guidelines, missing explicit trigger guidance caps this at 2, but the 'what' is also minimal, warranting a 1. | 1 / 3 |
Trigger Term Quality | Includes technical terms 'RTSP' and 'ONVIF' that knowledgeable users would use, plus 'frames' and 'clips', but misses common variations like 'IP camera', 'security camera', 'video stream', 'screenshot', or 'record'. | 2 / 3 |
Distinctiveness Conflict Risk | RTSP/ONVIF cameras is a very specific niche that is unlikely to conflict with other skills. The protocol-specific terminology creates clear boundaries for when this skill applies. | 3 / 3 |
Total | 8 / 12 Passed |
Implementation
87%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-crafted, concise skill that provides actionable CLI commands without unnecessary explanation. The main weakness is the lack of explicit validation/verification steps - for camera operations that may fail due to network issues or misconfiguration, a clearer workflow with checkpoints (e.g., verify connection before capturing) would improve reliability.
Suggestions
Add a brief workflow showing how to verify camera connectivity before capturing (e.g., 'First run `camsnap doctor --probe` to verify connection, then proceed with snap/clip commands')
Include what success/failure output looks like for key commands to help Claude verify operations completed correctly
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely lean and efficient. No unnecessary explanations of what RTSP/ONVIF cameras are or how ffmpeg works. Every line provides actionable information. | 3 / 3 |
Actionability | Provides concrete, copy-paste ready commands for all common operations: adding cameras, discovery, snapshots, clips, and motion watching. Includes specific flags and example values. | 3 / 3 |
Workflow Clarity | Commands are listed but there's no explicit workflow sequence. The 'prefer a short test capture before longer clips' hint suggests validation but doesn't provide a clear checkpoint process. For camera operations that could fail silently, explicit validation steps would help. | 2 / 3 |
Progressive Disclosure | For a simple CLI tool skill under 50 lines, this is appropriately organized with clear sections (Setup, Common commands, Notes). No need for external references given the scope. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
72%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 8 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata.version' is missing | Warning |
metadata_field | 'metadata' should map string keys to string values | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 8 / 11 Passed | |
Table of Contents
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.