CtrlK
BlogDocsLog inGet started
Tessl Logo

product-video-creator

多智能体协同的商品视频创作流水线,支持从商品信息到成视频的全流程创作:文案生成、故事策划、脚本创作、分镜设计、图片生成、字幕创作、音效推荐及视频合成;适用于电商商品宣传、品牌推广、社交媒体营销等场景

55

Quality

62%

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 ./skills/product-video-creator/product-video-creator/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

57%

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

The body is a well-structured, progressively-disclosed 8-step pipeline with clear sequencing and a real script invocation, but it lacks a validation feedback loop before the final batch video synthesis and most steps rely on instruction-style guidance rather than copy-paste code.

Suggestions

Add an explicit validate→fix→retry checkpoint before final video synthesis (e.g. verify subtitles.json and image sequence completeness, then re-run composer on failure) to satisfy the workflow-clarity feedback-loop requirement.

Provide concrete, copy-paste-ready invocations or code for the image-generation and asset-preparation steps rather than only describing them.

De-duplicate the capability list repeated across 任务目标, 前置准备, and step headings to tighten the body toward the level-3 conciseness anchor.

DimensionReasoningScore

Conciseness

The per-step 贌责/执行要点/输出 structure is mostly efficient and avoids explaining concepts Claude already knows, but the ~200-line body repeats the capability list across 任务目标, 前置准备, and the step headings and could be tightened, so it sits at level 2 rather than the lean level-3 anchor.

2 / 3

Actionability

Step 8 provides a concrete, executable bash invocation and steps give specific parameters (分辨率至少1920x1080, scene_001.jpg, 每行不超过20字), but most steps are instruction-only without copy-paste-ready code (e.g. image generation and script calls are described rather than given), matching the 'some concrete guidance but incomplete' anchor.

2 / 3

Workflow Clarity

Eight steps are clearly sequenced with outputs feeding the next step, but the final video synthesis is a batch operation with no validate→fix→retry checkpoint (质量验证 only happens after synthesis), which per the guidelines caps workflow clarity at 2.

2 / 3

Progressive Disclosure

A 资源索引 section signals one-level-deep references (storyboard_format.md, subtitle_format.md, video_specs.md, video_composer.py), all of which exist as real bundle files, and the body appropriately overviews while delegating detail to references, matching the level-3 anchor.

3 / 3

Total

9

/

12

Passed

Description

67%

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 highly specific about capabilities and occupies a distinct niche, but it lacks an explicit 'Use when...' trigger clause and relies on scenario categories instead of natural user keywords, capping completeness and trigger-term quality.

Suggestions

Add an explicit 'Use when...' clause listing natural trigger phrases users would say, e.g. 'Use when creating product promotional videos, ad clips, or social-media marketing videos for e-commerce goods'.

Surface concrete trigger keywords (商品视频, 宣传片, 广告视频, 短视频, 分镜) rather than only broad scenario categories.

Keep the existing action list but pair it with the trigger clause so both 'what' and 'when' are explicit.

DimensionReasoningScore

Specificity

Lists eight concrete production actions (文案生成、故事策划、脚本创作、分镜设计、图片生成、字幕创作、音效推荐及视频合成), matching the 'multiple specific concrete actions' anchor rather than the partial level-2 example.

3 / 3

Completeness

Clearly answers 'what' with the full pipeline, but 'when' is only implied via '适用于…场景' with no explicit trigger guidance, which per the guidelines caps completeness at 2.

2 / 3

Trigger Term Quality

Provides scenario categories (电商商品宣传、品牌推广、社交媒体营销) rather than natural trigger phrasings a user would say, and lacks a 'Use when...' clause with common keyword variations, so it does not reach level-3 coverage.

2 / 3

Distinctiveness Conflict Risk

The multi-agent product-video-creation pipeline is a clear niche with distinct triggers unlikely to conflict with other skills, matching the level-3 anchor.

3 / 3

Total

10

/

12

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.

Validation15 / 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
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.