CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

product-video-creator

电商运营与内容创作者在制作商品宣传、带货及社媒营销视频时,使用此多智能体协同流水线,一键自动完成卖点文案、故事分镜、场景图片、音效字幕到MP4视频合成的全流程,高效产出专业级营销视频,大幅节省制作成本与时间。

Quality

82%

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

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.

A well-architected multi-agent workflow: fully executable synthesis command (verified against the script's real CLI), concrete quantitative specs at every step, and an exemplary progressive-disclosure layout with one-level references anchored to the steps that need them. The drag is conciseness — duplicated dependency lists, a redundant resource index, generic注意事项, and three examples that mostly restate the step list — plus the absence of an explicit validate-and-retry loop.

Suggestions

Cut the 使用示例 执行流程 lists that merely restate the 8 steps; keep only the differentiated parameters (duration, shot count, audience, style, sample copy) in a compact table, saving ~40 lines.

Drop the 前置准备 dependency block (already in frontmatter) and remove either the 资源索引 section or the inline step links, since they duplicate each other.

Add an explicit feedback loop after step 8: if validation (resolution/帧率/音画同步) fails, name the corrective action (e.g. re-run composer with adjusted --fps/--width/--height, regenerate the offending scene image) before finishing.

DimensionReasoningScore

Conciseness

The step sections are tight and directive, but there is noticeable slack: the dependency block duplicates the frontmatter verbatim, the 资源索引 section re-lists reference links already given inline at steps 3/6/8, the 注意事项 section contains generic advice like "保持智能体间协作" and "必要时调整", and the three 使用示例 each spend ~8 lines restating the 8-step pipeline. Not a 2 because nothing explains concepts Claude already knows and the core instructions carry real information; not a 4 because the examples and resource-index redundancy could be cut with no loss.

3 / 5

Actionability

Guidance is fully executable: a copy-paste bash invocation of scripts/video_composer.py whose flags (--images/--subtitles/--audio/--output/--fps/--duration) exactly match the script's actual argparse, plus concrete numeric specs throughout (titles 5-10 字, 1920x1080 minimum resolution, 8-12 shots per 30s video, ≤20 字 per subtitle line, output naming scene_001.jpg..., subtitles.json). Not a 4: nothing here is pseudocode or vague, and the examples cover the common 30s/60s/15s cases with concrete shot counts.

5 / 5

Workflow Clarity

The eight steps are clearly sequenced, each with 职责/执行要点/输出, the chain rule is explicit ("每个步骤的输出应成为下一步的输入"), and there are checkpoints: pre-flight material verification in step 8 ("确保所有素材准备就绪") and output validation ("验证视频质量:分辨率、帧率、音画同步、字幕清晰"). Not a 5 because there is no error-recovery feedback loop — nothing says what to do when a generated image, subtitle timing, or the final render fails validation — and step-level self-checks in 注意事项 are stated only vaguely ("必要时调整").

4 / 5

Progressive Disclosure

The body is a proper overview with well-signaled, one-level-deep references that all exist in the bundle: storyboard_format.md linked at step 3, subtitle_format.md at step 6, video_specs.md at step 8, and scripts/video_composer.py invoked via bash, each linked exactly where needed with '格式参考'/'何时读取' cues. Formats are appropriately split out rather than inlined, and the 资源索引 provides navigation. Not a 4: structure and signaling match the best-practice example; the only cost of the resource index is mild duplication, which is a conciseness issue, not a navigation one.

5 / 5

Total

17

/

20

Passed

Description

78%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 description that explicitly states who should use it, when, and the concrete end-to-end pipeline stages, with good natural trigger terms for the e-commerce domain. Main weaknesses are marketing-fluff padding ("一键自动", "大幅节省") and missing common trigger variations like 短视频/抖音/种草.

Suggestions

Remove the buzzword tail ("一键自动完成", "高效产出专业级营销视频,大幅节省制作成本与时间") and spend those tokens on concrete trigger phrases instead.

Add common user-side synonyms to widen triggering, e.g. "短视频", "抖音/快手", "种草视频", or '.mp4'.

Make the trigger a crisp standalone clause (e.g. "当用户需要制作商品宣传/带货/种草短视频时") so the 'when' is unmistakable at a glance.

DimensionReasoningScore

Specificity

The description lists several concrete pipeline stages — "卖点文案、故事分镜、场景图片、音效字幕到MP4视频合成" — giving a specific multi-action view of what the skill does. It is not a 5 because marketing filler ("一键自动完成", "高效产出专业级营销视频,大幅节省制作成本与时间") pads the action list with over-claims rather than capabilities.

4 / 5

Completeness

Both parts are explicitly present: the 'what' is the full pipeline (copy → storyboard → images → audio/subtitles → MP4) and the 'when' is the explicit trigger clause "电商运营与内容创作者在制作商品宣传、带货及社媒营销视频时" naming both audience and use context. It falls short of 5 because the trigger is embedded in the sentence rather than a crisp standalone 'Use when...' phrase, and the buzzword tail dilutes the explicit trigger guidance.

4 / 5

Trigger Term Quality

Natural terms e-commerce users would say are present: "商品宣传" (product promo), "带货" (live-selling), "社媒营销视频" (social-media marketing video), "营销视频", "MP4视频". It is not a 5 because common variations users actually say — "短视频", "抖音", "种草视频", English terms, or file formats like .mp4 — are missing.

4 / 5

Distinctiveness Conflict Risk

It occupies a clear niche — e-commerce product marketing video creation via a multi-agent pipeline — with distinct triggers (带货, 商品宣传, 社媒营销) that are unlikely to collide with general video-editing or generic content skills. Not below 5: no overlap risk with other common skill domains is evident.

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

anbeime/skill

Path

skills/product-video-creator/product-video-creator/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.