fallback-script-execution

Two-step script execution workflow for debugging when shell_agent and execute_code_sandbox consistently fail

Quality

68%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./benchmarks/gdpval/skills/fallback-script-execution/SKILL.md

Quality

Content

75%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 executable code and concrete commands, and the two-step workflow is clearly sequenced with recovery guidance. Its main weakness is conciseness: the pattern is restated multiple times and several tip sections offer obvious advice Claude already knows.

Suggestions

Collapse the 'Core Pattern', 'Step-by-Step', and 'Example' sections so the two-step workflow is stated once, keeping the worked example as the single illustration.

Remove or drastically shorten the 'Best Practices' and 'Debugging Tips' bullets that restate obvious Python practices (try/except, print statements, descriptive comments).

Add an explicit verify step after run_shell (e.g. check exit code / output for SUCCESS marker) to turn the implicit feedback loop into a clear validation checkpoint.

Dimension	Reasoning	Score
Conciseness	The core steps and worked example are efficient and earn their place, but the pattern is restated three times (Core Pattern, Step-by-Step, Example) and the 'Best Practices' and 'Debugging Tips' sections state obvious advice Claude already knows, so it could be tightened.	3 / 5
Actionability	Provides copy-paste-ready write_file and run_shell invocations plus a fully executable worked pandas example with try/except and exit codes, and concrete debugging commands (which python, ls -la, /usr/bin/python).	5 / 5
Workflow Clarity	The two-step sequence is clearly ordered with an error-recovery feedback loop (inspect script, modify and re-run) and an escalation path, though there is no formal validate-before-proceeding checkpoint.	4 / 5
Progressive Disclosure	The body is well-organized with clear section headers and is self-contained with no nested references (no bundle files exist), but at ~120 lines it is somewhat monolithic and the auxiliary tip sections could be trimmed rather than split.	4 / 5
	Total	16 / 20 Passed

Description

62%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 clearly conveys a distinct fallback debugging niche and answers both what and when, but it leans on tool-name jargon for triggers and leaves the core mechanism (write_file + run_shell) unstated, limiting specificity and natural trigger coverage.

Suggestions

Name the concrete mechanism in the description, e.g. 'Write scripts to a file with write_file and execute them with run_shell' to lift specificity.

Add natural trigger phrases a user would say ('when scripts keep failing', 'script execution errors', 'debug failed code runs') alongside the tool names.

Consider an explicit 'Use when ...' clause to make the trigger guidance unambiguous.

Dimension	Reasoning	Score
Specificity	Names the domain ('Two-step script execution workflow') and implies two concrete actions (write script, execute), but does not enumerate the specific steps or tools used, so coverage is not comprehensive.	3 / 5
Completeness	Explicitly answers both 'what' (two-step script execution workflow) and 'when' (for debugging when the named tools consistently fail), but the 'what' is slightly abstract and could state the actual write_file + run_shell mechanism.	4 / 5
Trigger Term Quality	Includes a relevant natural term ('debugging') and 'script execution', but the primary triggers are tool-jargon ('shell_agent', 'execute_code_sandbox') and common synonyms or variations a user would naturally say are missing.	3 / 5
Distinctiveness Conflict Risk	The trigger tied to specific tool failure modes carves a distinct fallback niche with low conflict risk, though 'script execution workflow' is broad enough to overlap slightly with general scripting skills.	4 / 5
	Total	14 / 20 Passed

Validation

100%

Warnings & errors only

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: HKUDS/OpenSpace
Path: benchmarks/gdpval/skills/fallback-script-execution/SKILL.md
Commit: 3827781

Reviewed: 5 days ago

Table of Contents

Discovery Implementation Validation

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.