CtrlK
BlogDocsLog inGet started
Tessl Logo

ppt-generation-resilient

Resilient PowerPoint generation with shell_agent primary path and python-pptx fallback

57

Quality

72%

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

Quality

Content

77%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 and clearly sequenced with strong validation and retry loops, making it a strong operational guide. Its main weaknesses are repetition of the stderr-capture advice across sections and a monolithic single-file structure with no progressive disclosure.

Suggestions

Consolidate the `2>&1` / stderr-capture guidance into one section and reference it elsewhere instead of restating it four times.

Move the full python-pptx script and the detailed troubleshooting recipes into references/ files (e.g. REFERENCE.md, TROUBLESHOOTING.md) and link to them one level deep from SKILL.md.

Drop the redundant 'Example: Complete Workflow' section or fold it into Step 2.1 so the same script is not demonstrated twice.

DimensionReasoningScore

Conciseness

The body is mostly actionable rather than explanatory of basics, but the `2>&1` stderr advice is repeated across four sections (Path 2, Common Pitfalls, Troubleshooting, Tool-Specific Notes) and the 'Example: Complete Workflow' re-demonstrates the script already shown, so it could be tightened.

3 / 5

Actionability

It provides fully executable, copy-paste-ready content: a complete python-pptx script with imports and slide-building logic, concrete bash commands (find/cp/mv/stat), and a specific shell_agent task template covering the common cases.

5 / 5

Workflow Clarity

Steps are explicitly sequenced (Path 1 → Path 2 → locate → copy → verify) with validation checkpoints (file path reported, size > 0, python-pptx re-open test), a retry feedback loop ('Fix and retry, max 3 attempts'), a decision tree, and a success-criteria checklist.

5 / 5

Progressive Disclosure

No bundle files exist and the skill is a single ~340-line file with good section headers but no file-level splitting; the full script, troubleshooting detail, and pitfalls table are inlined rather than moved to one-level-deep references.

3 / 5

Total

16

/

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 is specific about the domain and dual-path approach but lacks any explicit trigger guidance and leans on internal tooling terms rather than natural user keywords. It is competent but incomplete on the 'when' axis.

Suggestions

Add an explicit 'Use when...' clause naming natural triggers, e.g. 'Use when generating PowerPoint (.pptx) presentations, especially when shell_agent fails or returns opaque errors.'

Swap internal jargon ('shell_agent', 'python-pptx') for or pair them with user-facing terms like 'presentations', 'slides', 'decks', and '.pptx files'.

List the concrete capabilities (e.g., create, save, locate, and verify presentation files) rather than relying on the single word 'generation'.

DimensionReasoningScore

Specificity

The description names the domain ('PowerPoint generation') and two concrete implementation paths ('shell_agent primary path and python-pptx fallback'), but the only action stated is 'generation' — it is not a comprehensive list of distinct capabilities.

3 / 5

Completeness

It gives a clear 'what' (resilient PowerPoint generation via two paths) but contains no 'when' / 'Use when...' trigger clause, which per the rubric caps completeness at 3.

3 / 5

Trigger Term Quality

'PowerPoint' is a natural user term, but 'shell_agent' and 'python-pptx' are internal/technical jargon rather than user language, and common synonyms like 'presentation', 'slides', 'deck', and '.pptx' are absent.

3 / 5

Distinctiveness Conflict Risk

The 'resilient PowerPoint generation with fallback' framing carves a fairly distinct niche with only minor overlap risk against a general presentation skill.

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.

Validation — 16 / 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.