CtrlK
BlogDocsLog inGet started
Tessl Logo

shell-python-fallback

Use run_shell with embedded Python heredoc as reliable fallback when code execution tools fail

56

Quality

63%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./benchmarks/gdpval/skills/shell-python-fallback/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

72%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 skill is highly actionable with executable, copy-paste-ready heredoc examples and clean organization, but it over-explains shell basics Claude already knows and lacks a concrete validation/feedback loop for verifying script execution. Tightening the prose and adding an explicit check-retry step would lift the weaker dimensions.

Suggestions

Trim 'Why This Works' and obvious troubleshooting rows (e.g. 'Ensure python3 is available') to remove content Claude already knows.

Replace the vague 'parse stdout to verify success' with a concrete validation step, e.g. check the exit code and retry with a fix loop on failure.

Add an explicit error-handling example using try/except with a non-zero exit code so success/failure is unambiguous.

DimensionReasoningScore

Conciseness

Mostly efficient with concrete examples, but 'Why This Works' explains shell behavior Claude already knows and parts of the troubleshooting table state the obvious ('Ensure python3 is available').

3 / 5

Actionability

Provides copy-paste-ready heredoc examples for PDF generation and data processing, plus concrete step-by-step instructions covering the common cases.

5 / 5

Workflow Clarity

Steps are clearly numbered with a trigger condition (2+ failures), but the output-verification step ('parse stdout to verify success') is vague with no concrete validation command or fix-retry feedback loop.

3 / 5

Progressive Disclosure

A single self-contained SKILL.md with no bundle files, organized into clear sections (When to Use, Pattern, Steps, Examples, Best Practices, Troubleshooting); well-structured and easy to navigate.

5 / 5

Total

16

/

20

Passed

Description

55%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 concrete and identifies a specific fallback niche, but it leans on technical jargon rather than natural user trigger phrases and offers only one narrow 'when' condition. Rewording to surface common natural-language triggers would raise trigger term quality and completeness.

Suggestions

Add natural-language trigger phrases users actually say, e.g. 'Use when the code sandbox keeps returning unknown errors or when you need a reliable way to run Python scripts.'

State the 'when' more explicitly and broadly rather than a single condition, so Claude knows the full set of triggering situations.

Keep the third-person action voice but trade jargon ('embedded Python heredoc') for plainer phrasing while preserving specificity.

DimensionReasoningScore

Specificity

Names the tool and mechanism ('run_shell with embedded Python heredoc') plus a concrete purpose ('reliable fallback'), but lists only one primary action rather than several specific actions.

3 / 5

Completeness

Clearly states what to do ('Use run_shell with embedded Python heredoc as reliable fallback') and gives a when condition ('when code execution tools fail'), though the trigger is a single narrow case.

4 / 5

Trigger Term Quality

Terms like 'code execution tools fail', 'run_shell', and 'Python heredoc' are technical jargon; users would not naturally say 'embedded Python heredoc', and common natural trigger phrases are missing.

2 / 5

Distinctiveness Conflict Risk

Targets a distinct niche (heredoc fallback for failing code execution tools) with only minor overlap risk against general shell-execution skills.

4 / 5

Total

13

/

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.