CtrlK
BlogDocsLog inGet started
Tessl Logo

code-exec-fallback-266cba

Fallback workflow for reliable code execution when sandbox fails repeatedly

67

Quality

80%

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/code-exec-fallback-266cba/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

85%

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 a clear, validated workflow and clean section organization; the main weakness is redundancy between the step-by-step instructions and the 'Complete Example' section.

Suggestions

Collapse the 'Complete Example' section or convert it to a single end-to-end script reference, since it duplicates the write_file and run_shell calls from the workflow steps.

Make the post-verification feedback loop explicit, e.g. 'If Step 4 reports an error, fix the script and re-run from Step 2.'

DimensionReasoningScore

Conciseness

The body is mostly efficient and avoids explaining concepts Claude already knows, but the 'Complete Example' section largely re-demonstrates the same write_file and run_shell calls already shown in the step-by-step workflow, which could be tightened.

2 / 3

Actionability

It provides concrete, copy-paste-ready calls with paths and timeouts (write_file, run_shell) and a fully executable Python example with try/except and sys.exit codes, matching the 'fully executable code/commands' anchor.

3 / 3

Workflow Clarity

The four-step sequence is clearly ordered with an explicit verification checkpoint (Step 4: 'Parse stdout/stderr ... to verify success or diagnose issues') plus built-in error handling, meeting the clear-sequence-with-explicit-validation bar.

3 / 3

Progressive Disclosure

This is a single-purpose skill with no external references needed; content is organized into clear, navigable sections (When to Use, Fallback Workflow, Best Practices, When NOT to Use) with no nested or monolithic structure.

3 / 3

Total

11

/

12

Passed

Description

75%

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, distinct, and answers both what and when with an explicit trigger, but it lacks multiple concrete action verbs and a richer set of trigger-term variations.

Suggestions

Add concrete action verbs to the description, e.g. 'Write scripts to a file and execute them via shell' so it lists multiple specific actions.

Broaden trigger-term coverage with phrasing users actually say, e.g. 'sandbox keeps timing out', 'code execution keeps failing', or 'execute_code_sandbox errors'.

Consider an explicit 'Use when ...' clause to make the trigger guidance unmistakable rather than embedded in the purpose statement.

DimensionReasoningScore

Specificity

The phrase 'Fallback workflow for reliable code execution' names the domain and an action but does not list multiple specific concrete actions like the anchor-3 example; it stays at the 'names domain and some actions' level.

2 / 3

Completeness

It states what it does ('Fallback workflow for reliable code execution') and gives an explicit trigger clause ('when sandbox fails repeatedly'), answering both what and when with explicit trigger guidance.

3 / 3

Trigger Term Quality

Terms like 'code execution', 'sandbox fails repeatedly' are natural for a technical user in this context, but coverage is thin with few common variations, matching the 'some relevant keywords but missing common variations' anchor.

2 / 3

Distinctiveness Conflict Risk

The narrow niche of a sandbox-failure fallback with a distinct trigger ('when sandbox fails repeatedly') makes it unlikely to fire for unrelated skills, matching the clear-niche anchor.

3 / 3

Total

10

/

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.