CtrlK
BlogDocsLog inGet started
Tessl Logo

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

85

2.90x
Quality

81%

Does it follow best practices?

Impact

90%

2.90x

Average score across 3 eval scenarios

SecuritybySnyk

Advisory

Suggest reviewing before use

SKILL.md
Quality
Evals
Security

Quality

Content

62%

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

The skill excels at actionability and workflow clarity with concrete commands, validation steps, and clear sequential processes for all major PPTX operations. However, it is severely bloated with content Claude doesn't need inline—18 color palettes, extensive design catalogs, and lengthy JSON schema examples that should be in referenced files. The progressive disclosure is partially implemented but undermined by the sheer volume of inline content.

Suggestions

Move the 18 color palettes and visual details options (geometric patterns, border treatments, typography treatments, etc.) to a separate design-reference.md file and reference it from the main skill

Move the detailed JSON schema examples and formatting patterns for the template workflow into a separate template-workflow-reference.md, keeping only a brief summary and one minimal example inline

Remove explanatory text Claude already knows (e.g., 'A .pptx file is essentially a ZIP archive containing XML files', general design principles about readability and contrast) to reduce token usage

Consolidate the dependency list into a single requirements file reference rather than listing installation commands inline

DimensionReasoningScore

Conciseness

The skill is extremely verbose at ~400+ lines. The color palette section alone lists 18 palettes with hex codes, the visual details options section is a massive catalog of design ideas, and the template workflow includes extensive JSON schema examples and formatting patterns. Much of this (design principles, color theory, layout innovations) is knowledge Claude already possesses. The content could be cut by 50%+ without losing actionable value.

1 / 3

Actionability

The skill provides concrete, executable commands throughout (python scripts with exact arguments, bash commands, JSON schemas with complete examples). Every workflow has specific copy-paste ready commands and the replacement JSON format is thoroughly documented with working examples.

3 / 3

Workflow Clarity

All three major workflows (creating without template, editing, creating with template) have clearly numbered sequential steps with explicit validation checkpoints. The editing workflow includes validate-then-fix loops, the creation workflow includes visual validation with thumbnail inspection and re-generation, and the template workflow has inventory validation before replacement.

3 / 3

Progressive Disclosure

The skill references external files (html2pptx.md, ooxml.md, scripts/) appropriately and uses one-level-deep references. However, the massive inline content (color palettes, visual details options, JSON schemas, formatting patterns) should be split into separate reference files rather than bloating the main SKILL.md. The file tries to be both an overview and a comprehensive reference simultaneously.

2 / 3

Total

9

/

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.

This is a strong skill description that clearly defines its scope around PowerPoint presentation tasks. It provides explicit trigger conditions with a numbered list of use cases, includes the file format (.pptx), and covers a comprehensive range of presentation-related actions. It matches one of the rubric's 'good overall examples' almost exactly, demonstrating best practices.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions: creating presentations, modifying/editing content, working with layouts, adding comments or speaker notes. These are distinct, actionable capabilities.

3 / 3

Completeness

Clearly answers both 'what' (presentation creation, editing, analysis) and 'when' ('When Claude needs to work with presentations (.pptx files) for:' followed by explicit trigger scenarios). The 'when' clause is explicit and well-structured.

3 / 3

Trigger Term Quality

Includes strong natural trigger terms users would say: 'presentations', '.pptx files', 'creating new presentations', 'editing content', 'layouts', 'comments', 'speaker notes'. Covers common variations of how users would describe presentation tasks.

3 / 3

Distinctiveness Conflict Risk

Clearly scoped to .pptx presentation files with specific triggers like 'presentations', 'speaker notes', and 'layouts' that are unlikely to conflict with other document-handling skills like PDF or spreadsheet tools.

3 / 3

Total

12

/

12

Passed

Validation

90%

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

Validation10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

10

/

11

Passed

Repository
davepoon/buildwithclaude
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.