CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

media

Create and inspect local audio and video with Python and FFmpeg.

Quality

75%

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 ./examples/v2/standard_host/skills/media/SKILL.md

The canonical home for this skill is media in ZHangZHengEric/Sage

SKILL.md
Quality
Evals
Security

Quality

Content

78%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 skill body is maximally concise and appropriately structured for a simple single-purpose skill, with an explicit pre-return validation checkpoint. Its main weakness is actionability: it states what to verify but gives no concrete commands (e.g., an ffprobe invocation) or failure-handling guidance.

Suggestions

Add one concrete verification command, e.g. `ffprobe -v error -show_entries format=duration,size -show_entries stream=width,height output.mp4`, so the 'verify dimensions, duration, and output size' directive is executable.

Add a one-line failure-handling step (e.g., 'If verification fails, regenerate with corrected parameters before returning') to close the feedback loop and raise workflow clarity.

Briefly name the creation path (e.g., a minimal ffmpeg/Python invocation or the preferred tool per task) so the 'write generated media' directive has a concrete starting point.

DimensionReasoningScore

Conciseness

The body is two lean sentences ('Write generated media inside the current sandbox workspace. Verify dimensions, duration, and output size before returning the result.') with zero padding and no explanation of concepts Claude already knows. Every token earns its place, matching the anchor-5 example of lean, competence-assuming content.

5 / 5

Actionability

There is concrete guidance — a specific write location ('inside the current sandbox workspace') and specific verification criteria ('dimensions, duration, and output size') — but no executable commands or code (e.g., no ffprobe example, no creation commands). This matches anchor 3 ('some concrete guidance but incomplete; missing key details'); it is above anchor 2 because the directives are specific rather than high-level hints, and below anchor 4 because nothing copy-paste executable is provided.

3 / 5

Workflow Clarity

The sequence (generate media -> write to workspace -> verify -> return) is clear and includes an explicit validation checkpoint ('Verify dimensions, duration, and output size before returning the result'), matching anchor 4 ('clear sequence with most checkpoints present; minor validation gaps'). It falls short of 5 because there is no feedback loop or guidance on what to do when verification fails.

4 / 5

Progressive Disclosure

This is an under-50-line simple skill with no bundle files (references/, scripts/, assets/ are absent) and no content that belongs in separate files; everything is appropriately in SKILL.md and trivially navigable. Per the rubric's simple-skills scoring note, this warrants a 5.

5 / 5

Total

17

/

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 is concise, third-person, and names a distinct domain with its tooling, but it omits any 'Use when...' trigger guidance and lacks file extensions and common verb variations. Its completeness is capped at 3 by the missing 'when' clause, which is the highest-leverage fix.

Suggestions

Add an explicit trigger clause, e.g. 'Use when creating, converting, trimming, or inspecting audio/video files (mp3, wav, mp4, mov) or when the user mentions FFmpeg.'

Enumerate a few more concrete actions (e.g., convert, trim, extract audio, read metadata) to raise specificity from two generic actions to several specific ones.

Include natural file extensions (.mp4, .mp3, .wav) and common verbs users say (convert, trim, transcode) to improve trigger-term coverage.

DimensionReasoningScore

Specificity

'Create and inspect local audio and video with Python and FFmpeg' names the domain and two actions plus tooling, matching anchor 3 ('names domain and 1-2 concrete actions, but not comprehensive'), like 'Processes PDF files and extracts content'. It is not 4 because it lacks the broader action coverage (no transcode, trim, extract-audio, or metadata inspection) that would list 'several specific actions'.

3 / 5

Completeness

The description has a clear 'what' ('Create and inspect local audio and video with Python and FFmpeg') but no 'Use when...' clause or equivalent trigger guidance, matching anchor 3 exactly; the rubric guideline explicitly caps completeness at 3 for a missing 'when' clause.

3 / 5

Trigger Term Quality

'audio', 'video', 'FFmpeg', and 'Python' are natural terms users actually say when needing this skill, giving good keyword coverage per anchor 4 ('a few natural terms missing'). It is not 5 because common variations and file extensions (.mp4, .mp3, .wav) and frequent verbs (convert, trim, transcode) are absent; it is above 3 because coverage goes well beyond a single generic keyword like 'Works with PDF files'.

4 / 5

Distinctiveness Conflict Risk

The audio/video + FFmpeg scope is a fairly distinct niche with only minor overlap risk against generic file-processing or media-editing skills, matching anchor 4 ('mostly distinct; minor overlap risk with closely related skills'). It is not 5 because without explicit trigger phrases it could still overlap with a dedicated video-editing or audio-analysis 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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

ZHangZHengEric/Sage

Path

examples/v2/standard_host/skills/media/SKILL.md

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.