pptx

Presentation creation, editing, and analysis. When Claude needs to work with presentations (.pptx files) for: (1) Creating new presentations, (2) Modifying or editing content, (3) Working with layouts, (4) Adding comments or speaker notes, or any other presentation tasks

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Medium

Suggest reviewing before use

Quality

Content

77%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The skill body is highly actionable and well-sequenced with strong validation feedback loops for fragile OOXML and layout operations. Its main weaknesses are verbosity from an inline design catalog and two clearly-signaled reference files (html2pptx.md, ooxml.md) that are missing from the bundle.

Suggestions

Ship the referenced html2pptx.md and ooxml.md alongside SKILL.md (or inline the essential parts) so the "READ ENTIRE FILE" navigation resolves to real files.

Move the 18-palette color catalog and the visual-details/typography/chart-styling option lists into a separate reference (e.g. design-ideas.md) to reduce SKILL.md's token footprint.

Trim redundant emphasis markers (e.g. repeated MANDATORY/CRITICAL/NEVER bolding) where a single clear directive would carry the same instruction.

Dimension	Reasoning	Score
Conciseness	The core workflows are tight and executable, but large encyclopedic catalogs (18 numbered color palettes with hex codes, dozens of visual-detail and typography-treatment bullets) pad the file with material that could be trimmed or moved to a reference; it is mostly efficient but could be tightened.	2 / 3
Actionability	Provides fully executable commands and copy-paste-ready examples throughout — e.g. `python ooxml/scripts/unpack.py <office_file> <output_dir>`, `python scripts/thumbnail.py output.pptx workspace/thumbnails --cols 4`, and a complete replacement-text JSON structure — with concrete API guidance.	3 / 3
Workflow Clarity	Each major task is a clearly numbered sequence with explicit validation checkpoints and feedback loops ("Validate immediately after each edit and fix any validation errors before proceeding", "Repeat until all slides are visually correct") plus example validation errors, matching the anchor for clear sequence with explicit validation.	3 / 3
Progressive Disclosure	The body signals one-level-deep references to html2pptx.md and ooxml.md with clear "READ ENTIRE FILE" callouts, but those referenced files are not present in the bundle, and a large design-ideas catalog is kept inline that could live in a separate reference; structure is decent but not cleanly split.	2 / 3
	Total	10 / 12 Passed

Description

100%

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 a strong, concrete, third-person statement that names several specific actions and gives an explicit "when" trigger tied to natural terms like .pptx and presentations. It matches the rubric's own good-example list and answers both what and when.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions — "Creating new presentations", "Modifying or editing content", "Working with layouts", "Adding comments or speaker notes" — matching the anchor for listing several specific actions.	3 / 3
Completeness	Explicitly answers both what ("Presentation creation, editing, and analysis") and when ("When Claude needs to work with presentations (.pptx files) for: ..."), satisfying the anchor requiring both an explicit what and an explicit trigger clause.	3 / 3
Trigger Term Quality	Includes natural, user-facing terms users would actually say ("presentations", ".pptx files", "comments", "speaker notes", "layouts") with good coverage rather than technical jargon.	3 / 3
Distinctiveness Conflict Risk	The .pptx/presentation niche is clearly distinct with dedicated triggers, making it unlikely to fire for other skills.	3 / 3
	Total	12 / 12 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: netease-youdao/LobsterAI
Path: SKILLs/pptx/SKILL.md
Commit: 2921c1e

Reviewed: about 11 hours ago

Table of Contents

Discovery Implementation Validation

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.