CtrlK
BlogDocsLog inGet started
Tessl Logo

pptx-debug-workflow

Systematic debugging workflow for python-pptx presentation generation

59

Quality

68%

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

82%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 is highly actionable with executable code throughout and a clear six-step workflow including validation. It is concise and well-structured, with only minor redundancy and an implicit rather than explicit error-recovery feedback loop.

DimensionReasoningScore

Conciseness

The body is mostly lean code and commands with minimal preamble, though the opening paragraph ('This workflow ensures reliable presentation generation through iterative verification...') and the partially redundant Quick Reference Template add minor padding; not a 5 because of these trimmable elements.

4 / 5

Actionability

Provides copy-paste ready, fully executable pip commands and Python snippets covering installation, minimal creation, table/chart patterns, and a complete template, matching the anchor for fully executable guidance covering common cases.

5 / 5

Workflow Clarity

Six steps are clearly sequenced with a minimal-creation test (Step 2), traceback capture (Step 4), and output validation (Step 6); not a 5 because the fix->re-run feedback loop is implicit rather than an explicit 're-execute and confirm the error is resolved' checkpoint.

4 / 5

Progressive Disclosure

Well-organized into clearly headed sections (steps, troubleshooting table, template) with no nested references and content appropriately inline for the size; not a 5 because no external reference files split out the API patterns or template, and the file exceeds the simple-skill line count.

4 / 5

Total

17

/

20

Passed

Description

53%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 clearly identifies the domain and purpose but lacks an explicit 'Use when' trigger clause and broader natural synonyms (PowerPoint, slides, .pptx). It is specific enough to avoid most conflicts but would benefit from explicit usage triggers.

Suggestions

Add a 'Use when...' clause specifying trigger scenarios, e.g. 'Use when generating or debugging PowerPoint presentations with python-pptx.'

Include natural synonyms and file extensions users would say: PowerPoint, slides, .pptx, decks.

Expand the action list beyond 'debugging workflow' to concrete capabilities (e.g., creating, editing, fixing chart/table API errors).

DimensionReasoningScore

Specificity

Names the domain ('python-pptx presentation generation') and one concrete action ('debugging workflow'), but coverage is minimal and not comprehensive, matching the anchor for naming a domain with 1-2 concrete actions.

3 / 5

Completeness

Provides a clear 'what' (systematic debugging workflow) but has no 'Use when...' trigger clause; per the rubric a missing explicit trigger guidance caps completeness at 3.

3 / 5

Trigger Term Quality

Includes the natural term 'python-pptx' and 'presentation', but misses common synonyms and extensions users would say (PowerPoint, slides, .pptx, decks), matching the 'some relevant keywords but missing variations' anchor.

3 / 5

Distinctiveness Conflict Risk

Tied to a specific library (python-pptx) giving it a clear niche with only minor overlap risk against general presentation skills; not a 5 because 'debugging workflow' is somewhat generic process language.

4 / 5

Total

13

/

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.