execute-code-fallback

Fallback from execute_code_sandbox to run_shell when e2b sandbox is unavailable

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

Quality

Content

75%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 executable commands and a clear sequenced workflow, but it is padded by duplicated examples (the pandas CSV and heredoc patterns each appear multiple times) and a redundant Quick Reference table that could be consolidated.

Suggestions

Remove the standalone 'Complete Example' section (or the Step 3/4 examples) since the pandas CSV use case is already shown verbatim earlier, eliminating the largest duplication.

Replace the generic 'Verify output and handle errors' checkpoint with an explicit feedback loop, e.g., re-run with adjusted code when run_shell returns a non-zero exit code.

Trim the Quick Reference table or merge it into the steps, since its rows repeat the same run_shell patterns already demonstrated above.

Dimension	Reasoning	Score
Conciseness	The body is code-forward and avoids explaining basic concepts Claude already knows, but the pandas CSV example is repeated in Steps 3, 4, and the Complete Example, the heredoc pattern appears twice, and the Quick Reference table rehashes the same commands; deduplicating these would tighten it notably.	3 / 5
Actionability	It provides fully executable, copy-paste-ready run_shell invocations covering the common cases (simple calc, install+run, multi-line heredoc, file I/O) plus a task-to-command mapping table, matching the top anchor.	5 / 5
Workflow Clarity	A clear 4-step sequence (Detect, Switch, Install, Heredoc) is paired with a Recovery Checklist and a verify-output consideration, but validation is generic ('Verify output and handle errors') without an explicit validate-then-retry feedback loop, leaving minor checkpoint gaps.	4 / 5
Progressive Disclosure	No bundle files exist and the skill is self-contained with well-organized sections and no nested references, but at over 50 lines with duplicated example content the organization has minor gaps rather than the lean, well-split structure of a 5.	4 / 5
	Total	16 / 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 is specific and distinct with an explicit what-and-when structure, but its trigger terms lean heavily on internal tool jargon rather than natural user language and enumerate only a single failure condition.

Suggestions

Reword trigger terms toward natural user phrasing (e.g., 'when the code execution sandbox is down or returns connection errors') instead of relying on internal tool names like 'e2b'.

Broaden the 'when' clause to list the failure signals the body already enumerates (e2b errors, sandbox-unavailable messages, connection timeouts) so the trigger coverage is comprehensive.

Add 1-2 more concrete actions (e.g., 'install missing packages, then run embedded Python via run_shell') to lift specificity toward comprehensive coverage.

Dimension	Reasoning	Score
Specificity	Names two concrete tools ('execute_code_sandbox', 'run_shell') and one concrete action ('Fallback'), matching the anchor for 1-2 concrete actions without comprehensive coverage; not a 4 because it lists only a single fallback action rather than several.	3 / 5
Completeness	It explicitly answers both what ('Fallback from execute_code_sandbox to run_shell') and when ('when e2b sandbox is unavailable'), but the trigger is a single narrow condition rather than the comprehensive set of trigger phrases that would warrant a 5.	4 / 5
Trigger Term Quality	The bulk is technical jargon a user would not naturally say ('execute_code_sandbox', 'run_shell', 'e2b sandbox'), with only 'sandbox is unavailable' as a quasi-natural phrase, placing it noticeably below the midpoint rather than at the jargon-only floor of 1.	2 / 5
Distinctiveness Conflict Risk	It occupies a clear, narrow niche (e2b sandbox unavailability fallback) with distinct triggers and minimal overlap risk with other skills, matching the top anchor.	5 / 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/execute-code-fallback/SKILL.md
Commit: 3827781

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