CtrlK
BlogDocsLog inGet started
Tessl Logo

fallback-code-execution

Fallback workflow for running code via file write and shell when sandbox execution fails

57

Quality

66%

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

Quality

Content

78%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 a compact, well-structured fallback workflow with concrete tool calls and a verification step. It is largely executable and well-organized, with only minor conciseness and example-completeness gaps.

Suggestions

Replace the schematic '# ... script logic ...' placeholder in the write_file example with a minimal complete script so the example is copy-paste ready.

Tighten the Overview and Best Practices to remove guidance Claude already knows (e.g., 'Ensure the script includes necessary error handling').

Make the error path in Step 3 an explicit feedback loop: on non-zero exit, fix the script and re-run until exit code 0.

DimensionReasoningScore

Conciseness

The body is well-organized and mostly efficient with concrete tool calls, but contains minor over-explanation such as 'This skill defines a robust workaround' and 'Ensure the script includes necessary error handling' that could be trimmed.

4 / 5

Actionability

Provides concrete tool names, file paths, shell commands, and YAML examples for each step; the code examples are slightly schematic ('# ... script logic ...') rather than fully copy-paste, leaving a minor gap.

4 / 5

Workflow Clarity

A clear three-step sequence is present with Step 3 acting as a verification checkpoint (exit code, output, stderr inspection) and error-handling guidance, though it stops short of a full validate->fix->retry feedback loop.

4 / 5

Progressive Disclosure

A single self-contained file under 50 lines with clean section headers and no external references needed; per the simple-skill guidance this is appropriately structured and navigable.

5 / 5

Total

17

/

20

Passed

Description

53%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 conveys a clear purpose and a narrow trigger condition, but lacks an explicit 'Use when' trigger clause and richer natural-language keywords. It is serviceable but not comprehensive.

Suggestions

Add an explicit 'Use when ...' clause naming concrete trigger phrases (e.g., 'Use when execute_code_sandbox repeatedly fails with unknown or transient errors').

Expand natural trigger terms to include synonyms users would actually say, such as 'code won't run', 'sandbox tool broken', or 'execution keeps failing'.

List a couple more concrete actions (e.g., 'write script to file, run via shell, capture stdout/stderr') to raise specificity.

DimensionReasoningScore

Specificity

Names the domain (running code) and two concrete actions ('file write and shell'), but the action list is brief rather than comprehensive, fitting the 1-2 concrete actions anchor.

3 / 5

Completeness

There is a clear 'what' (run code via file write and shell) and an implied 'when' (when sandbox execution fails), but no explicit 'Use when...' trigger clause, which caps completeness at 3 per the guidelines.

3 / 5

Trigger Term Quality

'sandbox execution fails' is a relevant keyword, but common natural phrases users would say ('code won't run', 'execution tool broken') and synonyms are missing.

3 / 5

Distinctiveness Conflict Risk

The fallback-on-sandbox-failure niche is fairly distinct with minimal overlap risk against other skills; only minor broadness keeps it from a 5.

4 / 5

Total

13

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

referenced_paths_exist

Referenced path issues: 2 missing

Warning

Total

15

/

16

Passed

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.