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 ./openclaw/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', 'security camera', or 'video stream', and could benefit from listing more specific capabilities.
Suggestions
Add a 'Use when...' clause with explicit triggers, e.g., 'Use when the user wants to capture snapshots or video clips from IP cameras, security cameras, RTSP streams, or ONVIF devices.'
Include common user-facing synonyms and variations such as 'IP camera', 'security camera', 'video stream', 'snapshot', 'recording', 'surveillance camera'.
Expand the capability list with more specific actions, e.g., 'save frames as images, record video clips, configure stream parameters, discover ONVIF devices'.
| 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 since the 'what' is also thin, this falls to 1. | 1 / 3 |
Trigger Term Quality | Includes relevant technical keywords like 'RTSP', 'ONVIF', 'frames', 'clips', and 'cameras', but misses common user variations like 'IP camera', 'security camera', 'video stream', 'snapshot', 'recording', 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 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.
This is a well-crafted, concise skill that provides clear CLI commands for camera capture operations. Its main weakness is the lack of an explicit workflow sequence with validation steps—particularly important since camera connections can fail and captures can produce corrupt output. The content is otherwise efficient and actionable.
Suggestions
Add a brief sequenced workflow showing the recommended order: discover → add → doctor (verify connectivity) → test snap → longer operations, with explicit validation checkpoints (e.g., check file size/existence after snap).
Include a brief error recovery note, e.g., what to do if `camsnap doctor --probe` fails or if a snapshot returns an empty file.
| 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 Claude wouldn't already know. | 3 / 3 |
Actionability | Provides specific, copy-paste ready CLI commands for every operation (discover, snap, clip, watch, doctor) with concrete flags and arguments. The setup instructions include exact config path and add command. | 3 / 3 |
Workflow Clarity | The commands are listed but there's no explicit sequenced workflow (e.g., discover → add → test snap → clip). The note about preferring a short test capture hints at validation but doesn't formalize it as a checkpoint. For camera operations that could fail silently, a clearer sequence with validation would be beneficial. | 2 / 3 |
Progressive Disclosure | For a simple, single-purpose CLI skill under 50 lines with no bundle files, the content is well-organized into logical sections (setup, commands, notes) and appropriately concise without needing external references. | 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
- trpc-group/trpc-agent-go
- Commit
9f4b734
- 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.