CtrlK
BlogDocsLog inGet started
Tessl Logo

python-debug-pattern

Debug Python script execution failures by capturing full output with exit codes and verifying working directory before file operations

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

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./benchmarks/gdpval/skills/python-debug-pattern/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

100%

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 lean, highly actionable single-purpose skill: executable commands and complete Python examples, a clear numbered workflow with a checklist, and a useful symptom/table mapping that ties the pattern to real failure modes. It assumes Claude's competence and adds only non-obvious value.

DimensionReasoningScore

Conciseness

The body is lean: it avoids explaining basic concepts Claude already knows, uses brief 'Why this works' bullets that earn their tokens, and presents commands and code directly; not level 2 because there is no unnecessary padding to tighten away.

3 / 3

Actionability

Provides a fully executable bash command pattern (`python3 script.py 2>&1 ; echo Exit code: $?`) and complete, copy-paste-ready Python snippets with absolute-path logging; not level 2 because the guidance is concrete and complete rather than pseudocode or missing key details.

3 / 3

Workflow Clarity

Sequences the techniques as numbered steps, reinforces them with a Quick Checklist, and the pattern itself acts as a validation checkpoint that surfaces errors; for a single-purpose diagnostic skill the workflow is unambiguous. Not capped at 2 because the skill surfaces rather than performs destructive/batch operations.

3 / 3

Progressive Disclosure

A single-file, well-organized skill with clearly labeled sections and no need for external references; per the rubric's scoring notes, simple skills under 50 lines with well-organized sections can score 3 without external file references.

3 / 3

Total

12

/

12

Passed

Description

60%

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 and action-oriented, naming concrete debugging techniques, but omits an explicit 'Use when...' trigger clause and has only partial coverage of natural trigger terms. This caps both completeness and distinctiveness at 2.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when a Python script fails with an opaque error, a file operation fails unexpectedly, or a script works locally but fails in CI/CD.'

Broaden trigger terms to include natural variations users would say: 'Python error', 'traceback', 'debug Python script', 'script won't run'.

Sharpen distinctiveness by scoping to script-execution debugging rather than general debugging, to reduce overlap with generic error-handling skills.

DimensionReasoningScore

Specificity

Names multiple concrete actions — 'capturing full output with exit codes' and 'verifying working directory before file operations' — rather than abstract language, matching the level-3 anchor of several specific actions; not level 2 because it lists more than one domain action.

3 / 3

Completeness

It clearly answers 'what' the skill does, but there is no 'Use when...' clause or equivalent explicit trigger guidance, which per the judging guidelines caps completeness at 2; not level 3 for the missing explicit 'when'.

2 / 3

Trigger Term Quality

Contains relevant keywords a user might say ('Python script execution failures', 'exit codes', 'working directory') but lacks common variations like 'traceback', 'Python error', or 'debug script'; not level 3 because coverage of natural terms is incomplete.

2 / 3

Distinctiveness Conflict Risk

The Python-script-debugging niche is somewhat specific, but 'debug script execution failures' is broad enough to overlap with general debugging or error-handling skills; not level 1 because it names Python and specific failure modes, not level 3 because it could still conflict with broader debugging skills.

2 / 3

Total

9

/

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.