CtrlK
BlogDocsLog inGet started
Tessl Logo

ppt-generator

产品经理、运营专员及综合办公文员在准备商业演示、学术汇报或培训课件时,通过七角色协作工作流,自动分析主题、推荐模板、填充内容并智能配图,一键输出高质量 PPTX 文件,将数小时的排版制作缩短至几分钟!

59

Quality

69%

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

Quality

Content

63%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 skill body has excellent progressive disclosure and a clear, well-modeled multi-role workflow with concrete commands and measurable content constraints. Its main weakness is padding: the persona/角色定位 and 核心能力 sections explain generic assistant behavior Claude already knows and add no operational value, costing token budget without improving execution.

Suggestions

Delete or compress the '角色定位' and '核心能力' persona paragraphs (e.g. 角色一's seven capability bullets, '我是一个可靠、高效、专业的助手...') — they restate generic assistant behavior Claude already knows and consume context without adding operational guidance.

Add an explicit validation/feedback loop to 角色七: check the generated .pptx opens or verify slide count against the plan, and on failure fix the JSON data and re-run generate_pptx.py before reporting success.

Include a minimal inline example of the ppt_data.json structure (metadata + one slide) so 角色七 can build the input without first opening references/ppt_structure_guide.md, and remove the '可选分支' section that duplicates the already-documented 快速模式/内容填充模式 modes.

DimensionReasoningScore

Conciseness

Noticeably verbose: each role carries a '角色定位' paragraph restating generic assistant capabilities Claude already knows — e.g. '不断学习和更新自己的知识,以适应不断变化的信息需求', '我是一个可靠、高效、专业的助手,随时为用户提供帮助' — and 角色一's seven '核心能力' bullets are pure persona filler unrelated to PPT generation. This matches the 2 anchor ('several unnecessary explanations or padded sections'); it is not a 1 because the operational steps, commands, and resource index are themselves tight and useful.

2 / 5

Actionability

Provides an executable, complete command ('python scripts/generate_pptx.py --input ./ppt_data.json --output ./presentation.pptx'), concrete quantitative constraints (titles ≤ 20 chars, 3-5 bullet points per page, 10-20 pages), and per-role deliverables. Minor gaps — no inline example of the ppt_data.json structure (delegated to the reference) — keep it at anchor 4 rather than the copy-paste-ready 5.

4 / 5

Workflow Clarity

The seven-role pipeline is clearly sequenced, and alternate modes (optimize existing PPT, quick mode, content-fill mode, single-role branches) plus user-confirmation checkpoints ('输出初步大纲供用户确认', '在关键节点(如大纲确认)征求反馈') are explicit. Not a 5 because the final build step ends with '确认文件生成成功,告知用户' without an explicit validate-on-failure/fix/retry feedback loop, and redundant '可选分支' restates modes already defined above.

4 / 5

Progressive Disclosure

The body is a genuine overview that pushes details to a well-organized bundle: a '资源索引' section lists references/ppt_structure_guide.md, references/visual_design_guide.md, scripts/generate_pptx.py, and assets/ppt_templates/ (all verified to exist), each with a '何时读取' (when to read) annotation, and the same files are linked contextually at the exact role steps that need them. References are one level deep and clearly signaled, matching the 5 anchor.

5 / 5

Total

15

/

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.

The description clearly communicates what the skill does and when it applies, with concrete action verbs and natural trigger terms for Chinese business/academic presentation scenarios. It is held back from top marks by persona-focused phrasing of the trigger context, a few missing synonyms, and light marketing-style padding ('一键', '将数小时的排版制作缩短至几分钟!').

DimensionReasoningScore

Specificity

Lists several concrete actions — '自动分析主题、推荐模板、填充内容并智能配图,一键输出高质量 PPTX 文件' — alongside target users and contexts. It falls short of the 5 anchor because the optimization/polishing capability present in the skill body is omitted, and phrases like '一键输出高质量' carry mild promotional filler; it is clearly above anchor 3 (1-2 concrete actions) with five distinct named actions.

4 / 5

Completeness

The 'what' is explicit (analyze theme, recommend template, fill content, place images, output PPTX) and a genuine 'when' clause exists — '在准备商业演示、学术汇报或培训课件时' — so both are present. The 'when' is phrased as user-persona context rather than an explicit 'Use when the user needs...' trigger, which keeps it at anchor 4 ('when' could be more explicit) rather than 5, and it is well above anchor 3 where 'when' is only weakly implied.

4 / 5

Trigger Term Quality

Good natural keyword coverage: 'PPT', 'PPTX 文件', '商业演示', '学术汇报', '培训课件', '排版制作'. A few common synonyms users would say are missing ('幻灯片', 'PowerPoint', 'slides', '美化/优化 PPT'), placing it at the 4 anchor rather than the comprehensive 5, but well above the 3 anchor's 'missing common variations'.

4 / 5

Distinctiveness Conflict Risk

A clear niche (PPT generation via a seven-role workflow) with distinctive terms like '七角色协作工作流' and '智能配图'. Minor overlap risk remains with a generic presentation/.pptx manipulation skill, matching anchor 4 ('mostly distinct; minor overlap risk with closely related skills') rather than the 5 anchor's 'minimal conflict risk'.

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.