CtrlK
BlogDocsLog inGet started
Tessl Logo

python-debug-execution

Debug Python scripts with proper error surfacing and working directory verification

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

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./benchmarks/gdpval/skills/python-debug-execution/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 content is highly actionable with executable code and a useful failure-pattern table, and its single-file structure is appropriately organized with no external references needed. The main weaknesses are repeated commands and over-explanation of basic shell mechanics, plus the absence of an explicit fix-retry feedback loop in the debugging workflow.

Suggestions

Remove the duplicate 'python3 script.py 2>&1 ; echo Exit code: $?' occurrences (define the command once and reference it), and trim the 'Why this works' bullets that re-explain basic shell redirection.

Turn the implicit 'Analyze Output' step into an explicit feedback loop, e.g. 'If exit code is non-zero or a traceback appears, fix the indicated issue and re-run until exit code is 0.'

Consider folding the diagnostic snippet and the complete workflow script into one canonical example to reduce redundancy.

DimensionReasoningScore

Conciseness

The body is mostly efficient, but the core bash command is repeated three times and 'Why this works' explains basic shell redirection (2>&1) that Claude already knows, so it could be tightened rather than padded.

3 / 5

Actionability

It provides fully executable, copy-paste-ready bash and Python snippets plus a complete runnable diagnostic script, and the failure-pattern table covers the common cases concretely.

5 / 5

Workflow Clarity

The three-step workflow (add diagnostics, execute, analyze) is clearly sequenced, but the analysis checkpoint is implicit and there is no explicit fix-and-retry feedback loop, which is the whole point of a debugging workflow.

3 / 5

Progressive Disclosure

No bundle files exist and none are needed; the single self-contained file is well-organized with clearly navigable sections and no nested references, satisfying the simple-skill exception for progressive disclosure.

5 / 5

Total

16

/

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 is clear and reasonably specific about what the skill does, but it omits any explicit 'when to use' trigger guidance and lacks keyword synonyms, which together cap completeness and trigger-term quality at the midpoint. Adding a 'Use when...' clause with natural trigger phrases would lift the two lowest dimensions.

Suggestions

Add an explicit trigger clause, e.g. 'Use when a Python script fails silently, raises a traceback, or produces FileNotFoundError/ModuleNotFoundError in an automated or agent context.'

Include natural synonyms and file extensions users actually say, such as 'Python errors', 'traceback', 'script failing', and '.py'.

Tighten distinctiveness by naming the specific scenario (agent/CI execution) rather than generic Python debugging.

DimensionReasoningScore

Specificity

The description names the domain ('Python scripts') and two concrete actions ('error surfacing' and 'working directory verification'), matching the anchor for 1-2 concrete actions without comprehensive coverage.

3 / 5

Completeness

The 'what' is clear (debug Python scripts via error surfacing and working directory verification) but there is no 'Use when...' clause or equivalent trigger guidance, so per the rubric completeness is capped at 3.

3 / 5

Trigger Term Quality

It includes the natural phrase 'Debug Python scripts' but omits common variations and synonyms a user might say ('traceback', 'Python errors', 'script failing', '.py'), placing it at 'some relevant keywords but missing variations'.

3 / 5

Distinctiveness Conflict Risk

It targets a specific Python debugging niche with concrete technique cues, making it mostly distinct with only minor overlap risk against general debugging skills; it lacks the explicit trigger phrases needed for a 5.

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.