media-processing
Media processing utilities for images, audio, and video using FFmpeg and ImageMagick. Use when working with media conversion, optimization, or batch processing tasks.
Install with Tessl CLI
npx tessl i github:siviter-xyz/dot-agent --skill media-processing64
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
75%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This description has good structure with explicit 'what' and 'when' clauses, and establishes a clear niche around media processing tools. However, it could be strengthened by listing more specific actions (resize, transcode, compress) and including common file format keywords users would naturally mention.
Suggestions
Add specific concrete actions like 'resize images, convert video formats, extract audio, create thumbnails, compress media files'
Include common file format trigger terms users would say: 'mp4, mp3, jpg, png, gif, wav, webm, .mov'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (media processing) and mentions tools (FFmpeg, ImageMagick), but actions are generic ('conversion, optimization, batch processing') rather than listing specific concrete actions like 'resize images, convert video formats, extract audio tracks'. | 2 / 3 |
Completeness | Clearly answers both what ('Media processing utilities for images, audio, and video using FFmpeg and ImageMagick') and when ('Use when working with media conversion, optimization, or batch processing tasks') with an explicit 'Use when' clause. | 3 / 3 |
Trigger Term Quality | Includes some relevant keywords ('images, audio, video, media conversion, optimization, batch processing') but misses common variations users might say like 'resize', 'compress', 'transcode', 'thumbnail', 'mp4', 'jpg', 'wav', or file extensions. | 2 / 3 |
Distinctiveness Conflict Risk | Clear niche focused on media processing with specific tool mentions (FFmpeg, ImageMagick). The combination of media types and processing tools creates a distinct trigger profile unlikely to conflict with document or code-focused skills. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
42%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides good organizational structure and appropriate progressive disclosure to reference materials, but critically lacks actionable content. It describes capabilities and scripts without showing how to actually use them - no command examples, no code snippets, no concrete invocations. The content reads more like documentation overview than executable guidance.
Suggestions
Add concrete command-line examples for each script showing actual invocations, e.g., `python scripts/batch_resize.py ./images --strategy thumbnail --size 150x150 --output ./thumbs/`
Include at least one complete workflow example showing a real task from input to validated output, such as converting a video for web with quality verification
Remove or condense the 'When to Use' and 'Key Principles' sections - Claude understands these concepts; replace with executable quick-start examples
Add expected output examples or validation commands to verify successful processing (e.g., checking file sizes, running ffprobe on output)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is reasonably efficient but includes some unnecessary sections like 'When to Use' and 'Key Principles' that explain concepts Claude already understands. The capabilities section describes what the scripts do rather than showing how to use them. | 2 / 3 |
Actionability | No executable code examples or concrete commands are provided. The skill describes scripts and their capabilities but never shows actual usage syntax, command-line invocations, or expected outputs. Users must infer how to run the scripts. | 1 / 3 |
Workflow Clarity | Usage guidelines provide a reasonable sequence (check dependencies → dry-run → keep originals → document), but lacks explicit validation checkpoints or error recovery steps. No concrete workflow showing a complete task from start to finish. | 2 / 3 |
Progressive Disclosure | Well-structured with clear sections and appropriate references to external files (scripts/, references/). Navigation is clear with one-level-deep references to specific documentation files for deeper topics. | 3 / 3 |
Total | 8 / 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.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- 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.