CtrlK
BlogDocsLog inGet started
Tessl Logo

sandbox-fallback-execution-048d5a

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

65

Quality

78%

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

82%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 fully executable examples and a clear step sequence, well suited to a simple single-purpose skill. Its weak spots are mild redundancy between the steps and the Complete Example, and an implicit rather than explicit error-recovery loop.

Suggestions

Remove or trim the 'Complete Example' section since it duplicates the Step 1-2 pattern already shown, to tighten conciseness.

Add an explicit feedback loop in Step 3 (e.g., 'If errors appear in stderr, fix the script and re-run python3 ... until it executes cleanly') to strengthen workflow clarity.

Consider moving the 'Common e2b Errors That Trigger This Fallback' list into a short reference note or trimming it, since it mildly duplicates the description's trigger condition.

DimensionReasoningScore

Conciseness

The body is mostly efficient with no concept-padding Claude already knows, but the 'Complete Example' duplicates the Step 1-2 pattern and the Tips section partially restates the steps, so not every token earns its place.

4 / 5

Actionability

It provides copy-paste-ready, fully executable tool invocations (write_file with path/content, run_shell with explicit python3 command and timeout) plus a complete runnable pandas example, covering the common case.

5 / 5

Workflow Clarity

A clear three-step sequence (write, execute, verify) includes an explicit verification checkpoint in Step 3, but the error-recovery feedback loop (validate -> fix -> retry) is only implicit rather than spelled out.

4 / 5

Progressive Disclosure

No bundle files exist and the skill is well organized into clear navigable sections, but at ~92 lines it exceeds the simple-skill threshold and contains minor duplication (Complete Example rehashing the steps) rather than pristine content placement.

4 / 5

Total

17

/

20

Passed

Description

73%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 concise and specific, clearly conveying a narrow niche (sandbox-failure fallback) with explicit what-and-when guidance. Its main weakness is limited action coverage and a single-condition trigger rather than broader trigger phrasing.

DimensionReasoningScore

Specificity

Names the domain (sandbox fallback) and one concrete action (execute Python code) but is not comprehensive, matching the 'Names domain and 1-2 concrete actions' anchor; it lists only a single action so it does not reach 'several specific actions'.

3 / 5

Completeness

It states both what ('Fallback method to execute Python code') and when ('when execute_code_sandbox fails with e2b errors'), but the 'when' is a single condition rather than multiple concrete trigger phrases, fitting the 'both present, when could be more explicit' anchor.

4 / 5

Trigger Term Quality

'execute_code_sandbox fails with e2b errors' are natural terms a user would say when hitting this failure, giving good keyword coverage, but coverage is narrow with no synonyms or variations so it falls short of comprehensive.

4 / 5

Distinctiveness Conflict Risk

The trigger is tied to a specific named tool and a specific error type, creating a clear narrow niche with minimal conflict risk against unrelated skills.

5 / 5

Total

16

/

20

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.