CtrlK
BlogDocsLog inGet started
Tessl Logo

three-body-video-creator

影片与视频编辑和内容创作者必备!当需要制作《三体》主题视频时,自动化完成选题策划、视觉设计、音频生成到成片合成,多智能体协作流程,3小时搞定72小时工作量。

64

Quality

76%

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

Quality

Content

73%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 body delivers a well-sequenced, validated multi-phase workflow with genuinely executable script calls that match the actual bundle scripts. Its weaknesses are redundancy — dependency lists and character/scene specs repeated inline that already live in references/assets — and a few steps (image generation, B站 packaging) that specify outputs without an executable mechanism.

Suggestions

Deduplicate the character voice/台词 specs in 步骤3 and 步骤10 — keep one line each and point to references/character-profiles.md, which already contains the full profiles.

Drop the duplicated dependency block in 前置准备 (it repeats the frontmatter dependency list verbatim) and keep only the mkdir directory-setup commands.

For 步骤8 and 步骤14, either specify the concrete mechanism (image-generation prompt workflow referencing assets/scene-examples, or a script) or explicitly state the agent-driven approach as the 注意事项 section implies.

DimensionReasoningScore

Conciseness

The body is mostly procedural and domain-specific, but contains clear tightening opportunities: the dependency list is duplicated (frontmatter and 前置准备), and the character voice/台词 profiles (罗辑:低沉平静…略带沙哑 etc.) appear nearly verbatim in both 步骤3 and 步骤10 even though they also live in references/character-profiles.md — matching anchor 3 ('mostly efficient but includes some unnecessary explanation or could be tightened'). It is not 4 because these duplications are recurring rather than minor.

3 / 5

Actionability

Script invocations are concrete and executable with real arguments ('scripts/voice_generator.py --input <旁白数据JSON> --output ./output/audio/voice', quality_checker example calling check_video_quality which exists at scripts/quality_checker.py:12), plus concrete mkdir setup — matching anchor 4 ('mostly executable guidance; concrete code or commands with minor gaps'). It is not 5 because 步骤8 (image generation) and 步骤14 (B站 adaptation) give direction with no executable mechanism, and some outputs ('输出: 《情绪曲线图》') are named without any how.

4 / 5

Workflow Clarity

The 15 steps are sequenced across three explicit phases with dedicated validation checkpoints (步骤12 原著合规检测, 步骤13 技术指标检测 via quality_checker.py, 步骤15 五维评审 with a pass threshold 总分≥80分) and a feedback-loop section (可选分支: re-run steps 1-3, 4-8, 11, or 13 on failure) — matching anchor 5 ('clear sequence with explicit validation steps; feedback loops for error recovery; checklists').

5 / 5

Progressive Disclosure

Structure is good: SKILL.md acts as the overview, all referenced paths (4 references/*.md, 5 scripts/*.py, 3 assets subdirectories) exist and are one level deep, and the 资源索引 annotates each reference with '何时读取' — matching anchor 4 ('good structure; most content appropriately placed; references mostly clear; minor organization gaps'). It is not 5 because detailed specs (character voices, scene descriptions, color palette) are duplicated inline in steps 3/5/6/9/10 rather than fully delegated to the bundle files that already hold them.

4 / 5

Total

16

/

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.

The description is a solid, niche-scoped trigger with concrete pipeline actions and an explicit when-clause. Its main weaknesses are marketing fluff ('必备!', '3小时搞定72小时工作量') and a single trigger phrase with no variations or synonyms.

Suggestions

Remove the marketing opener '影片与视频编辑和内容创作者必备!' and the unverifiable over-claim '3小时搞定72小时工作量' — they add tokens without aiding discovery.

Expand the trigger with variations users would naturally say, e.g., '当用户需要制作三体主题视频、三体短视频、B站三体二创或威慑纪元剧情视频时'.

Round out the 'what' with the quality-control capability documented in the body (e.g., 原著合规检测与技术指标检测) to close the coverage gap.

DimensionReasoningScore

Specificity

The description lists several concrete pipeline actions — '选题策划、视觉设计、音频生成到成片合成' (topic planning, visual design, audio generation, final composition) — matching anchor 4 ('lists several specific actions; minor gaps in coverage'). It is not a 5 because coverage omits capabilities the body documents (quality checking, B站/Platform adaptation) and the marketing opener '影片与视频编辑和内容创作者必备!' plus the over-claim '3小时搞定72小时工作量' pad rather than inform.

4 / 5

Completeness

It answers both questions: 'what' via '自动化完成选题策划、视觉设计、音频生成到成片合成' and 'when' via the explicit trigger clause '当需要制作《三体》主题视频时', matching anchor 4 ('both what and when; when could be more explicit or specific'). It is not 5 because only one trigger condition is given, whereas top-anchor examples enumerate several concrete trigger phrases; it is well above 3 since the when-clause is explicit, not weakly implied.

4 / 5

Trigger Term Quality

Natural trigger phrasing is present — '当需要制作《三体》主题视频时' (when you need to make a Three-Body-themed video) — alongside keywords like '视频编辑' and '内容创作者' that users would actually say, matching anchor 4 ('good keyword coverage; a few natural terms missing'). It is not 5 because common variations users might say (e.g., 短视频, B站, 配音, 分镜) are absent, and not 3 because the core trigger phrase is fully natural rather than generic jargon.

4 / 5

Distinctiveness Conflict Risk

The description carves out a clear niche — 《三体》(Three-Body) themed video production — with a distinct trigger ('制作《三体》主题视频'), so it is unlikely to fire for unrelated video or document skills, matching anchor 5 ('clear niche with distinct triggers; minimal conflict risk').

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