python-spreadsheet-debug

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

Quality

60%

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

67%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 delivers a clear, actionable diagnostic workflow with executable code and a useful troubleshooting table, but it is padded with redundant explanations and a repeat diagnostic command that hurt token efficiency.

Suggestions

Remove explanatory restatements that restate the obvious (e.g. 'This identifies whether Python is available and which version is being used.', the 'Purpose:' line, and the 'Benefits' section) to tighten conciseness.

Delete or fold the 'Quick Diagnostic Command' section into Step 4, since it merely re-runs commands already shown in Steps 1-2.

Add an explicit validation feedback loop note (e.g. 'If a step prints a ✗, resolve it via the table below before proceeding to the next step') to make the implicit checkpoint explicit.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient but retains several restated-the-obvious sentences ('This identifies whether Python is available…', 'Purpose: …'), a redundant 'Quick Diagnostic Command' that repeats prior steps, and a promotional 'Benefits' section, fitting anchor 3 rather than 4.	3 / 5
Actionability	Provides concrete, copy-paste-ready shell commands and a complete test_minimal.py script covering the common import/read/groupby cases, with only minor gaps (placeholder 'sample.xlsx' and column names, 'Replace library names based on your script's requirements'), matching anchor 4.	4 / 5
Workflow Clarity	A clear 4-step sequence (verify environment, test imports, minimal script, full script) with an implicit checkpoint ('Once the minimal test passes…') and a common-issues error-recovery table; no explicit validate->fix->retry loop, but the task is diagnostic (non-destructive) so the workflow-clarity cap does not apply — anchor 4.	4 / 5
Progressive Disclosure	Self-contained with well-organized section headers and easy navigation; no external bundle files are needed or referenced, but at ~100 lines it sits just above the simple-skill threshold, fitting anchor 4 rather than 5.	4 / 5
	Total	15 / 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 clearly states what the skill does and carves out a distinct niche, but it omits an explicit 'Use when...' trigger clause and lacks natural trigger synonyms, leaving it at mid-level scores across completeness and trigger quality.

Suggestions

Add an explicit trigger clause, e.g. 'Use when run_shell returns opaque errors on Python spreadsheet/data-processing scripts, or when a previously working pandas/openpyxl script suddenly fails.'

Include natural user-facing keywords and synonyms such as 'Excel', 'pandas', 'openpyxl', '.xlsx', and 'import errors' to improve trigger-term coverage.

Enumerate concrete actions (e.g. 'verifies the Python environment, tests library imports in isolation, runs a minimal reproduction script') to lift specificity above a single stated goal.

Dimension	Reasoning	Score
Specificity	Names the domain ('Python debugging workflow for spreadsheet tasks') and one concrete action ('isolate environment issues from script logic'), but does not enumerate several specific actions, matching anchor 3 rather than 4.	3 / 5
Completeness	Provides a clear 'what' (systematic debugging workflow to isolate environment vs. logic issues) but lacks any explicit 'Use when...' trigger clause, which per the guidelines caps completeness at 3.	3 / 5
Trigger Term Quality	Relevant keywords ('Python', 'debugging', 'spreadsheet') are present but common user phrasings and synonyms ('Excel', 'pandas', 'run_shell errors', '.xlsx') are missing, fitting anchor 3.	3 / 5
Distinctiveness Conflict Risk	The niche (Python spreadsheet debugging focused on environment/logic isolation) is mostly distinct with only minor overlap risk against general Python debugging skills, matching anchor 4 rather than 5 (no explicit triggers) or 3.	4 / 5
	Total	13 / 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/python-spreadsheet-debug/SKILL.md
Commit: 3827781

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