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

64

Quality

76%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./resources/skills/pptx/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

70%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 skill with excellent, well-validated workflows covering creation, editing, and templating. Its weaknesses are token bloat from design-catalog and schema content inlined in SKILL.md, and broken navigation: the mandatory html2pptx.md and ooxml.md references do not exist in the bundle.

Suggestions

Move the 18-entry color-palette catalog, visual-detail treatments, and the inventory JSON schema into a separate reference file (e.g., design.md) and link to it from SKILL.md to cut inline token cost.

Fix the broken bundle references: either include html2pptx.md, ooxml.md, and the ooxml/scripts/ (unpack.py, validate.py, pack.py) files in the bundle, or rewrite those workflow steps to be self-contained.

Trim redundant emphasis by consolidating the many repeated CRITICAL/MANDATORY/IMPORTANT markers — each workflow needs at most one or two flagged points.

DimensionReasoningScore

Conciseness

The body inlines ~90 lines of visual-detail treatments, an 18-entry color-palette catalog, and a ~60-line inventory JSON schema that belong in reference files, and repeats CRITICAL/MANDATORY emphasis heavily — mostly useful operational content but clearly tighten-able. Not 2, since nothing explains concepts Claude already knows.

3 / 5

Actionability

Commands are concrete and copy-paste ready throughout (markitdown, rearrange.py, replace.py, thumbnail.py, pdftoppm, plus worked JSON examples and sample validation errors), but the html2pptx conversion step has no inline code example and its mandated reference (html2pptx.md) is absent from the bundle, leaving minor gaps.

4 / 5

Workflow Clarity

Three workflows are explicitly numbered with validation checkpoints and feedback loops: 'Validate immediately after each edit and fix any validation errors before proceeding', the visual thumbnail inspection loop with named failure modes (text cutoff, overlap, contrast) and 'Repeat until all slides are visually correct', and worked validation-error examples.

5 / 5

Progressive Disclosure

References are clearly signaled and scripts/ contents match, but the two mandatory one-level-deep references (html2pptx.md and ooxml.md) and all ooxml/scripts/* paths referenced in the body are missing from the bundle, and large reference-appropriate content (palettes, visual treatments, inventory schema) is inlined in SKILL.md.

3 / 5

Total

15

/

20

Passed

Description

83%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 pairs a concise capability statement with an explicit, enumerated use-when clause tied to the .pptx domain. Its only weaknesses are the catch-all closing phrase and missing common synonyms like 'PowerPoint' and 'slides'.

DimensionReasoningScore

Specificity

Enumerates several concrete actions — creating new presentations, modifying or editing content, working with layouts, adding comments or speaker notes — but 'analysis' is generic and slide-level operations are not covered, matching the 'several specific actions; minor gaps' anchor rather than comprehensive coverage.

4 / 5

Completeness

Explicitly answers both what ('Presentation creation, editing, and analysis') and when ('When Claude needs to work with presentations (.pptx files) for: ...') with concrete trigger phrases; not 4 because the when-clause is fully explicit rather than improvable.

5 / 5

Trigger Term Quality

Natural terms like 'presentations', '.pptx files', 'speaker notes', 'comments', and 'layouts' are present, but common synonyms users would say — 'PowerPoint', 'slides', 'decks' — are missing, so coverage is good rather than comprehensive.

4 / 5

Distinctiveness Conflict Risk

The '.pptx files' scope carves a clear niche with minimal conflict against non-presentation skills, but the trailing 'or any other presentation tasks' is a catch-all that broadens overlap with related document skills, keeping it below a clear-niche 5.

4 / 5

Total

17

/

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

relative_links

Relative link issues: 2 missing

Warning

Total

14

/

16

Passed

Repository
ThinkInAIXYZ/deepchat
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.