CtrlK
BlogDocsLog inGet started
Tessl Logo

video-frames

Extract frames or short clips from videos using ffmpeg.

60

Quality

73%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/video-frames/SKILL.md

The canonical home for this skill is video-frames in Hung-Reo/hungreo-openclaw

SKILL.md
Quality
Evals
Security

Quality

Content

92%Weight 40%Scale 1-5

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

The body is an exemplary lean skill file: executable commands up front, no fluff, and useful non-obvious notes. The only weakness is a small coverage gap between what the description promises (short clips) and what the body demonstrates (single frames only). Adding one clip-extraction example or trimming the description would close it.

DimensionReasoningScore

Conciseness

The body is ~20 lines with zero padding: a one-line purpose statement ("Extract a single frame from a video, or create quick thumbnails for inspection"), two copy-paste commands, and two genuinely non-obvious notes (jpg vs png guidance). Every token earns its place and nothing explains concepts Claude already knows.

5 / 5

Actionability

Both quick-start commands are fully executable and copy-paste ready with concrete arguments, but coverage has minor gaps: the script's --index mode and the "short clips" capability promised in the description have no example. This fits 'mostly executable guidance; concrete code or commands with minor gaps' rather than the comprehensive common-case coverage of a 5.

4 / 5

Workflow Clarity

This is a simple single-purpose skill where the single action is unambiguous: run {baseDir}/scripts/frame.sh with a video path and --out. Per the rubric's simple-skill guidance, workflow clarity scores 5; the operation is non-destructive and single-shot, so no validation checkpoint is required.

5 / 5

Progressive Disclosure

The skill is under 50 lines with no need for external references, and the body is well-organized into Quick start and Notes sections. The one referenced path, {baseDir}/scripts/frame.sh, is a real file in the bundle, and the reference is one level deep and clearly signaled in executable commands.

5 / 5

Total

19

/

20

Passed

Description

53%Weight 40%Scale 1-5

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 concise and names a concrete, distinct capability, but it omits any 'when to use' trigger guidance and lacks natural synonym/extension terms. It reads as a terse capability statement rather than a complete discovery description. Adding an explicit 'Use when...' clause with common user phrasings would raise both completeness and trigger term quality.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user wants a frame, thumbnail, screenshot, or preview image from a video, or mentions .mp4/.mov files."

Include natural synonyms and file extensions users would say ("thumbnail", "screenshot from video", "preview", ".mp4", ".mov") to improve trigger term coverage.

Either enumerate the supported capabilities (timestamped frames, frame by index, output format choice) or drop "short clips" from the description, since the bundled script only extracts single frames.

DimensionReasoningScore

Specificity

"Extract frames or short clips from videos using ffmpeg" names the domain (videos) and two concrete actions (frame extraction, short clips), matching the '1-2 concrete actions, but not comprehensive' anchor. It is not a 4 because coverage is thin — no mention of thumbnails, timestamps, frame indexes, or output formats that the bundled script actually supports.

3 / 5

Completeness

The description has a clear 'what' ("Extract frames or short clips from videos using ffmpeg") but no 'Use when...' clause or equivalent trigger guidance, which caps completeness at 3 per the judging guidelines. Not a 2 because the 'what' is concrete rather than vague.

3 / 5

Trigger Term Quality

Terms like "frames", "clips", "videos", and "ffmpeg" are relevant natural keywords, but common variations users would say — "thumbnail", "screenshot from a video", "preview", ".mp4" — are missing, matching the 'some relevant keywords but missing common variations or synonyms' anchor. It is above a 2 because the present keywords are domain-specific rather than generic.

3 / 5

Distinctiveness Conflict Risk

Video frame/clip extraction with ffmpeg is a fairly clear niche with distinct triggers, matching 'mostly distinct; minor overlap risk' — it could overlap slightly with general video-editing or media-conversion skills. Not a 5 because the description does not enumerate distinct trigger phrases that would fully separate it from adjacent video skills.

4 / 5

Total

13

/

20

Passed

Validation

81%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

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

13

/

16

Passed

Repository
Bitterbot-AI/bitterbot-desktop
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.