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

75%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./scientific-skills/Other/PPTX-Skill/SKILL.md

Quality

Content

50%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 content pairs a strong, executable python-pptx example with useful implementation notes, but undermines itself with extensive generic boilerplate and a disconnect from the actual bundle scripts. The real workflow tooling exists in the bundle yet is never surfaced, leaving navigation and concrete workflow guidance weak.

Suggestions

Remove the generic boilerplate sections (Output Contract, Deterministic Output Rules, Validation and Safety Rules, Failure Handling, Completion Checklist, Scope Reminder) that do not add pptx-specific knowledge, or replace them with pptx-specific guidance.

Reference the actual bundle scripts (e.g., `python scripts/office/unpack.py`, `scripts/office/validate.py`, `scripts/office/pack.py`, `scripts/add_slide.py`, `scripts/thumbnail.py`, `scripts/clean.py`) so Claude can navigate to the real tooling instead of the python-pptx-only example.

Fix the 'Quick Validation' command: `python scripts/__init__.py --help` targets an empty file and produces no help — replace it with a real, runnable verification step such as invoking one of the bundle scripts with `--help`.

Dimension	Reasoning	Score
Conciseness	The pptx-specific sections (features, dependencies, code example, implementation details) are efficient, but roughly half the body is generic boilerplate — 'When Not to Use', 'Required Inputs', 'Recommended Workflow', 'Deterministic Output Rules', 'Output Contract', 'Validation and Safety Rules', 'Failure Handling', 'Completion Checklist', 'Scope Reminder' — that restate process concepts Claude already knows without adding pptx-specific value.	2 / 5
Actionability	The python-pptx example is concrete and copy-paste ready, covering create/bullets/image/edit/extract common cases, but the 'Quick Validation' command `python scripts/__init__.py --help` is non-functional (the file is empty) and the real bundle scripts are never surfaced as actionable commands.	4 / 5
Workflow Clarity	A 'Recommended Workflow' with four steps exists, but the steps are generic and abstract ('select the documented execution path', 'run a final validation pass') rather than concrete pptx commands; validation checkpoints are implicit and the actual unpack→edit→validate→repack flow enabled by the bundle scripts is never described.	3 / 5
Progressive Disclosure	The body is sectioned, but the provided bundle scripts (add_slide.py, clean.py, thumbnail.py, office/unpack.py, pack.py, validate.py, validators/pptx.py) are not referenced or linked anywhere; the only script reference points to an empty __init__.py, so navigation to the real tooling is missing.	3 / 5
	Total	12 / 20 Passed

Description

100%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 is concise, third-person, and explicitly answers both what the skill does and when to use it with concrete, natural trigger terms. It is a strong, well-scoped description with no over-claims.

Dimension	Reasoning	Score
Specificity	Names the .pptx domain and lists multiple concrete actions — 'Create, edit, and extract content', 'generate slides programmatically', 'update existing decks', 'export slide previews' — giving comprehensive coverage rather than a single generic verb.	5 / 5
Completeness	Explicitly states what it does ('Create, edit, and extract content from PowerPoint (.pptx) files') and when to use it ('use when you need to generate slides programmatically, update existing decks, or export slide previews') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Includes natural user terms and synonyms — 'PowerPoint', '.pptx', 'slides', 'decks' — plus the file extension, covering the variations a user would actually say; only 'presentations' is absent but 'decks' and 'slides' compensate.	5 / 5
Distinctiveness Conflict Risk	PowerPoint/.pptx is a clear niche with distinct triggers (slides, decks, .pptx) and minimal overlap risk with other document or data skills.	5 / 5
	Total	20 / 20 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
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
Commit: 63c61d3

Reviewed: 9 hours ago

Table of Contents

Discovery Implementation Validation

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.