CtrlK
BlogDocsLog inGet started
Tessl Logo

pptx-official

A user may ask you to create, edit, or analyze the contents of a .pptx file. A .pptx file is essentially a ZIP archive containing XML files and other resources that you can read or edit. You have different tools and workflows available for different tasks.

48

Quality

53%

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 ./plugins/antigravity-bundle-documents-presentations/skills/pptx-official/SKILL.md

The canonical home for this skill is pptx-official in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

56%Scale 1-5

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

This is a comprehensive skill covering multiple PPTX workflows with good actionability and clear step-by-step processes. Its main weakness is severe verbosity — the color palettes, visual design options, and extensive JSON examples inflate the file well beyond what's needed in the main skill file. Moving design guidance and detailed format specifications to referenced files would significantly improve token efficiency while maintaining the strong workflow structure.

Suggestions

Move the 18 color palettes and visual details options (geometric patterns, border treatments, typography treatments, etc.) to a separate design-guide.md file referenced from the main skill — this alone would cut ~100 lines

Move the detailed JSON schema examples and formatting patterns for the template workflow to a separate template-workflow-reference.md, keeping only a brief summary and link in SKILL.md

Remove explanatory text Claude already knows (e.g., 'A .pptx file is essentially a ZIP archive containing XML files') and trim redundant instructions like repeated 'NEVER set any range limits when reading this file'

Add an explicit error-recovery loop to the editing workflow: after validate.py fails, describe the fix-revalidate cycle more concretely rather than just stating 'fix any validation errors before proceeding'

DimensionReasoningScore

Conciseness

The skill is extremely verbose at ~400+ lines. The color palette section alone lists 18 palettes with hex codes that could be summarized or moved to a reference file. The visual details options section extensively lists design patterns Claude already understands. Many sections over-explain concepts (e.g., what a .pptx file is, detailed JSON schema examples that could be in a reference file).

2 / 5

Actionability

The skill provides concrete, executable commands throughout (unpack.py, pack.py, validate.py, rearrange.py, inventory.py, replace.py, thumbnail.py) with specific syntax and examples. JSON format examples are detailed and copy-paste ready. Minor gaps exist where some script paths are uncertain (the 'Note' about using find to locate unpack.py suggests potential path issues).

4 / 5

Workflow Clarity

Three distinct workflows (creating without template, editing, creating with template) are clearly sequenced with numbered steps. The editing workflow includes a critical validation step with validate.py. The template-based creation workflow is thorough with 7 well-defined steps. However, the 'creating without template' workflow's validation step (visual thumbnail inspection) is less rigorous than explicit programmatic validation, and the editing workflow could more explicitly describe the fix-and-retry loop.

4 / 5

Progressive Disclosure

The skill references external files (html2pptx.md, ooxml.md) appropriately for detailed guidance, which is good. However, massive amounts of content that should be in separate files are inlined — the 18 color palettes, the extensive visual details options, and the detailed JSON schema examples all bloat the main SKILL.md. Without bundle files provided, we can't verify the referenced paths exist, but the structure suggests content that belongs in supplementary files.

3 / 5

Total

13

/

20

Passed

Description

50%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 identifies the correct domain (.pptx files) and provides some useful context about the file format, but it lacks specific sub-actions, natural trigger terms users would say (e.g., 'presentation,' 'PowerPoint,' 'slides'), and an explicit 'Use when...' clause. The second-person voice ('A user may ask you to') is borderline but doesn't use 'you can use this' phrasing directly. Overall, it's a functional but underspecified description that would benefit from richer keywords and explicit trigger guidance.

Suggestions

Add an explicit 'Use when...' clause with trigger terms like 'presentation', 'PowerPoint', 'slides', '.pptx', 'slideshow', 'speaker notes'.

List more specific actions such as 'creating new presentations, modifying slide layouts, adding speaker notes, inserting images, or extracting slide content'.

Include natural synonyms and variations users would say, e.g., 'PowerPoint', 'presentation', 'deck', 'slides', alongside the technical '.pptx'.

DimensionReasoningScore

Specificity

Names the domain (.pptx files) and lists three general actions (create, edit, analyze), but doesn't elaborate on specific sub-actions like adding slides, modifying layouts, inserting images, or generating charts.

3 / 5

Completeness

The 'what' is partially addressed (create, edit, analyze .pptx files) and there's a weak implied 'when' ('A user may ask you to...'), but there is no explicit 'Use when...' clause with concrete trigger phrases. The rubric caps completeness at 3 without an explicit trigger guidance clause.

3 / 5

Trigger Term Quality

Includes '.pptx' as a file extension and mentions 'create, edit, or analyze,' but misses natural user terms like 'presentation,' 'PowerPoint,' 'slides,' 'speaker notes,' or 'slideshow.'

3 / 5

Distinctiveness Conflict Risk

Mentioning .pptx specifically helps distinguish it from generic document skills, but the broad verbs 'create, edit, or analyze' and the mention of 'ZIP archive containing XML files' could overlap with other XML/archive-handling skills. Missing terms like 'presentation' or 'PowerPoint' that would sharpen its niche.

3 / 5

Total

12

/

20

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
administrakt0r/AI-Agents-Safe-Coding-Skills
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.