CtrlK
BlogDocsLog inGet started
Tessl Logo

ffmpeg-encoder-check-4855c0

Check available FFmpeg encoders before writing encoding scripts to avoid library version 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-4855c0/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

75%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 a well-structured, highly actionable single-file skill with executable commands, a complete decision-flow script, and an explicit verification checkpoint. It could be tightened slightly for conciseness and would benefit from an explicit error-recovery feedback loop in the verify step.

DimensionReasoningScore

Conciseness

Mostly efficient with no concept-padding, but includes restating lines ('This shows which H.264 encoders are available') and slightly padded 'Common Pitfalls' / 'When to Use Stream Copy' prose that could be tightened, matching anchor 3 rather than 4.

3 / 5

Actionability

Provides copy-paste ready, fully executable commands (probe command, test encode command) and a complete bash decision-flow script with working logic that covers the common encoder-selection cases, matching anchor 5.

5 / 5

Workflow Clarity

A clear three-step sequence (Probe, Choose, Verify) with an explicit validation checkpoint (short test encode before full runs), but no explicit error-recovery feedback loop, so it sits at anchor 4 rather than 5.

4 / 5

Progressive Disclosure

Single self-contained file with well-organized sections and no nested references, appropriate for this size; not 5 because the 'When to Use Stream Copy' and 'Common Pitfalls' sections overlap with the Step 2 priority list, a minor organization gap.

4 / 5

Total

16

/

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 specific and well-scoped to a genuine niche, with a clear 'what' and natural FFmpeg terminology. Its main weakness is the absence of an explicit 'Use when...' trigger clause and limited synonym coverage, which cap both completeness and trigger term quality at 3.

Suggestions

Add an explicit 'Use when...' trigger clause, e.g. 'Use when writing FFmpeg encoding scripts or when the user mentions video encoding, codecs, or transcoding.'

Broaden trigger-term coverage with natural synonyms such as 'codec', 'transcode', 'video encoding', and 'H.264' so it matches more user phrasings.

Optionally name one or two more concrete actions (e.g. 'probe encoders and pick a fallback') to lift specificity from 3 toward 4.

DimensionReasoningScore

Specificity

Names the domain (FFmpeg encoders) and one concrete action ('Check available FFmpeg encoders') tied to a purpose, but does not list several specific actions, so it matches anchor 3 rather than 4.

3 / 5

Completeness

The 'what' is clear (check available encoders before writing scripts), but 'when' is only weakly implied with no explicit 'Use when...' trigger clause, which caps completeness at 3 per the guidelines.

3 / 5

Trigger Term Quality

Includes natural terms like 'FFmpeg encoders' and 'encoding scripts' a user might say, but misses common synonyms and variations such as 'codec', 'transcode', 'video encoding', or 'H.264'.

3 / 5

Distinctiveness Conflict Risk

Targets a clear, narrow niche (FFmpeg encoder probing) with minimal conflict risk; not a 5 only because it lacks an explicit trigger phrase that would make it unambiguously distinct.

4 / 5

Total

13

/

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.