CtrlK
BlogDocsLog inGet started
Tessl Logo

pptx-skill

当用户要求对 PowerPoint 幻灯片(.pptx)做任何操作时触发:阅读、总结、提取、编辑、创建、格式转换均适用。核心认知:PPTX 是视觉结构化文件——图表、排版、示意图等内容靠纯文字抽取无法可靠还原。理解幻灯片内容的正确路径是:用 PptxInspect render 把目标页渲染成 PNG,再交给视觉模型(CloudImageUnderstand)理解,而不是仅靠 text/outline 文字提取。文字工具仅作补充上下文使用。典型说法:"总结这份 PPT"、"这个 deck 在讲什么"、"第 3 页讲什么"、"描述第 5 页内容"、"帮我做一份 Q4 汇报 PPT"、"改第 3 页标题"。用户提到 .pptx 文件、deck、幻灯片、演示文稿时都加载本技能。

70

Quality

86%

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

SKILL.md
Quality
Evals
Security

Quality

Content

72%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 highly actionable, token-efficient body with executable demos and good read-path sequencing, but destructive/batch write workflows lack validation checkpoints and all content is inlined in one file with no progressive disclosure to references.

Suggestions

Add a validation step after destructive XML edits — e.g. re-open with PptxInspect summary or render the changed slide — to confirm the file is still valid and the edit landed before reporting success.

Split the three full pptxgenjs/adm-zip demos into a references/ file (e.g. examples.md) and keep SKILL.md as an overview that points to them, so the skill practices one-level-deep progressive disclosure.

Add a verify checkpoint to the batch N-page generation demo (e.g. assert slideCount or render a sample slide) so batch operations are not left unvalidated.

DimensionReasoningScore

Conciseness

The body is dense and information-rich, assuming Claude knows pptxgenjs/adm-zip without explaining them; the three code demos are long but each covers a distinct common case and earns its place, with only minor prose that could be trimmed.

4 / 5

Actionability

It provides three fully executable copy-paste demos, concrete tool invocations with parameters (e.g. PptxInspect { action: "summary", … }), and a compact symptom→cause→fix table covering common cases.

5 / 5

Workflow Clarity

The read path has a clear summary→dispatch sequence and the visual-recognition branch has an explicit anti-hallucination checkpoint, but the destructive XML-edit (2.3) and batch generation (2.2) workflows lack validation/verification steps, capping this per the destructive-operations rule.

3 / 5

Progressive Disclosure

The body is well-organized into numbered sections with tables and callouts, but it is a single monolithic ~250-line file with three long inline code demos and no external reference files to offload detail.

3 / 5

Total

15

/

20

Passed

Description

100%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 strong description that explicitly covers what, when, and natural trigger phrases with file extensions and synonyms in third-person voice. The embedded "核心认知" guidance is substantive though slightly instructional for a description field.

DimensionReasoningScore

Specificity

The description enumerates six concrete operations — "阅读、总结、提取、编辑、创建、格式转换" — giving comprehensive coverage of the PPTX domain rather than vague language, matching the anchor for multiple specific concrete actions.

5 / 5

Completeness

It explicitly answers both what (the six operations) and when ("当用户要求…时触发", "用户提到 .pptx 文件、deck、幻灯片、演示文稿时都加载本技能") with concrete trigger phrases, in third-person voice.

5 / 5

Trigger Term Quality

It lists natural user phrases ("总结这份 PPT", "这个 deck 在讲什么", "改第 3 页标题") plus synonyms (deck/幻灯片/演示文稿) and the .pptx extension, giving comprehensive coverage of terms users actually say.

5 / 5

Distinctiveness Conflict Risk

It is tightly scoped to PowerPoint artifacts (.pptx/deck/幻灯片/演示文稿) with distinct triggers, leaving minimal overlap risk with other skills.

5 / 5

Total

20

/

20

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
itsablabla/openloaf-web
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.