CtrlK
BlogDocsLog inGet started
Tessl Logo

ppt-roadshow-generator

PPT 路演视频全流程生成器,支持品牌风格学习、智能配音、音效音乐、字幕和一键视频合成。可一次性生成 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

65%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 content is well-structured with strong progressive disclosure and largely executable script guidance, but conciseness slips from duplication and the batch workflow lacks the validation checkpoints the rubric demands. Adding explicit verification loops would most improve the score.

Suggestions

Insert explicit validation checkpoints between roles and a verify-output step before final video composition (e.g. validate brand_style.json, verify audio/subtitle timing, confirm video plays) to lift workflow_clarity above the batch cap of 3.

De-duplicate the dependency block — keep it only in frontmatter or 前置准备, not both — to improve conciseness.

Make the TTS and image-generation steps concrete (named API/tool and expected output) to close the actionability gap toward 5.

DimensionReasoningScore

Conciseness

Mostly efficient role-by-role guidance, but the dependency list is duplicated verbatim between frontmatter and 前置准备, and 可选分支 repeats role coverage, adding unnecessary tokens; fits 3 over 4 due to these padded sections.

3 / 5

Actionability

Provides copy-paste-ready invocations for audio_processor.py, subtitle_generator.py, and roadshow_composer.py with full arguments and named outputs; minor gaps (TTS call and image generation stay abstract) keep it at 4 rather than 5.

4 / 5

Workflow Clarity

A clear ten-role sequence exists, but this is a batch operation (15–100 pages) with only one weak validation mention (验证配置完整性) and no systematic validate-and-retry feedback loops, so the batch-operation cap holds it at 3.

3 / 5

Progressive Disclosure

The body is an overview with a 资源索引 that links one-level-deep to references/, scripts/, and assets/ with per-link purpose annotations, and all referenced files verified to exist, matching the score-5 anchor for clear navigation.

5 / 5

Total

15

/

20

Passed

Description

71%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 specific and reasonably trigger-rich but lacks an explicit 'when to use' clause, which caps its completeness. Overall a solid, mostly-distinct description that would benefit from explicit activation guidance.

Suggestions

Add an explicit trigger clause such as 'Use when the user needs a roadshow video, product-launch demo, or company-intro video' to lift completeness above 3.

Include natural synonyms and file extensions (演示文稿, .pptx, 路演 PPT) to broaden trigger-term coverage toward 5.

Tighten the second sentence or fold it into the trigger clause to avoid slight redundancy with the capability list.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — '品牌风格学习、智能配音、音效音乐、字幕和一键视频合成' — giving comprehensive coverage of the pipeline, matching the score-5 anchor; no significant gaps warrant a 4.

5 / 5

Completeness

It clearly states what the skill does but contains no 'Use when…' / '当用户需要…' trigger clause, so per the judging guideline the missing explicit trigger guidance caps completeness at 3 rather than 4.

3 / 5

Trigger Term Quality

Includes natural terms a user would say ('PPT', '路演视频', '配音', '字幕', '视频合成') but misses common synonyms and file extensions (e.g. 演示文稿, .pptx), so good-but-not-comprehensive coverage fits 4 rather than 5.

4 / 5

Distinctiveness Conflict Risk

The '路演视频' niche is distinct and unlikely to trigger for the wrong skill, with only minor overlap risk against related PPT skills the body itself names as collaborators, fitting 4 over 5.

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.

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.