CtrlK
BlogDocsLog inGet started
Tessl Logo

ffmpeg-encoder-check

Check FFmpeg encoder availability before video encoding to avoid library mismatches

56

Quality

64%

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 ./benchmarks/gdpval/skills/ffmpeg-encoder-check/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

67%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 content is actionable and well-structured with a clear workflow and validation step for batch encoding, but it is held back by redundancy between its Best Practices and Common Errors sections and a template with undefined variables.

Suggestions

Merge "Common Errors to Avoid" into "Best Practices" (or vice versa) to remove the duplicated libx264/copy guidance and tighten token use.

Make the example script self-contained by setting INPUT/OUTPUT and detecting SOURCE_RESOLUTION/TARGET_RESOLUTION, or explicitly mark the placeholders and show how to populate them.

Add a short fix→retry feedback loop for the batch-validation step (e.g., on sample-test failure, report the encoder error and re-probe before proceeding) to push workflow clarity higher.

DimensionReasoningScore

Conciseness

The body is mostly efficient with concrete commands, but the "Common Errors to Avoid" section substantially duplicates "Best Practices" (e.g., prefer libx264, use -c:v copy for matching resolution), so it could be tightened.

3 / 5

Actionability

Provides concrete, executable ffmpeg commands and a full bash template covering common cases, but the template references undefined variables ($SOURCE_RESOLUTION, $TARGET_RESOLUTION, $INPUT, $OUTPUT), leaving minor gaps.

4 / 5

Workflow Clarity

A clear four-step sequence is present with an explicit validation checkpoint (Step 4 "Validate Before Batch Processing") and fail-fast error handling in the script, but there is no fix→retry feedback loop, so it sits below 5.

4 / 5

Progressive Disclosure

No bundle files exist; the ~100-line body is well-organized into clearly labeled sections with no need for external references, though minor redundancy between sections keeps it just below a 5.

4 / 5

Total

15

/

20

Passed

Description

61%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 clearly states what the skill does and targets a distinct niche, but it omits an explicit 'Use when…' trigger clause, which caps completeness and limits trigger-term quality.

Suggestions

Add an explicit 'Use when…' clause naming concrete trigger phrases (e.g., 'Use when writing video encoding scripts, transcoding footage, or before running batch FFmpeg jobs').

Broaden the action list slightly to improve specificity (e.g., 'probe encoders, interpret results, and choose an encoding strategy').

Include common synonyms/file cues users might say (e.g., 'transcode', 'H.264', 'libx264', 'libopenh264') to raise trigger-term coverage.

DimensionReasoningScore

Specificity

Names the domain and a concrete action ("Check FFmpeg encoder availability") but lists only one core action with no broader coverage, matching the 1-2 concrete actions anchor.

3 / 5

Completeness

The "what" is clear (check encoder availability before encoding) but there is no explicit "Use when…" trigger clause; per the rubric a missing trigger clause caps completeness at 3, and "when" is only weakly implied by "before video encoding".

3 / 5

Trigger Term Quality

Includes natural terms a user would say ("FFmpeg", "video encoding", "encoder", "library mismatches") with good coverage, though a few common variations are missing.

4 / 5

Distinctiveness Conflict Risk

It targets a clear niche (FFmpeg H.264 encoder probing) that is mostly distinct, with only minor overlap risk against a more general FFmpeg/video skill.

4 / 5

Total

14

/

20

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
HKUDS/OpenSpace
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.