CtrlK
BlogDocsLog inGet started
Tessl Logo

pptx-validation-fallback

Validate PowerPoint files using python-pptx when read_file fails

60

Quality

70%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./benchmarks/gdpval/skills/pptx-validation-fallback/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

78%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 delivers fully executable, well-organized guidance for a single-purpose validation skill, with clear sequencing and a self-contained structure. Its main weakness is mild verbosity from repeated imports and explanatory asides that could be trimmed.

Suggestions

Consolidate the repeated `from pptx import Presentation` into one opening example or reference shared setup to reduce redundancy.

Add an explicit feedback loop in Step 3 (e.g., 'if validation fails, report which slides are missing titles/content and re-inspect') to reach top workflow clarity.

Trim the introductory 'This provides a reliable alternative...' sentence and the pip-install aside, which state things Claude already knows.

DimensionReasoningScore

Conciseness

The body is mostly efficient but includes some unnecessary padding (repeated imports across code blocks, 'This provides a reliable alternative...', and the pip-install aside) that could be tightened.

3 / 5

Actionability

Three complete, executable python-pptx code blocks cover slide counting, title extraction, structure validation, and detailed content extraction in copy-paste-ready form.

5 / 5

Workflow Clarity

Steps 1-4 are clearly sequenced with a failure check (Step 1) and structure validation (Step 3), but there is no explicit error-recovery feedback loop when validation reveals problems.

4 / 5

Progressive Disclosure

The skill is self-contained (~96 lines, no bundle files), single-purpose, and well-organized into When to Use, Procedure, Expected Output, Common Use Cases, and Dependencies sections with no need for external references.

5 / 5

Total

17

/

20

Passed

Description

62%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 states what and when with a narrow, distinct trigger, but it lists only one concrete action and underuses natural user-facing terms like 'presentations' and '.pptx'. Tightening trigger phrasing and broadening the action list would push it higher.

Suggestions

Broaden the action list to concrete capabilities (e.g., 'count slides, extract titles, and verify structure') to lift specificity.

Add natural synonyms users would say, such as 'presentations' and '.pptx files', alongside 'PowerPoint files'.

Expand the 'when' clause to cover the common trigger contexts (e.g., 'Use when read_file cannot parse .pptx files or when verifying slide count, titles, and structure').

DimensionReasoningScore

Specificity

The phrase 'Validate PowerPoint files' names the domain and one concrete action (validate), matching the anchor for 1-2 concrete actions without comprehensive coverage.

3 / 5

Completeness

Both 'what' (validate PowerPoint files using python-pptx) and 'when' (when read_file fails) are present and clear, though the 'when' trigger is narrow and could be more explicit.

4 / 5

Trigger Term Quality

'PowerPoint files' is a relevant natural term but the description leans on technical jargon (python-pptx, read_file) and misses common variations like 'presentations', 'slides', or '.pptx'.

3 / 5

Distinctiveness Conflict Risk

The conditional 'when read_file fails' trigger carves a fairly distinct niche with minor overlap risk against general pptx-handling skills.

4 / 5

Total

14

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
HKUDS/OpenSpace
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.