CtrlK
BlogDocsLog inGet started
Tessl Logo

pptx-debug-workflow

Systematic debugging workflow for python-pptx presentation generation

56

Quality

63%

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-debug-workflow/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

77%

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, validated workflow, but it is somewhat padded (a redundant template and troubleshooting table) and monolithic with no progressive disclosure structure.

Suggestions

Remove the 'Quick Reference Script Template' section or fold it into Step 3, since it duplicates the existing example structure and inflates the body.

Move the per-API patterns (chart legend, table cells, chart data) and the troubleshooting table into a separate reference file, leaving a concise overview in SKILL.md.

Trim explanatory lines like 'Run this first to confirm basic functionality' that restate what the preceding code already makes obvious.

DimensionReasoningScore

Conciseness

The body is mostly efficient and avoids explaining basic concepts, but the 'Quick Reference Script Template' largely duplicates the Step 3 example and the 'Common Troubleshooting' table repeats Step 5's API patterns, adding padding that could be tightened.

2 / 3

Actionability

It provides fully executable pip commands and complete, copy-paste-ready Python snippets for installation, minimal creation, table cell access, and chart data, with specific API patterns rather than pseudocode.

3 / 3

Workflow Clarity

Steps 1–6 are clearly sequenced with an explicit validation step (Step 6) and a concrete error-recovery feedback loop (Step 4 captures the traceback, Step 5 fixes API errors iteratively).

3 / 3

Progressive Disclosure

Sections are well-organized, but the skill is a 155-line monolithic file with no bundle references, and content like the API patterns and template is inline where it could be split out for a leaner overview.

2 / 3

Total

10

/

12

Passed

Description

50%

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 names a specific domain and action but is uniformly mid-tier: it lacks explicit trigger guidance, common keyword variations, and a list of concrete capabilities. It is clear but not comprehensive or trigger-rich.

Suggestions

Add a 'Use when...' clause with explicit triggers, e.g. 'Use when generating or debugging PowerPoint (.pptx) presentations with python-pptx, fixing chart/table API errors, or resolving import issues.'

Enumerate concrete capabilities (e.g. create slides, add tables, position chart legends, fix API errors) instead of the generic 'debugging workflow'.

Include natural user terms such as 'PowerPoint', 'pptx', '.pptx', and 'slides' alongside 'python-pptx' to improve trigger-term coverage.

DimensionReasoningScore

Specificity

The phrase 'debugging workflow for python-pptx presentation generation' names a clear domain and a general action, but it does not list multiple specific concrete actions (e.g. create slides, add tables, fix API errors), so it falls short of the top anchor.

2 / 3

Completeness

It states what the skill does but provides no 'Use when...' clause or equivalent explicit trigger guidance, which per the judging guidelines caps completeness at 2.

2 / 3

Trigger Term Quality

It includes relevant keywords like 'python-pptx', 'presentation', and 'debugging', but omits common natural variations a user might say such as 'PowerPoint', 'pptx', 'slides', or '.pptx'.

2 / 3

Distinctiveness Conflict Risk

Tying it to python-pptx gives it a niche, but 'systematic debugging workflow' is generic enough to overlap with general debugging skills, and there are no explicit distinct triggers.

2 / 3

Total

8

/

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.