python-spreadsheet-debug

Systematic Python debugging workflow for spreadsheet tasks to isolate environment issues from script logic

Quality

61%

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/python-spreadsheet-debug/SKILL.md

Quality

Content

72%

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 and well-structured with executable examples throughout, but it loses points on conciseness due to explanatory padding and a non-essential Benefits section, and its workflow checkpoints are implicit rather than explicit gates.

Suggestions

Remove explanations of commands Claude already knows (e.g. the sentence after `python --version`) and drop the 'Benefits' section to tighten token usage.

Make validation checkpoints explicit gates in the steps, e.g. 'If the import checks fail, stop and resolve dependencies before continuing to Step 3.'

Fold the Common Issues table's error-recovery guidance into the relevant steps so the workflow itself contains the fix-and-retry loop rather than relegating it to a reference table.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands, but it explains commands Claude already understands ('This identifies whether Python is available and which version is being used') and closes with a padded 'Benefits' section of meta-commentary, so it is not fully lean.	2 / 3
Actionability	It provides fully executable, copy-paste-ready guidance: import probes via `python -c`, a complete `test_minimal.py` script, a one-line diagnostic, and a resolution table with specific commands, matching the level-3 anchor for fully executable code and commands.	3 / 3
Workflow Clarity	The four steps are clearly sequenced and the minimal test yields pass/fail feedback, but the validation checkpoints are prose-stated ('Once the minimal test passes') rather than explicit gates, and the error-recovery loop lives only in the supplementary table rather than in the numbered workflow.	2 / 3
Progressive Disclosure	This is a single-purpose, self-contained debugging skill with no need for external references and well-organized sections (Steps 1–4, Quick Diagnostic, Common Issues, When to Use), which per the scoring notes lets progressive disclosure score 3 on well-organized sections alone.	3 / 3
	Total	10 / 12 Passed

Description

50%

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 its purpose but uniformly lands at the mid-level because it omits an explicit use-when trigger and lacks broad natural keyword coverage. Adding a 'Use when...' clause with concrete user phrases would lift completeness and trigger_term_quality.

Suggestions

Append an explicit trigger clause, e.g. 'Use when a Python spreadsheet script fails with opaque errors, or when you see ModuleNotFoundError/ImportError from pandas, openpyxl, or xlrd.'

Broaden natural keywords to include library and error names users actually say (pandas, openpyxl, xlrd, ModuleNotFoundError, ImportError) rather than only 'Python' and 'spreadsheet'.

List one or two more concrete actions (e.g. 'verify imports, run a minimal repro, then execute the full script') to push specificity toward the level-3 anchor.

Dimension	Reasoning	Score
Specificity	Names the domain ('Python debugging workflow for spreadsheet tasks') and a concrete action ('isolate environment issues from script logic'), but does not enumerate multiple specific actions, so it stops short of the comprehensive level-3 anchor.	2 / 3
Completeness	It clearly states what the skill does but lacks any explicit 'Use when...' trigger guidance, which per the judging guidelines caps completeness at 2 ('Has what, but when is missing or only implied').	2 / 3
Trigger Term Quality	Includes relevant natural keywords ('Python', 'debugging', 'spreadsheet') but misses common user variations a person would actually say like 'pandas error', 'openpyxl', or 'ModuleNotFoundError', so coverage is partial rather than complete.	2 / 3
Distinctiveness Conflict Risk	The 'spreadsheet tasks' qualifier gives it a niche, but the broader 'Python debugging workflow' framing could overlap with general Python debugging skills, so it is only somewhat distinct.	2 / 3
	Total	8 / 12 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/python-spreadsheet-debug/SKILL.md
Commit: c5a9c4b

Reviewed: 2 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.