CtrlK
BlogDocsLog inGet started
Tessl Logo

sandbox-execution-fallback-238489

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

53

Quality

58%

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-execution-fallback-238489/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

50%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The skill body is well-structured around a clear write-execute-verify pattern with a real code example, but it is padded with redundant explanation and meta-commentary while its core instructions remain pseudocode rather than executable tool calls. Tightening the prose and making the steps concrete would raise every dimension.

Suggestions

Remove the 'Why This Works' and 'Self-Assessment' sections, which restate knowledge Claude already has and add no actionable value.

Replace the pseudocode Step 1/2 blocks ('Use write_file to create a script') with concrete, copy-paste-ready tool invocations matching the real reportlab example.

Strengthen Step 3 with an explicit validation checkpoint and a fix-and-retry loop (e.g., inspect exit code/stderr, fix the script, re-run) instead of the vague 'Check that the script executed successfully'.

DimensionReasoningScore

Conciseness

The core steps are efficient, but the 'Why This Works' section restates facts Claude already knows and the 'Self-Assessment' section is meta-commentary that earns no tokens. It is mostly efficient but padded and could be tightened, matching the score-2 anchor.

2 / 3

Actionability

A genuinely executable reportlab example is included, but the primary Step 1/2 instructions are pseudocode tool-call sketches ('Use write_file to create a script (e.g., script.py)') rather than concrete, copy-paste-ready invocations, fitting 'some concrete guidance but incomplete'.

2 / 3

Workflow Clarity

The write -> execute -> verify sequence is present with a troubleshooting section, but the verification step is vague ('Check that the script executed successfully') and there is no explicit validate-fix-retry feedback loop, so checkpoints are implicit.

2 / 3

Progressive Disclosure

The body is organized into clear, navigable sections and is self-contained with no nested references, but inline meta-content like the 'Self-Assessment' section is material that should not be present at all, fitting 'some structure but content that should be separate is inline'.

2 / 3

Total

8

/

12

Passed

Description

67%

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 conveys both purpose and trigger using third-person voice, but relies on internal tool jargon rather than natural user keywords and offers only a narrow action list. It is solid but would benefit from more natural trigger phrasing and broader concrete actions.

Suggestions

Add natural-language trigger terms a user would actually say (e.g., 'Use when the code sandbox fails, times out, or lacks needed Python libraries') rather than only the internal tool name 'execute_code_sandbox'.

Broaden the action list beyond two steps to make the capability more concrete and distinguishable from general coding skills.

DimensionReasoningScore

Specificity

Names the domain ('Fallback pattern for when execute_code_sandbox fails') and two concrete actions ('write script to file and execute directly with run_shell'), but the action list is narrow rather than comprehensive. It does not reach the multiple-specific-actions level of the score-3 anchor.

2 / 3

Completeness

It explicitly states what to do ('write script to file and execute directly with run_shell') and when to do it ('Fallback pattern for when execute_code_sandbox fails'), answering both what and when with an explicit trigger clause.

3 / 3

Trigger Term Quality

The trigger 'when execute_code_sandbox fails' is relevant, but the terms are internal tool names ('execute_code_sandbox', 'run_shell') rather than language a user would naturally say, so it lands at 'some relevant keywords but missing common variations'.

2 / 3

Distinctiveness Conflict Risk

The niche is tied to specific tool names, but as a general code-execution fallback it could still overlap with ordinary coding skills, matching 'somewhat specific but could still overlap'.

2 / 3

Total

9

/

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.