sandbox-file-discovery-and-validation

Use shell tools safely in sandboxed environments by discovering files from real workspace roots instead of assumed user folders, then explicitly verifying output artifacts after generation.

Quality

70%

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/sandbox-file-discovery-and-validation/SKILL.md

Quality

Content

81%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 highly actionable with a clear, validation-rich workflow and concrete commands throughout; its main weakness is length and redundancy across the workflow, reuse-patterns, decision-rules, and end-to-end example sections.

Suggestions

Consolidate 'Shell patterns to reuse', 'Practical decision rules', and 'Example end-to-end pattern' into the main workflow steps to remove restated commands and cut length.

Trim or move the 'When to use this' and 'Core principles' lists so the workflow begins sooner, since the description already covers motivation.

Consider a one-line quick-start sequence at the top so a returning Claude can skip the rationale.

Dimension	Reasoning	Score
Conciseness	Mostly efficient actionable content, but ~220 lines with redundant sections ('Shell patterns to reuse', 'Practical decision rules', 'Example end-to-end pattern') that restate commands already shown in the workflow.	3 / 5
Actionability	Copy-paste ready shell commands appear throughout (find, ls, test -f, test -s, mkdir -p, file), covering discovery, output creation, and validation cases specifically.	5 / 5
Workflow Clarity	A clear 7-step sequence with explicit validation checkpoints (steps 5 and 6) and a feedback emphasis — 'Never assume generation succeeded just because a command exited successfully' — plus an evidence-based reporting step.	5 / 5
Progressive Disclosure	Single self-contained file with no bundle files and well-organized section headers; redundant repeated-pattern sections prevent a top score.	4 / 5
	Total	17 / 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 states concrete capabilities clearly and occupies a distinct niche, but lacks an explicit 'when to use' trigger clause and natural-language trigger terms, capping completeness and trigger quality at the midpoint.

Suggestions

Add an explicit 'Use when ...' clause naming concrete triggers, e.g. 'Use when working in a sandboxed shell where ~/Desktop or ~/Documents may not exist or when task files must be located and output artifacts verified.'

Include natural synonyms and concrete artifacts users mention (e.g. 'find input files', 'locate spreadsheets', 'verify the .xlsx was created') to broaden trigger-term coverage.

Lead with the verb phrase of the core action before the rationale so the 'what' lands first and the 'when' follows as a separate sentence.

Dimension	Reasoning	Score
Specificity	Names the domain and several concrete actions — 'discovering files from real workspace roots' and 'explicitly verifying output artifacts after generation' — with only minor coverage gaps.	4 / 5
Completeness	The 'what' is clear, but there is no explicit 'Use when...' trigger clause, which caps completeness at 3 per the rubric guideline.	3 / 5
Trigger Term Quality	Relevant terms like 'sandboxed environments' and 'shell tools' appear but lean technical, missing common synonyms or file extensions users would naturally say.	3 / 5
Distinctiveness Conflict Risk	The sandbox/assumed-folder/verification niche is mostly distinct with only minor overlap risk against generic shell or file skills.	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/sandbox-file-discovery-and-validation/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.