ffmpeg-encoder-check

Check FFmpeg encoder availability before video encoding to avoid library mismatches

Quality

71%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

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

Quality

Content

85%

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

The content is highly actionable with executable commands, a clear validated workflow, and clean single-file organization; the only drag is minor redundancy between the Best Practices and Common Errors sections.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands, but the 'Common Errors to Avoid' section largely rephrases 'Best Practices' and the purpose/table cells add explanatory padding Claude does not need, fitting 'mostly efficient but could be tightened'.	2 / 3
Actionability	Provides fully executable commands (ffmpeg -encoders ... \| grep h264, libx264 encode lines) and a copy-paste-ready bash template, matching the 'fully executable code/commands; copy-paste ready' anchor.	3 / 3
Workflow Clarity	A clear 4-step sequence (Probe, Interpret, Choose, Validate) includes an explicit validation checkpoint ('test on a small sample file before batch processing') and a fail-fast exit-on-no-encoder loop, matching the anchor with explicit validation and feedback.	3 / 3
Progressive Disclosure	It is a single-file, well-organized skill with no nested or external references and clear sections, so it meets the simple-skill allowance for well-organized content scoring 3 on progressive disclosure.	3 / 3
	Total	11 / 12 Passed

Description

57%

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 specific and distinctive but stops short of listing multiple concrete actions and omits an explicit 'Use when...' trigger, capping specificity, trigger-term quality, and completeness at 2.

Suggestions

Add an explicit 'Use when...' trigger clause (e.g., 'Use when writing video encoding scripts or before batching H.264 encodes').

List multiple concrete actions (probe encoders, interpret results, choose codec strategy, validate on a sample) to lift specificity to 3.

Broaden trigger terms to include natural user phrasings like 'H.264', 'libx264', 'libopenh264', and 'transcode'.

Dimension	Reasoning	Score
Specificity	Names the FFmpeg-encoder domain and one concrete action ('Check FFmpeg encoder availability') but lists no further actions, matching the 'names domain and some actions, but not comprehensive' anchor.	2 / 3
Completeness	It states what the skill does and implies a when ('before video encoding'), but lacks an explicit 'Use when...' trigger clause, which per the guidelines caps completeness at 2.	2 / 3
Trigger Term Quality	Contains relevant terms ('FFmpeg encoder', 'video encoding', 'library mismatches') but omits common variations a user might say ('H.264', 'libx264', 'transcode'), so coverage is partial rather than complete.	2 / 3
Distinctiveness Conflict Risk	The FFmpeg encoder-availability niche is narrow and unlikely to trigger for unrelated skills, matching the 'clear niche with distinct triggers; unlikely to conflict' anchor.	3 / 3
	Total	9 / 12 Passed

Validation

100%

Warnings & errors only

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: HKUDS/OpenSpace
Path: benchmarks/gdpval/skills/ffmpeg-encoder-check/SKILL.md
Commit: c5a9c4b

Reviewed: 2 days ago

Table of Contents

Discovery Implementation Validation

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.