CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

pptx-skill

Create, edit, and extract content from PowerPoint (.pptx) files; use when you need to generate slides programmatically, update existing decks, or export slide previews.

Quality

74%

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 ./scientific-skills/Other/PPTX-Skill/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

46%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 split-quality body: the front half (When to Use, Dependencies, Example Usage, Implementation Details) is concrete and executable, but the back half is generic template filler, the only validation command is broken, and none of the real bundle scripts are surfaced. The skill advertises capabilities (thumbnails, PDF export, template support) whose actual tooling exists in the bundle yet is never linked.

Suggestions

Replace the generic boilerplate tail (When Not to Use, Required Inputs, Recommended Workflow, Deterministic Output Rules, Output Contract, Validation and Safety Rules, Failure Handling, Completion Checklist, Scope Reminder) with pptx-specific guidance or remove it entirely — these sections add tokens without adding anything Claude does not already know.

Surface the actual bundle scripts with one-line usage examples (e.g., `python scripts/office/unpack.py input.pptx`, `python scripts/office/validate.py unpacked/`, `python scripts/thumbnail.py input.pptx`), and fix the Quick Validation section — `scripts/__init__.py` is an empty file, so `python scripts/__init__.py --help` cannot produce the documented expected output.

Add an executable command for the advertised export features (e.g., the LibreOffice headless PPTX-to-PDF invocation) instead of only noting that 'export generally requires external rendering'.

DimensionReasoningScore

Conciseness

Roughly half the body is generic boilerplate unrelated to pptx specifics: "A clearly specified task goal aligned with the documented scope", "Keep output safe, reproducible, and within the documented scope at all times", and a "Scope Reminder" that repeats the frontmatter description verbatim. This matches 'Noticeably verbose; several unnecessary explanations or padded sections'; it is not 1 because the technical sections (Example Usage, Implementation Details) are reasonably tight and free of beginner-concept explanations.

2 / 5

Actionability

The Example Usage section is complete, executable, copy-paste-ready code covering creation (prs.slide_layouts[0]), text editing via TextFrame, image insertion with Pillow normalization, and title extraction, with concrete details like "prs.slide_layouts[0] for title slide". It is not 5 because the advertised export features have no commands ("Thumbnail/PDF export generally requires external rendering") and the Quick Validation command `python scripts/__init__.py --help` targets an empty 0-byte file and cannot produce the stated expected output; it is not 3 because the core create/edit/extract path is fully runnable with real code, not pseudocode.

4 / 5

Workflow Clarity

"Recommended Workflow" lists a sequence ("Validate the request against the skill boundary... Run a final validation pass") but all steps are abstract with no concrete checkpoints — matching 'Steps listed but validation gaps; sequence present but checkpoints missing or implicit'. It is not 4 because the only validation command is broken (empty scripts/__init__.py) and no step includes an executable checkpoint or feedback loop; it is not 2 because a coherent sequence plus dedicated Failure Handling and Completion Checklist sections do exist.

3 / 5

Progressive Disclosure

The bundle provides substantial tooling (scripts/add_slide.py, clean.py, thumbnail.py, and scripts/office/ with unpack.py, pack.py, validate.py, soffice.py) but the body never references any of them; the sole reference, "python scripts/__init__.py --help", points to an empty file. This matches 'Minimal structure; content that clearly belongs in separate files is inlined; or references are buried' — the OOXML editing/export workflows that live in the bundle are invisible from SKILL.md. It is not 3 because there is effectively no working navigation to the bundle at all, and not 1 because the body itself is well sectioned rather than an unstructured wall of text.

2 / 5

Total

11

/

20

Passed

Description

92%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, well-formed description: concrete actions, explicit 'use when' triggers with natural terminology and synonyms, and a clearly bounded PowerPoint/.pptx niche. Its only weakness is the absence of the term 'presentation(s)', the most natural synonym a user might say.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — "Create, edit, and extract content from PowerPoint (.pptx) files", "generate slides programmatically, update existing decks, or export slide previews" — covering creation, editing, extraction, and export comprehensively. This matches the anchor 'Lists multiple specific concrete actions; comprehensive coverage'; it is not 4 because there are no significant gaps in coverage of the skill's stated capabilities.

5 / 5

Completeness

It explicitly answers both what ("Create, edit, and extract content from PowerPoint (.pptx) files") and when with concrete trigger phrases ("use when you need to generate slides programmatically, update existing decks, or export slide previews"). This matches the anchor 'Clearly and explicitly answers both what AND when with concrete trigger phrases' — equivalent in structure to the anchor-5 PDF example — and clearly exceeds the anchor-4 pattern where the 'when' is less specific.

5 / 5

Trigger Term Quality

Natural user terms are present with synonyms and extension: "PowerPoint (.pptx)", "slides", "decks", "slide previews". It is not 5 because the most common phrasing users would say — "presentation(s)" — is absent; it is not 3 because coverage includes both synonyms (decks, slides) and the file extension (.pptx), going well beyond minimal keywords.

4 / 5

Distinctiveness Conflict Risk

"PowerPoint (.pptx)" is a clear niche with distinct triggers (pptx, decks, slide previews) and minimal conflict risk with other skills, matching the anchor-5 example where a specific file format with distinct triggers defines the niche.

5 / 5

Total

19

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

Repository

aipoch/medical-research-skills

Path

scientific-skills/Other/PPTX-Skill/SKILL.md

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.