sandbox-execution-fallback-238489

Fallback pattern for when execute_code_sandbox fails - write script to file and execute directly with run_shell

Quality

66%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Critical

Do not install without reviewing

Fix and improve this skill with Tessl

tessl review fix ./benchmarks/gdpval/skills/sandbox-execution-fallback-238489/SKILL.md

Quality

Content

71%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 well-structured and actionable with a solid executable example and a troubleshooting feedback loop. Its main weakness is padding — the 'Why This Works' and 'Self-Assessment' sections add tokens that do not aid execution.

Suggestions

Delete the 'Self-Assessment' section and trim 'Why This Works' to a single line or remove it entirely; this meta-commentary does not help execution.

Replace the descriptive step prose ('Use write_file to create a script') with literal tool invocations so the steps themselves are copy-paste-ready, mirroring the example block.

Tighten Step 3 verification into a concrete checkpoint: assert the expected output file exists and check the shell exit code before considering the task complete.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with actionable steps and a real code example, but the 'Why This Works' bullets and the 'Self-Assessment' section restate obvious benefits and meta-justify the skill rather than aiding execution, so it could be tightened.	3 / 5
Actionability	The example pattern provides copy-paste-ready reportlab code covering the common PDF case and troubleshooting gives concrete commands, but the step instructions themselves are prose ('Use write_file to create a script') rather than literal tool invocations, leaving a minor gap.	4 / 5
Workflow Clarity	A clear 3-step sequence (write → execute → verify) pairs with a troubleshooting feedback loop for run_shell failures; the verify step is present but light on what to check, keeping it below the explicit-validation anchor 5.	4 / 5
Progressive Disclosure	The skill is a single well-organized file with clear section headers and no nested references; per the simple-skill scoring note, a single-purpose file with no external-reference needs and clean navigation earns the top score.	5 / 5
	Total	16 / 20 Passed

Description

62%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 compact, third-person, and clearly pairs a trigger condition with two concrete fallback actions. It is distinct and unambiguous, but trigger-term coverage is somewhat technical and the 'when' could enumerate more failure scenarios.

Suggestions

Broaden trigger terms to natural user phrasing (e.g., 'sandbox errored', 'code won't run', 'library not available in sandbox') so users describe the problem in their own words.

Optionally enumerate a couple more concrete actions or failure modes (missing libraries, failed file I/O) to lift specificity and completeness toward the top anchors.

Dimension	Reasoning	Score
Specificity	Names the domain (sandbox execution fallback) and two concrete actions ('write script to file' and 'execute directly with run_shell'), but coverage is not comprehensive — fits the '1-2 concrete actions' anchor rather than the 'several specific actions' anchor above.	3 / 5
Completeness	It states both what ('write script to file and execute directly with run_shell') and an explicit when ('for when execute_code_sandbox fails'); the when is concrete but could list more triggers (missing libraries, failed I/O), so it sits below the fully-explicit anchor 5.	4 / 5
Trigger Term Quality	Relevant keywords are present ('execute_code_sandbox fails', 'run_shell') but they skew technical/internal and miss natural user variations like 'sandbox errored' or 'code won't run', so it does not reach the good-coverage anchor.	3 / 5
Distinctiveness Conflict Risk	The trigger 'when execute_code_sandbox fails' carves a clear, distinct niche with minimal conflict risk, though the broad domain of code execution leaves minor overlap with general code-running 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-execution-fallback-238489/SKILL.md
Commit: 3827781

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