camsnap
Capture frames or clips from RTSP/ONVIF cameras.
72
59%
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 and misses common user-facing trigger terms like 'IP camera', 'security camera', or 'video stream' that would help Claude match it to user requests.
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', 'surveillance', 'video stream', 'snapshot', and 'network camera' to improve matching.
Expand the capability list with more specific actions, e.g., 'connect to camera streams, capture still frames, record video clips, configure camera settings via RTSP/ONVIF protocols.'
| 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 configuration, streaming, saving formats, or other concrete operations. | 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 for when Claude should select this skill. Per rubric guidelines, missing 'Use when' caps completeness at 2, and the 'what' is also minimal, warranting a 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 'surveillance'. | 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 (RTSP, ONVIF) clearly distinguish it. | 3 / 3 |
Total | 8 / 12 Passed |
Implementation
79%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
A concise, actionable skill that efficiently covers the core camsnap CLI commands without unnecessary verbosity. Its main weakness is the lack of a clear sequential workflow with validation steps (e.g., verify camera connectivity after adding, confirm ffmpeg availability before capturing) and the absence of references to more detailed documentation for advanced features like motion watch actions.
Suggestions
Add a brief sequential workflow: 1. Verify ffmpeg (`ffmpeg -version`), 2. Add camera, 3. Test with `camsnap doctor --probe`, 4. Take a test snapshot before longer clips.
Include a validation/feedback step after adding a camera (e.g., `camsnap doctor --probe` to confirm connectivity before attempting captures).
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Very 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 specific, copy-paste ready commands for every operation: adding cameras, discovering, snapshotting, clipping, and motion watching with concrete flags and arguments. | 3 / 3 |
Workflow Clarity | The commands are listed but there's no clear sequenced workflow (e.g., setup → discover → configure → capture). The note about preferring a short test capture hints at validation but doesn't provide an explicit checkpoint or feedback loop. | 2 / 3 |
Progressive Disclosure | Content is well-organized with clear sections, but uses flat markdown headers without proper heading syntax (no ## markers). For a simple skill under 50 lines this is adequate, but the config file reference and motion watch action parameter could benefit from links to more detailed documentation. | 2 / 3 |
Total | 10 / 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.