ppt-reliable-creation

Robust PowerPoint generation with shell_agent primary and python-pptx fallback, including directory verification and error debugging

Quality

57%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./benchmarks/gdpval/skills/ppt-workflow-location-enhanced-72b4a5/SKILL.md

Quality

Content

56%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 body delivers a well-sequenced, actionable dual-path workflow with validation and feedback loops, but it is noticeably verbose due to heavy repetition across overlapping sections and would benefit from splitting reference material into separate files. A minor bug in the Python example (missing os import) slightly reduces actionability.

Suggestions

Consolidate the redundant find/copy/verify and 2>&1 guidance into a single section; remove the overlapping Debugging Commands, Example Complete Workflow, and Troubleshooting Table entries that rehash Steps 3-5.

Fix the Python script by adding 'import os' before os.path.abspath so the example is copy-paste runnable.

Move the troubleshooting tables, debugging commands, and full example workflow into a separate reference file (e.g., TROUBLESHOOTING.md) referenced one level deep from SKILL.md to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The same find/cp/verify and 2>&1 operations are repeated across Steps 3-5, Debugging Commands, Example Complete Workflow, and the Pitfalls/Troubleshooting tables, giving several padded, redundant sections that could be consolidated.	2 / 5
Actionability	It provides concrete, mostly copy-paste-ready bash and python-pptx code, but the Python script references os.path.abspath without importing os, a minor gap that keeps it from being fully executable as written.	4 / 5
Workflow Clarity	A clear Step 0 through Step 5 sequence with explicit validation (2c directory match, Step 5 file checks) and a decision tree with feedback loops exists, but checkpoints are scattered across redundant sections, leaving minor gaps.	4 / 5
Progressive Disclosure	At roughly 290 lines with no bundle files, the skill is monolithic: debugging commands, troubleshooting tables, and the full example workflow are inlined rather than split into one-level-deep reference files, though section headers provide some structure.	3 / 5
	Total	13 / 20 Passed

Description

58%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 conveys a clear, specific capability set around PowerPoint generation with a primary/fallback strategy, but it lacks an explicit use-trigger clause and leans on the 'Robust' buzzword. Trigger-term coverage is limited to 'PowerPoint' without common synonyms or file extensions.

Suggestions

Add an explicit 'Use when...' trigger clause naming the natural phrases users say (e.g., 'Use when creating PowerPoint presentations, .pptx files, or slide decks').

Replace the buzzword 'Robust' with a concrete qualifier or drop it, and add synonyms like 'presentations', 'slides', and '.pptx' to broaden trigger-term coverage.

Clarify the 'when' by noting the failure/fallback condition as a trigger (e.g., 'Use when shell_agent PowerPoint generation fails or produces opaque errors').

Dimension	Reasoning	Score
Specificity	Names the PowerPoint domain plus several concrete actions ('shell_agent primary and python-pptx fallback', 'directory verification and error debugging'), but the buzzword 'Robust' is fluff that keeps it just below the comprehensive 5 anchor.	4 / 5
Completeness	It clearly states what the skill does but has no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the rubric.	3 / 5
Trigger Term Quality	It includes the natural term 'PowerPoint generation' but omits common variations and synonyms a user would say, such as 'presentations', 'slides', 'PPT', or '.pptx'.	3 / 5
Distinctiveness Conflict Risk	The dual-path PowerPoint-generation niche with named tools (shell_agent, python-pptx) is mostly distinct with only minor overlap risk against a general presentation skill, falling just short of the minimal-conflict 5 anchor.	4 / 5
	Total	14 / 20 Passed

Validation

100%

Warnings & errors only

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
Path: benchmarks/gdpval/skills/ppt-workflow-location-enhanced-72b4a5/SKILL.md
Commit: 3827781

Reviewed: 10 days ago

Table of Contents

Discovery Implementation Validation

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.