CtrlK
BlogDocsLog inGet started
Tessl Logo

historical-science-video-prod

自媒体创作者与内容创作者在制作历史科学类3分钟科普短视频时,使用此技能可一键生成包含口播文案、分镜脚本、Veo2提示词及人物规范的全流程素材包,完美适配即梦平台,让视频创作更高效。

62

Quality

73%

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/historical-science-video-prod/historical-science-video-prod/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, efficient overview with executable commands and correctly signaled one-level references that all resolve to real files. The main gaps are the absence of any validation/feedback step for the batch generation workflow and small actionability holes: an ellipsis placeholder in the main procedure and undocumented required environment variables and template assets.

Suggestions

Add a validation checkpoint after generation, e.g. '检查 output/ 下四个文件均存在且分镜数为30-35,否则检查 COZE_LLM_API_KEY 后重试', to introduce a feedback loop for the batch operation.

Complete step 2 (remove the '处理...' ellipsis) and document the required environment variables COZE_LLM_BASE_URL and COZE_LLM_API_KEY in 前置准备, since the script fails without them.

Reference assets/output-templates/ (script-template.txt, storyboard-template.md, veo2-prompts-template.txt) in the 资源索引 so the whole bundle is discoverable.

DimensionReasoningScore

Conciseness

The body is lean and non-tutorialial, with no explanation of concepts Claude already knows. Minor over-explanation remains: the 任务目标 section restates the frontmatter, the 使用示例 uses a bureaucratic 功能说明/执行方式/关键参数 scaffold, and step 2 trails off with a vague "处理...". It is not 5 because these sections could be tightened, but well above 3 since there is no conceptual padding.

4 / 5

Actionability

The body provides a copy-paste-ready bash command with fully specified arguments and a worked example ("python scripts/generate_video_materials.py --theme ... --output_dir ./output") plus an enumerated list of output files. It is not 5 because step 2 contains an ellipsis placeholder ("调用 ... 处理...") and the required environment variables (COZE_LLM_BASE_URL / COZE_LLM_API_KEY) that the script depends on are never mentioned.

4 / 5

Workflow Clarity

The sequence (prepare inputs → run script → view outputs) is clearly listed, but there are no validation checkpoints for a batch operation that generates four output files; the 注意事项 items are advisories rather than verify/fix/retry loops. This matches anchor 3 ('steps listed but validation gaps') and is above 2 because the sequence and expected outputs are well defined.

3 / 5

Progressive Disclosure

The body is a genuine overview with one-level-deep references, each annotated with a 何时读取 (when to read) cue, and every referenced file exists in the bundle (references/*.md ×4 and scripts/generate_video_materials.py). It is not 5 because assets/output-templates/ (three template files) is never referenced or linked from the body, leaving part of the bundle undocumented.

4 / 5

Total

15

/

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 distinctive, domain-specific description that clearly states what it produces and when it applies, with good natural trigger terms. Its main weaknesses are marketing padding (一键生成, 完美适配, 更高效) in place of additional concrete capabilities, and a trigger clause phrased around creator personas rather than explicit invocation conditions.

Suggestions

Replace the marketing phrases (一键生成, 完美适配即梦平台, 让视频创作更高效) with concrete capability statements, e.g. the actual generation steps or output formats.

State the trigger explicitly in invocation form: '当用户需要制作历史科学类科普短视频或索要口播文案/分镜脚本/Veo2提示词时使用' rather than describing who the creators are.

Add common trigger synonyms such as 短视频制作, 视频脚本, 科普文案 to broaden natural-term coverage.

DimensionReasoningScore

Specificity

The description lists four concrete deliverables ("口播文案、分镜脚本、Veo2提示词及人物规范"), matching the 'several specific actions with minor gaps' anchor. It falls short of 5 because phrases like "一键生成" (one-click generation), "完美适配" (perfectly adapts), and "让视频创作更高效" (makes creation more efficient) are marketing fluff rather than concrete capabilities.

4 / 5

Completeness

The 'what' is explicit (generates a full material package of script, storyboard, Veo2 prompts, and character specs) and a 'when' is present ("在制作历史科学类3分钟科普短视频时"), so the missing-trigger cap of 3 does not apply. It is not 5 because the trigger is framed around creator personas rather than a crisp 'use when the user asks for X' phrase, and it is embedded in a promotional sentence rather than stated as explicit invocation guidance.

4 / 5

Trigger Term Quality

Terms like "历史科学类", "3分钟", "科普短视频", "口播文案", "分镜脚本", and "Veo2提示词" are natural phrases a creator would actually say. It is not 5 because common variations and synonyms (e.g., 短视频制作, 视频脚本, 科普文案) are missing, and it is well above 3 since coverage goes beyond one or two generic keywords.

4 / 5

Distinctiveness Conflict Risk

The niche is unmistakable — historical-science 3-minute explainer videos with Veo2 prompts and the 即梦 platform — giving it distinct triggers with minimal overlap with any other plausible skill.

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.