CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

pptx-generator

产品经理与运营专员在准备汇报展示时,将 JSON 数据一键转换为标准 .pptx 文件。自动应用多种布局、图表与表格样式,快速生成专业 PPT,彻底告别繁琐手工排版,让内容产出与展示更高效!

Quality

70%

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

Quality

Content

67%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 provides a well-sequenced, highly actionable JSON→PPTX workflow with genuine validation checkpoints and a properly organized one-level-deep bundle. Its main weaknesses are redundancy (duplicated collaboration diagrams and dependency lists), a broken template file reference, and the absence of error-recovery guidance when validation fails.

Suggestions

Fix the broken template reference: 'assets/templates/business_template.pptx' does not exist — either add the template or update the example to the actual 'assets/templates/ppt_data_template.json'.

Add error-recovery feedback loops after each validation step (e.g. '若 json_validator.py 报错:根据错误信息修正 JSON 字段后重新验证,通过后再构建'), which would raise workflow clarity to anchor 5.

Replace the inlined ASCII collaboration diagrams with a one-line pointer to references/collaboration_guide.md, and trim the duplicated dependency list and repetitive 使用示例 commands to reduce token cost.

DimensionReasoningScore

Conciseness

The operational sections are lean (direct commands with flags), but there is noticeable duplication: the ~50-line ASCII collaboration diagram duplicates references/collaboration_guide.md, the 前置准备 dependency list duplicates the frontmatter, and the 使用示例 section restates commands already shown in the steps. Mostly efficient with some sections that should be trimmed — fits anchor 3 better than anchor 2 since the core instruction content is tight.

3 / 5

Actionability

Nearly all guidance is fully executable: concrete bash commands with real paths for validation, building, custom styles, and batch mode, plus worked examples. The one notable gap is the template example referencing 'assets/templates/business_template.pptx', which does not exist in the bundle (the directory contains ppt_data_template.json), so that command fails if copied verbatim. Not level 5 due to this broken path; well above level 3's pseudocode/incomplete anchor.

4 / 5

Workflow Clarity

The standard flow is a clear four-step sequence (receive JSON → validate with json_validator.py → build with pptx_builder.py → validate with pptx_validator.py) with explicit validation checkpoints both before and after generation, and batch operations are also covered by the validate/build/validate pattern. It falls short of level 5 because there is no error-recovery feedback loop telling Claude what to do when a validation step fails.

4 / 5

Progressive Disclosure

SKILL.md works as an overview with a 资源索引 that lists every bundle file with its purpose, and the bundle structure is verified appropriate: three reference guides (JSON spec, layout, collaboration) and three scripts are one level deep with no nested reference chains, and styles live in assets/styles/. Minor gaps: the inlined ASCII collaboration section duplicates the separate collaboration_guide.md instead of just pointing to it, and the broken assets/templates/business_template.pptx reference keeps it below anchor 5.

4 / 5

Total

15

/

20

Passed

Description

61%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 communicates a clear, reasonably specific capability (JSON → .pptx with layouts, charts, and tables) with good natural trigger terms, but it is wrapped in marketing fluff and lacks an explicit 'use when' trigger clause, which limits its completeness and weakens its invocation guidance.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user needs to generate .pptx files, convert JSON PPT data into presentations, or export slide content to PowerPoint/幻灯片/演示文稿'.

Trim the marketing fluff ('一键', '彻底告别繁琐手工排版', '让内容产出与展示更高效!') and spend those tokens on concrete capabilities instead (e.g. validation, batch generation, custom styles/templates).

Include common synonyms users say — '幻灯片', '演示文稿', 'PowerPoint' — alongside 'PPT' and '.pptx' to improve trigger coverage.

DimensionReasoningScore

Specificity

The description names its domain clearly ('将 JSON 数据一键转换为标准 .pptx 文件') and a couple of concrete capabilities ('自动应用多种布局、图表与表格样式'), but coverage is not comprehensive and it is padded with marketing fluff ('彻底告别繁琐手工排版,让内容产出与展示更高效!') that the guidelines penalize. It sits between anchor 2 (too harsh — actions are more than minimal/generic) and anchor 4 (coverage of discrete actions is not broad enough).

3 / 5

Completeness

The 'what' is clear (JSON-to-.pptx conversion with styling), but there is no explicit 'Use when...' trigger clause; '在准备汇报展示时' describes the end-user's scenario rather than when to invoke the skill, so per the judging guidelines completeness is capped at 3. Not level 2 because the 'what' is specific, not vague.

3 / 5

Trigger Term Quality

Good keyword coverage with natural terms users would say: 'PPT', '.pptx', 'JSON', '汇报展示', '布局', '图表', '表格'. A few natural synonyms are missing ('幻灯片', '演示文稿', 'PowerPoint'), which matches anchor 4 rather than anchor 5's comprehensive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

It carves out a clear niche (JSON data → .pptx generation) with distinct triggers (JSON, .pptx, PPT), giving minimal conflict with unrelated skills; minor overlap risk remains with closely related presentation skills such as the referenced ppt-generator. Not level 5 because the trigger terms don't sharply separate it from generic presentation-creation skills.

4 / 5

Total

14

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

referenced_paths_exist

Referenced path issues: 1 missing, 3 deeper-than-1-level

Warning

Total

14

/

16

Passed

Repository

anbeime/skill

Path

skills/pptx-generator/pptx-generator/SKILL.md

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.