camsnap
Capture frames or clips from RTSP/ONVIF cameras.
74
63%
Does it follow best practices?
Impact
100%
4.00xAverage score across 3 eval scenarios
Risky
Do not use without reviewing
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/camsnap/SKILL.mdQuality
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 and distinctive niche (RTSP/ONVIF camera capture) but is too terse. It lacks a 'Use when...' clause, misses common user-facing trigger terms like 'IP camera' or 'security camera', and could benefit from listing more specific capabilities beyond just 'frames or clips'.
Suggestions
Add a 'Use when...' clause, e.g., 'Use when the user wants to capture snapshots or video clips from IP cameras, security cameras, or video streams.'
Include common trigger term variations such as 'IP camera', 'security camera', 'video stream', 'snapshot', 'recording', and 'surveillance'.
Expand the capability list with specifics like supported output formats, scheduling captures, or configuring camera connections.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (RTSP/ONVIF cameras) and two actions (capture frames, capture clips), but doesn't elaborate on additional capabilities like saving formats, scheduling, or configuration options. | 2 / 3 |
Completeness | Describes what the skill does (capture frames/clips from cameras) but completely lacks a 'Use when...' clause or any explicit trigger guidance, which per the rubric caps completeness at 2, and the 'what' is also fairly thin, placing this at 1. | 1 / 3 |
Trigger Term Quality | Includes relevant technical keywords like 'RTSP', 'ONVIF', 'frames', and 'clips' that users familiar with IP cameras would use, but misses common variations like 'IP camera', 'security camera', 'video stream', 'snapshot', or 'recording'. | 2 / 3 |
Distinctiveness Conflict Risk | RTSP/ONVIF camera frame/clip capture is a very specific niche that is unlikely to conflict with other skills; the protocol-specific terms clearly distinguish it. | 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.
A concise, well-structured skill that provides clear, actionable CLI commands for camera capture operations. Its main weakness is the lack of a sequenced workflow showing the typical setup-to-capture flow and explicit validation steps (e.g., verifying camera connectivity before attempting clips).
Suggestions
Add a brief sequenced workflow showing the typical first-use flow: discover → add → doctor → test snap → production use, with a validation checkpoint after 'doctor' to confirm connectivity.
Include a brief error-recovery note, e.g., what to do if 'camsnap doctor --probe' fails or if ffmpeg is not found.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Very lean and efficient. Every line provides actionable information without explaining what RTSP or ONVIF cameras are, or how ffmpeg works. No unnecessary padding. | 3 / 3 |
Actionability | Provides specific, copy-paste ready commands for every operation: adding cameras, discovering, snapshotting, clipping, and motion watching. Includes concrete flags and arguments. | 3 / 3 |
Workflow Clarity | Commands are listed but there's no clear sequenced workflow (e.g., discover → add → test → snap). The note about preferring a short test capture hints at validation but doesn't formalize it as a checkpoint. For a tool that could involve streaming/recording operations, a clearer sequence would help. | 2 / 3 |
Progressive Disclosure | For a simple, single-purpose skill under 50 lines with no bundle files, the content is well-organized into logical sections (setup, commands, notes) and is easy to scan. 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 | |
- Repository
- qsimeon/openclaw-engaging
- Commit
4467e04
- 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.