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.

54

Quality

61%

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

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.

The body is a thorough, well-sequenced guide with strong validation feedback loops and concrete commands, scoring high on workflow clarity and actionability. Its weaknesses are token-heavy inline design material that belongs in reference files and references to .md/ooxml files that are not present in the bundle.

Suggestions

Move the 18 color palettes and the Visual Details / Typography / Chart / Layout / Background option lists into a dedicated reference file (e.g., references/design-options.md) and link to it from SKILL.md.

Add the missing referenced files (html2pptx.md, ooxml.md, ooxml/scripts/unpack.py, validate.py, pack.py) to the bundle, or correct the paths to point at files that actually ship with the skill.

Include an executable html2pptx() code snippet and a minimal full HTML slide example so the create-without-template workflow is fully copy-paste ready.

DimensionReasoningScore

Conciseness

The workflow sections are efficient and assume competence, but the design section inlines heavy content Claude largely already knows (18 full color palettes, plus six bulleted categories of visual/typography/chart/layout/background options) that could be tightened or moved to a reference, matching the 'mostly efficient but includes unnecessary material' anchor.

3 / 5

Actionability

It provides copy-paste-ready commands with arguments across all workflows (markitdown, unpack/validate/pack, rearrange.py, inventory.py, replace.py, thumbnail.py, soffice, pdftoppm) plus concrete JSON schemas, but the html2pptx step only describes the html2pptx() call without an executable code snippet and shows no full HTML slide example, leaving a minor gap.

4 / 5

Workflow Clarity

Each path (create-without-template, edit-existing, create-from-template) is a clearly numbered sequence with explicit validation checkpoints — 'Validate immediately after each edit and fix any validation errors before proceeding', replace.py shape validation, and the thumbnail 'Repeat until all slides are visually correct' feedback loop — matching the anchor with explicit validation, error-recovery loops, and checklists.

5 / 5

Progressive Disclosure

Structure and reference signaling are good in intent (mandatory reads of html2pptx.md and ooxml.md for deep detail), but those referenced .md files and the ooxml/scripts/* paths do not exist in the actual bundle (only scripts/ with 5 files is present), so navigation is broken, and large design reference material (palettes, visual options) is inlined rather than split out.

3 / 5

Total

15

/

20

Passed

Description

53%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.

The description cleanly names the .pptx domain and its core actions but is written in second person and lacks an explicit "Use when" trigger clause, so it lands at mid-range across most dimensions. Adding natural synonyms (PowerPoint, presentation, slides) and an explicit trigger clause would lift completeness and trigger quality.

Suggestions

Add an explicit 'Use when...' clause naming concrete triggers (e.g., 'Use when creating, editing, or analyzing PowerPoint (.pptx) presentations, slides, or decks').

Include natural user synonyms — PowerPoint, presentation, slides, deck — not just the .pptx extension.

Rewrite in third person ('Creates, edits, and analyzes .pptx files') to avoid the second-person voice penalty.

DimensionReasoningScore

Specificity

The description names the .pptx domain and three concrete actions ("create, edit, or analyze the contents of a .pptx file"), which would anchor at 4, but it uses second-person voice ("A user may ask you to...", "You have different tools and workflows") and the actions are broad rather than granular, so specificity is reduced by 1 per the voice penalty.

3 / 5

Completeness

It has a clear "what" (create/edit/analyze .pptx contents) but no explicit "Use when..." trigger clause; the opening "A user may ask you to..." is only a weakly implied when, capping completeness at 3 per the missing-trigger guideline.

3 / 5

Trigger Term Quality

It surfaces the ".pptx file" extension and the create/edit/analyze verbs, but omits the most natural user terms ("PowerPoint", "presentation", "slides", "deck"), leaving common variations and synonyms missing as at anchor 3.

3 / 5

Distinctiveness Conflict Risk

The .pptx niche is specific and largely distinguishable from other skills with only minor overlap risk, though the generic closer ("different tools and workflows available for different tasks") keeps it just below a clean 5.

4 / 5

Total

13

/

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.

Validation14 / 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
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.