CtrlK
BlogDocsLog inGet started
Tessl Logo

pptx-file-validation

Validate PowerPoint files using python-pptx when standard file readers fail

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

Passed

No findings from the security scan

Fix and improve this skill with Tessl

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

Quality

Content

72%

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

The content is highly actionable with executable code and a clear step sequence, organized into clean sections with no need for external references. Its main weaknesses are minor redundancy and a lack of explicit error-recovery checkpoints in the workflow.

Suggestions

Remove the redundant 'Example Usage' block or the 'Benefits' section to tighten token usage.

Add an explicit feedback loop in Step 3 (e.g., if the script errors or output is unexpected, re-run with adjusted arguments) to strengthen workflow clarity.

Note the dependency-installation step earlier in the flow so the executable command does not assume python-pptx is already present.

DimensionReasoningScore

Conciseness

The body is mostly efficient and avoids explaining concepts Claude already knows, but the 'Example Usage' section duplicates the Step 2 code and the closing 'Benefits' section is marketing-style padding that could be trimmed.

2 / 3

Actionability

Provides fully executable `python3 -c` and `pip install` commands with concrete, copy-paste-ready examples and specific output to parse, matching the top anchor.

3 / 3

Workflow Clarity

The four steps are clearly sequenced and include a verify step, but Step 3 validates the file's contents (the task goal) rather than providing an explicit error-recovery feedback loop or proceed-only-when-valid gating.

2 / 3

Progressive Disclosure

No bundle files exist and none are needed for this self-contained, single-purpose skill, which is organized into clear labeled sections (When to Use, Steps, Example, Prerequisites), satisfying the well-organized-sections guidance.

3 / 3

Total

10

/

12

Passed

Description

67%

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 clear and includes an explicit when-to-use trigger, but it is narrow in action coverage and trigger vocabulary. It distinguishes a real niche yet risks overlapping with general PowerPoint skills.

Suggestions

List more concrete actions (e.g., inspect slide count, titles, structure) to raise specificity.

Add natural trigger variations such as '.pptx', 'slides', and 'presentations' so users' phrasing matches the skill.

Sharpen distinctiveness by framing the trigger around read_file/standard-reader failure specifically for .pptx files.

DimensionReasoningScore

Specificity

Names the domain ('PowerPoint files') and one concrete action ('Validate') plus the tool ('python-pptx'), but lists only a single action rather than multiple specific concrete actions, so it stops short of the top anchor.

2 / 3

Completeness

Explicitly states both what it does ('Validate PowerPoint files using python-pptx') and when to use it ('when standard file readers fail'), so the 'when' is explicit rather than missing or implied.

3 / 3

Trigger Term Quality

Includes the natural term 'PowerPoint files' but omits common variations users would say such as 'pptx', '.pptx', 'slides', or 'presentations', matching the 'some relevant keywords but missing common variations' anchor.

2 / 3

Distinctiveness Conflict Risk

The validation-when-readers-fail niche is somewhat specific, but the bare 'PowerPoint files' trigger could still overlap with broader pptx creation/editing skills, so it is not a fully distinct niche.

2 / 3

Total

9

/

12

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.