CtrlK
BlogDocsLog inGet started
Tessl Logo

sandbox-fallback-execution-048d5a

Fallback method to execute Python code when execute_code_sandbox fails with e2b errors

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

Critical

Do not install without reviewing

Fix and improve this skill with Tessl

tessl review fix ./benchmarks/gdpval/skills/sandbox-fallback-execution-048d5a/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

70%

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 concrete, executable code and a clear three-step sequence, and is well-organized for a simple skill. Its main weakness is the absence of an explicit validation/retry feedback loop in the verification step, and some redundancy across the triggering-condition sections.

Suggestions

Add an explicit validation checkpoint in Step 3 (e.g., 'If run_shell returns a non-zero exit code or traceback, read stderr, fix the script, and re-run') to create a clear fix-and-retry loop.

Consolidate the repeated triggering-condition material across 'When to Use', 'Common e2b Errors', and 'When NOT to Use' to reduce redundancy and tighten token use.

State the expected success signal concretely (e.g., exit code 0 and the 'File created successfully' print) so verification is unambiguous.

DimensionReasoningScore

Conciseness

The body is mostly efficient with concrete code blocks and tight tips, but it restates the triggering condition across multiple sections ('When to Use', 'Common e2b Errors', 'When NOT to Use') and includes a large repeated complete example that overlaps the step examples, fitting 'mostly efficient but could be tightened'.

2 / 3

Actionability

It provides fully executable, copy-paste-ready guidance: explicit write_file and run_shell invocations with absolute paths, a complete runnable pandas example, and concrete timeout values, matching the 'fully executable code/commands; copy-paste ready' anchor.

3 / 3

Workflow Clarity

The three steps are clearly sequenced, but Step 3 (verify output) only says to check stdout/stderr without an explicit validation checkpoint or a fix-and-retry feedback loop for a batch/execution operation, which the rubric notes should cap workflow clarity at 2.

2 / 3

Progressive Disclosure

This is a simple, single-purpose skill under 50 lines of guidance with no external bundle files; content is organized into clearly labeled sections (When to Use, Steps, Example, Tips, Errors, When NOT to Use), which the simple-skills note allows to score 3.

3 / 3

Total

10

/

12

Passed

Description

50%

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 the purpose and triggering condition but is terse and lacks an explicit 'Use when' trigger clause plus the multi-action comprehensiveness of top-tier examples. It is third-person and free of fluff, but sits at the mid-band across most dimensions.

Suggestions

Add an explicit 'Use when ...' clause naming natural user phrasing (e.g., 'Use when execute_code_sandbox returns e2b errors after retries and sandbox isolation is not required').

List the concrete actions performed (write script to file, run via python3, verify output) so specificity reaches the multi-action bar.

Include common natural trigger variations such as 'e2b sandbox errors', 'sandbox execution failed', or 'code won't run in sandbox'.

DimensionReasoningScore

Specificity

The description names a concrete action ('execute Python code') and a named failure mode ('execute_code_sandbox fails with e2b errors'), but it does not list multiple specific concrete actions—it describes one fallback rather than enumerating several, matching the 'names domain and some actions, but not comprehensive' anchor.

2 / 3

Completeness

It states what the skill does (fallback to execute Python code) and implies when (when execute_code_sandbox fails with e2b errors), but it lacks an explicit 'Use when...' trigger clause; the guideline caps completeness at 2 for a missing explicit trigger.

2 / 3

Trigger Term Quality

It references concrete technical terms a user would mention ('execute_code_sandbox', 'e2b errors', 'Python code'), but lacks common natural variations or phrasing a user would typically say, fitting 'some relevant keywords but missing common variations'.

2 / 3

Distinctiveness Conflict Risk

The trigger is fairly specific to the e2b/execute_code_sandbox context, reducing broad conflicts, but a generic 'execute Python code' fallback could still overlap with other code-execution skills, matching 'somewhat specific but could still overlap'.

2 / 3

Total

8

/

12

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.