ppt-workflow-location

Generate PowerPoint files using shell_agent and locate them in nested workspace directories

Quality

60%

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/SKILL.md

Quality

Content

70%

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

The workflow is clearly sequenced with a genuine verification step and error-recovery guidance, and it is well-organized as a self-contained skill. Its main weaknesses are over-explanation of basic commands and a non-executable, placeholder-heavy generation step.

Suggestions

Tighten Step 1 into concrete, actionable delegation guidance (e.g., a ready-to-use prompt with a real topic placeholder convention and required output fields) instead of a prose bullet list inside a code fence.

Remove the redundant 'Example Workflow' section and the line-by-line comments on basic commands (cp, mv, ls) that Claude already knows, to reclaim token budget.

Keep only the troubleshooting entries that add information beyond the Common Pitfalls section to avoid duplicated guidance.

Dimension	Reasoning	Score
Conciseness	The body is mostly action-oriented but over-explains basic shell commands Claude already knows (cp, mv, ls, file) and includes a redundant 'Example Workflow' section that repeats Steps 2-4, so it could be tightened without losing clarity.	2 / 3
Actionability	The find/cp/ls/file commands are executable, but the core Step 1 offers only a non-executable prompt template with placeholders ([topic], /path/to/found/...) rather than concrete, copy-paste-ready generation guidance.	2 / 3
Workflow Clarity	A clearly numbered Generate → Locate → Copy → Verify sequence includes an explicit validation checkpoint (Step 4 checks existence and file size) plus a troubleshooting table providing feedback loops for error recovery, matching the top anchor.	3 / 3
Progressive Disclosure	The skill is self-contained with well-organized, navigable sections (When to Use, Steps 1-4, Pitfalls, Troubleshooting), no nested references, and no content that warrants a separate file, satisfying the top anchor for simple skills.	3 / 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 states concrete capabilities but omits any 'Use when' trigger guidance and relies on internal jargon, leaving it at the mid-level across all dimensions. It is clear about what it does but not when to invoke it.

Suggestions

Add an explicit 'Use when...' clause with natural triggers, e.g., 'Use when you need to create PowerPoint presentations (.pptx) and direct document tools are unavailable.'

Replace jargon like 'shell_agent' and 'nested workspace directories' with user-facing terms such as 'presentations', 'slides', and '.pptx' to improve trigger-term coverage.

Broaden the capability list beyond generate/locate (e.g., mention slide content and structure) to lift specificity toward a comprehensive action set.

Dimension	Reasoning	Score
Specificity	Names the PowerPoint domain and two concrete actions ('Generate PowerPoint files', 'locate them in nested workspace directories'), but is not comprehensive — it omits editing, reading, or converting, matching the 'names domain and some actions' anchor rather than the multi-action anchor 3.	2 / 3
Completeness	It clearly states the 'what' (generate and locate PowerPoint files) but provides no 'Use when...' or equivalent trigger guidance for the 'when', which per the judging guidelines caps completeness at 2.	2 / 3
Trigger Term Quality	Includes the relevant keyword 'PowerPoint files' but misses common variations users say (presentations, slides, .pptx, pptx) and leans on jargon ('shell_agent', 'nested workspace directories') that users would not naturally say.	2 / 3
Distinctiveness Conflict Risk	The shell_agent-mediated generation niche is fairly specific, but the generic 'PowerPoint files' phrasing could overlap a general presentation skill and the absence of explicit triggers leaves it somewhat indistinct.	2 / 3
	Total	8 / 12 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/SKILL.md
Commit: c5a9c4b

Reviewed: 2 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.