CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

media-ops-skill

处理本地已有的图片 / 视频 / 音频文件,或下载网络视频。图片:缩放、裁剪、旋转、格式转换(→webp/png/jpeg)、滤镜、查看尺寸;视频:格式转换、提取音频、查看元信息;下载:YouTube / B 站等公开视频。也用于 AI 生成图片后的二次处理(转格式、缩放)。**不用于**:AI 从零生成图片/视频/语音(→cloud-media-skill)、在对话里渲染图表(→visualization-ops-skill)。

60

Quality

76%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Critical

Do not install without reviewing

Fix and improve this skill with Tessl

tessl review fix ./apps/server/src/ai/builtin-skills/media-ops/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

68%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.

A well-structured, actionable body that makes the three deferred tools immediately usable, with a good decision tree and concrete call examples. The main gaps are validation: the batch conversion workflow lacks verification steps and there is no explicit validate→fix→retry feedback loop, and the single ~110-line file could offload per-tool parameter detail to one-level-deep reference files.

Suggestions

Add a verification checkpoint to the batch workflow (e.g. run `get-info` on the first converted file to confirm format/size before continuing, and check each output file exists).

Convert the 常见错误 section into an explicit feedback loop: on failure, run `get-info` to diagnose, adjust parameters/paths, and retry — rather than only describing the likely causes.

Split per-tool action/parameter tables into one-level-deep reference files (e.g. references/imageprocess.md) and keep SKILL.md as the overview + decision tree.

DimensionReasoningScore

Conciseness

The body is dense and operational: action tables with key parameters, a decision tree, and terse call examples in the workflows — every section carries guidance specific to these custom tools rather than general knowledge. It is not a 5 because there is mild redundancy (the "⚡ 读到此处立刻行动" callout repeats the "加载" ToolSearch note) and a few rationale sentences (e.g. "WebP ... 文件体积约为 JPEG 的 70%") could be trimmed.

4 / 5

Actionability

Concrete and executable throughout: each tool's actions are tabulated with exact parameter names (`resize` → `width`/`height`/`fit`, `extract-audio` → `audioFormat`), and workflows show full call shapes like `ImageProcess(action: "convert", filePath: "…", format: "webp", outputPath: "…")`. Minor gaps (e.g. `CloudImageGenerate` appears without any introduction, and some filter parameters are only gestured at as "各有专属参数") keep it below the copy-paste-ready-with-full-coverage bar of 5.

4 / 5

Workflow Clarity

Sequences are clear (decision tree, get-info-first checkpoint, three concrete workflows), but the guideline cap applies: the 批量图片格式转换 batch workflow has no validation/verification step (no get-info or output check per file, no failure-recovery loop), and the error section describes likely errors without an explicit verify-then-retry feedback loop. This sits at the anchor 'steps listed but validation gaps; checkpoints missing or implicit' rather than the 4 anchor with 'most checkpoints present'.

3 / 5

Progressive Disclosure

There is no bundle (references/, scripts/, assets/ all absent) and the single SKILL.md is well organized — headers, a tool inventory table, a decision tree, and per-tool sections make navigation easy. Since the body exceeds the ~50-line threshold at which a single self-contained file can score 5 (it is ~110 lines), and per-tool parameter detail could plausibly live in one-level-deep reference files, it fits the 4 anchor: good structure, appropriately placed content, minor organization gaps.

4 / 5

Total

15

/

20

Passed

Description

75%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.

A strong, highly specific description with excellent distinctiveness (explicit negative-trigger redirects to sibling skills). Its main weakness is the absence of an explicit 'Use when...' trigger clause, which leaves the 'when' half only partially addressed, and the lack of file-extension/synonym trigger terms.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user mentions 缩放/裁剪/转格式/提取音频/下载视频 or image/video/audio file paths (.jpg/.png/.mp4/.webm)".

Include common file extensions and synonyms (压缩、转码、格式转换 for media) as trigger terms to round out keyword coverage.

Move the 也用于 AI 生成图片后的二次处理 case into the trigger clause so the 'when' guidance is consolidated and explicit.

DimensionReasoningScore

Specificity

The description enumerates concrete per-domain actions: "图片:缩放、裁剪、旋转、格式转换(→webp/png/jpeg)、滤镜、查看尺寸;视频:格式转换、提取音频、查看元信息;下载:YouTube / B 站等公开视频" — multiple specific actions with named target formats, comprehensive across all three tools. This matches the anchor for listing multiple specific concrete actions with comprehensive coverage; the only soft spot (filter types left generic as "滤镜") is not enough to drop a level.

5 / 5

Completeness

The 'what' is clear and detailed, but there is no general explicit 'Use when...' trigger clause; 'when' guidance is only weakly implied by the opening "处理本地已有的..." plus partial special-case triggers ("也用于 AI 生成图片后的二次处理", "不用于..."). Per the judging guideline, a missing 'Use when...' clause or equivalent explicit trigger guidance caps completeness at 3 — this is not the 4 anchor, where an explicit 'when' exists even if imperfect.

3 / 5

Trigger Term Quality

Natural user terms are well covered: "缩放、裁剪、旋转、格式转换、滤镜、提取音频、下载、YouTube / B 站". However common synonyms and file extensions users actually say (如 .jpg/.png/.mp4/"压缩"/"转码") are absent, which keeps it at 'good keyword coverage; a few natural terms missing' rather than comprehensive.

4 / 5

Distinctiveness Conflict Risk

It carves a clear niche (processing existing local media vs. downloading) and explicitly redirects the two adjacent skills with negative triggers: "**不用于**:AI 从零生成图片/视频/语音(→cloud-media-skill)、在对话里渲染图表(→visualization-ops-skill)". This is a clear niche with distinct triggers and minimal conflict risk; without those explicit redirects it would risk the 4 anchor's 'minor overlap with closely related skills'.

5 / 5

Total

17

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

itsablabla/openloaf-web

Path

apps/server/src/ai/builtin-skills/media-ops/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.