sandbox-fallback-python

Fallback to run_shell with embedded Python when execute_code_sandbox fails due to e2b unavailability

Quality

66%

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

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 content is highly actionable with copy-paste-ready fallback commands and a clear procedural sequence, well-structured for a simple single-purpose skill. Its main gaps are missing explicit validation/verification checkpoints and some redundancy between the procedure and the examples sections.

Suggestions

Add an explicit validation step after running the fallback, e.g. checking the run_shell exit code or confirming expected stdout, with a retry loop on failure.

Consolidate the 'Code Examples' section into the procedure steps or trim examples that merely repeat the procedural heredocs to reduce redundancy.

Provide a concrete mitigation for the noted output-truncation caveat (e.g. write large output to a file and read it back) rather than only flagging the limitation.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with executable heredoc examples and no padding about what Python is, but sections like 'Code Examples' repeat patterns already shown in the procedure and 'Best Practices' partly restate what the examples demonstrate, so it could be tightened to remove redundancy.	3 / 5
Actionability	The content provides fully executable, copy-paste-ready bash heredoc commands covering the common cases (simple execution, dependency install, file I/O, JSON processing), with specific examples and concrete flags like 'pip install -q' and "<< 'EOF'".	5 / 5
Workflow Clarity	Steps are clearly sequenced (detect failure, switch to run_shell, install deps, handle file I/O), but there are no validation checkpoints confirming the fallback actually succeeded beyond a vague 'Verify execution' bullet, and the 'Caveats' note output may be truncated without a mitigation, matching the 'steps listed but validation gaps' anchor.	3 / 5
Progressive Disclosure	The skill is a short, single-purpose fallback with no bundle files; it is well-organized into clearly headed sections (When to Use, Fallback Procedure, Code Examples, Best Practices, Caveats, When NOT to Use) with no nested references, satisfying the simple-skill exception for a top score.	5 / 5
	Total	16 / 20 Passed

Description

66%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 clear, specific, and well-scoped to a distinct trigger condition, with both a 'what' and a 'when' clause present. Its main weakness is narrow trigger-term coverage and limited breadth of stated capabilities.

Suggestions

Broaden trigger terms to include natural phrasings users might say, e.g. 'sandbox failed', 'code execution error', or 'python fallback'.

Acknowledge additional fallback capabilities (e.g. installing dependencies, file I/O) in the description to improve capability comprehensiveness.

Dimension	Reasoning	Score
Specificity	The description names a concrete action ('Fallback to run_shell with embedded Python') and a concrete trigger condition ('when execute_code_sandbox fails due to e2b unavailability'), but it lists only one fallback mechanism rather than a comprehensive set of capabilities, matching the 'names domain and 1-2 concrete actions' anchor.	3 / 5
Completeness	It explicitly answers both 'what' (fallback to run_shell with embedded Python) and 'when' (when execute_code_sandbox fails due to e2b unavailability); the 'when' is concrete but narrow and lacks broader trigger phrasing, so it is a clear what+when that could be more explicit.	4 / 5
Trigger Term Quality	It surfaces relevant technical terms ('execute_code_sandbox', 'run_shell', 'e2b unavailability') that a user encountering the failure would reference, but it omits common natural-language variations (e.g. 'sandbox failed', 'code execution error', 'python fallback') and synonyms, landing at 'some relevant keywords but missing common variations'.	3 / 5
Distinctiveness Conflict Risk	The trigger is narrowly scoped to a specific tool failure ('execute_code_sandbox fails due to e2b unavailability') with a distinct fallback action, giving it a clear niche with minimal conflict risk against other skills.	5 / 5
	Total	15 / 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-fallback-python/SKILL.md
Commit: 3827781

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