CtrlK
BlogDocsLog inGet started
Tessl Logo

ppt-workflow-location

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

54

Quality

60%

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

Quality

Content

67%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 is a well-structured, mostly actionable workflow with concrete shell commands and a verification step. Its main weaknesses are mild redundancy between the Pitfalls/Troubleshooting/Example sections and a Step 1 that delegates rather than providing executable steps.

Suggestions

Collapse the 'Example Workflow' into the relevant steps or the Troubleshooting table to remove duplicated commands and tighten conciseness.

Make Step 1 executable by giving the literal shell_agent invocation or task-delegation syntax instead of a descriptive prompt template.

Add an inline validate->fix->retry loop (e.g. 'if find returns nothing, broaden the search; if the file is 0 bytes, re-run the task') to lift workflow clarity to 5.

DimensionReasoningScore

Conciseness

The body is mostly efficient with concrete commands, but the 'Common Pitfalls' and 'Troubleshooting' sections restate guidance already covered in the steps (find before assuming location, check file size), so it could be tightened; it is not a 2 because the padding is limited rather than pervasive.

3 / 5

Actionability

Steps 2-4 give concrete, executable commands (find, cp/mv, ls, file) with realistic output examples; Step 1 is a descriptive delegation prompt rather than executable code, a minor gap that keeps it just below fully copy-paste ready.

4 / 5

Workflow Clarity

A clear four-step sequence includes an explicit verify step (file size/exists) and a troubleshooting table for error recovery, satisfying 'clear sequence with most checkpoints'; it is not a 5 because the error-recovery loop is a reference table rather than an inline validate->fix->retry loop.

4 / 5

Progressive Disclosure

The skill is self-contained with no bundle files and well-organized sections (When to Use, Steps, Pitfalls, Example, Troubleshooting); it is not a 5 because it runs slightly over the ~50-line simple-skill threshold and the Example Workflow duplicates commands from earlier sections.

4 / 5

Total

15

/

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 states what the skill does but omits any 'when to use it' trigger guidance and lacks synonyms or the .pptx extension. It is moderately specific and reasonably distinct, but its completeness is capped by the missing trigger clause.

Suggestions

Add a 'Use when...' clause naming natural triggers, e.g. 'Use when generating PowerPoint presentations via shell_agent or when a generated .pptx file needs to be located in the workspace.'

Include the .pptx extension and synonyms like 'presentations' or 'slides' so the description matches terms users actually say.

Mention a concrete extra capability (e.g. copying and verifying the located file) to lift specificity toward a 4.

DimensionReasoningScore

Specificity

Names the domain and two concrete actions ('Generate PowerPoint files' and 'locate them in nested workspace directories'), but does not enumerate further actions, matching the '1-2 concrete actions, not comprehensive' anchor.

3 / 5

Completeness

It states a clear 'what' but has no 'Use when...' or equivalent trigger clause, so per the missing-trigger cap it cannot exceed 3; it is not a 2 because the 'what' is explicit rather than vague.

3 / 5

Trigger Term Quality

'PowerPoint files' is a natural user term, but the description omits common synonyms and the .pptx extension and leans on the technical term 'shell_agent', fitting 'some relevant keywords but missing common variations'.

3 / 5

Distinctiveness Conflict Risk

The combination of PowerPoint generation and locating files in nested workspace directories is mostly distinct with only minor overlap with generic file-finding skills, matching 'mostly distinct; minor overlap risk'.

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.