CtrlK
BlogDocsLog inGet started
Tessl Logo

ppt-roadshow-generator

产品经理与内容创作者在筹备产品发布或公司路演视频时,使用此技能可从文档解析到视频合成全链路自动化,一键生成15-100页带智能配音、精准字幕和转场动画的完整路演视频,将数天的制作周期缩短至几分钟。

58

Quality

68%

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/ppt-roadshow-generator/ppt-roadshow-generator/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

61%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 ten-role pipeline with genuinely executable script commands and a clean, verifiable resource index. Its weaknesses are redundancy between the workflow, collaboration, and example sections, unspecified intermediate file formats, and — most significantly for a 15-100 page batch pipeline — the complete absence of validation/verification checkpoints.

Suggestions

Add explicit validation steps between stages — e.g., verify slide image count matches the structural plan, check each script's exit status and output files exist before proceeding, and probe the final roadshow_video.mp4 (duration/resolution/audio track) — with fix-and-retry guidance.

Cut the "使用示例" section to one-line pointers or remove it; it re-describes flows already fully specified in "操作步骤" and "与其他 Skill 协同", and drop the duplicated dependency block from "前置准备".

Specify the expected formats of intermediate artifacts (roadshow_script.txt structure, brand_style.json keys, transitions.json schema) or link to the reference files that define them.

DimensionReasoningScore

Conciseness

Mostly procedural with little concept-teaching padding, but there is real redundancy: the dependency list in "前置准备" duplicates the frontmatter verbatim, the "使用示例" section re-narrates flows already specified in "操作步骤" and "与其他 Skill 协同", and the collaboration sections repeat content that the resource index points to in references/collaboration_guide.md. This is the 'could be tightened' case rather than severely padded, but it is noticeably below fully lean.

3 / 5

Actionability

The four script invocations (scripts/audio_processor.py, subtitle_generator.py, roadshow_composer.py, style_learner.py) are given as complete, copy-paste-ready bash commands with arguments, and all referenced files exist in the bundle. Minor gaps: the formats of intermediate artifacts (roadshow_script.txt, transitions.json, brand_style.json) are never specified, and agent roles like "视觉设计师" direct image generation only in the abstract.

4 / 5

Workflow Clarity

The ten-role pipeline is sequenced clearly with explicit input→output chaining ("每一步输出为下一步输入") and optional branches are enumerated, which is above the level of a rough sequence. However, this is a batch operation ("支持一次性生成 15-100 页") with no validation or verification checkpoints anywhere — no check that TTS audio was produced, that image count matches the plan, or that the composed video is well-formed — and per the rubric guideline, missing validation in batch workflows caps workflow_clarity at 3. The only checkpoint is a soft "在关键节点征求反馈" with no error-recovery loop.

3 / 5

Progressive Disclosure

Good structure: the body stays an overview, and the "资源索引" clearly signals each one-level-deep reference (references/brand_style_guide.md, design-system-import-guide.md, roadshow_script_template.md, collaboration_guide.md — all verified to exist) with stated purpose, plus scripts and assets. Minor organization gaps keep it below 5: the '与其他 Skill 协同' details are inlined where the dedicated collaboration guide should carry them, and per-section inline links (e.g., the guide link inside role three's section) are somewhat buried rather than consolidated.

4 / 5

Total

14

/

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 solid description that answers both what and when with concrete capabilities and natural trigger terms in the target domain. Weaknesses are the marketing-fluff phrases, the embedded rather than separate trigger clause, and missing common variations like 'PPT'/'演示'.

Suggestions

Split the trigger into an explicit '当用户需要制作路演视频、产品发布演示、PPT 演示视频时使用' clause at the end, mirroring the body's own trigger section.

Add natural synonyms users would say — 'PPT', '演示文稿', 'pitch 视频' — to broaden trigger coverage.

Remove over-claims like '一键生成' and '将数天的制作周期缩短至几分钟' which are unverifiable marketing language rather than capability statements.

DimensionReasoningScore

Specificity

The description lists several concrete capabilities — "从文档解析到视频合成全链路自动化" (document parsing through video composition), "智能配音、精准字幕和转场动画" (smart voiceover, precise subtitles, transition animations) — but stops short of comprehensive coverage and mixes in marketing fluff like "一键生成" (one-click) and "将数天的制作周期缩短至几分钟" (shrinks days of work to minutes).

4 / 5

Completeness

Both 'what' (full-pipeline automated roadshow-video generation with voiceover, subtitles, and transitions, 15-100 pages) and 'when' ("在筹备产品发布或公司路演视频时,使用此技能" — when preparing product launches or roadshow videos) are answered explicitly, so the missing-trigger cap at 3 does not apply. The 'when' clause is embedded mid-sentence rather than a clean 'Use when...' statement, and could be more specific.

4 / 5

Trigger Term Quality

Natural trigger terms are present: "产品发布" (product launch), "公司路演视频" (company roadshow video), "配音" (voiceover), "字幕" (subtitles), "转场动画" (transitions). A few common variations users would say are missing, notably "PPT", "演示文稿" (presentation/deck), and file-format terms, which the skill itself is named around.

4 / 5

Distinctiveness Conflict Risk

Roadshow video generation with voiceover/subtitles is a distinct niche, and the description narrowly targets product managers/content creators preparing launch videos. Minor overlap risk remains with generic PPT-generation or presentation skills, which the description does not explicitly differentiate from.

4 / 5

Total

16

/

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.