CtrlK
BlogDocsLog inGet started
Tessl Logo

ffmpeg-encoder-check-4855c0

Check available FFmpeg encoders before writing encoding scripts to avoid library version mismatches

61

Quality

71%

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

85%

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

The body is highly actionable with executable commands and a clear, validated workflow, and it is well-organized for a self-contained skill; its only weakness is repetition of the libopenh264 and stream-copy guidance.

Suggestions

Consolidate the libopenh264 warning so it appears once (e.g., in Pitfalls) rather than in Purpose, Step 2, and Pitfalls.

Merge the stream-copy guidance so it is stated once rather than in both the Step 2 priority list and the 'When to Use Stream Copy' section.

DimensionReasoningScore

Conciseness

The body is lean and avoids explaining basic concepts, but the libopenh264 warning recurs in Purpose, Step 2, and Pitfalls and stream-copy guidance is repeated, so it could be tightened.

2 / 3

Actionability

Provides fully executable commands ('ffmpeg -encoders | grep h264', a short test encode) and a copy-paste-ready bash decision script, matching the anchor-3 example.

3 / 3

Workflow Clarity

A clear three-step sequence includes an explicit 'Verify Before Execution' checkpoint and a branching fallback (libx264 -> h264 -> copy), satisfying the clear-sequence-with-validation anchor.

3 / 3

Progressive Disclosure

This self-contained, single-purpose skill is well-organized into clearly labeled sections with no need for external references (none are bundled), which scores 3 per the simple-skills scoring note.

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 concrete and well-scoped to a clear FFmpeg niche, but it relies on a single action and lacks an explicit 'Use when...' trigger clause, which caps completeness and trigger-term coverage.

Suggestions

Add an explicit trigger clause such as 'Use when writing FFmpeg encoding scripts or when the user asks to encode video with FFmpeg'.

Broaden trigger terms to include natural variations like 'video encoding', 'transcoding', 'codec', or 'H.264'.

Consider listing one or two more concrete actions (e.g., 'probe encoders, select a compatible codec, and verify with a test encode') to lift specificity to anchor 3.

DimensionReasoningScore

Specificity

Names a single concrete action ('Check available FFmpeg encoders') with a clear purpose ('to avoid library version mismatches'), but does not list multiple specific actions as the anchor-3 example does.

2 / 3

Completeness

Clearly states what the skill does and gives a temporal 'when' ('before writing encoding scripts'), but lacks an explicit 'Use when...' trigger clause, so completeness is capped at 2 per the judging guidelines.

2 / 3

Trigger Term Quality

Includes relevant natural terms ('FFmpeg encoders', 'encoding scripts') but omits common variations a user might say (codec, transcode, H.264, video encoding), matching the 'some relevant keywords but missing common variations' anchor.

2 / 3

Distinctiveness Conflict Risk

Occupies a clear niche (FFmpeg encoder availability probing) with distinct, specific triggers, making it unlikely to fire for unrelated skills.

3 / 3

Total

9

/

12

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.