spreadsheet-python-file-exec

Execute Python scripts from files for reliable spreadsheet operations, avoiding heredoc issues with shell_agent

Quality

57%

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

Quality

Content

65%

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 strong executable examples and a clear core pattern, but it is somewhat verbose, lacks explicit verification checkpoints for risky writes, and keeps all examples inline in a single long file.

Suggestions

Add an explicit verify step to the recommended workflow (e.g. 'Verify output.xlsx exists and opens before reporting success') to lift workflow clarity.

Trim the overlapping 'When to Use'/'Why Direct Execution?' rationale and the Common Libraries table, which restates knowledge Claude already has.

Move the longer worked examples (Examples 2–4) into a referenced examples file to reduce SKILL.md length and improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	Most content is useful code, but the 'When to Use' and 'Why Direct Execution?' sections overlap, and the Common Libraries table explains library purposes Claude already knows, fitting the 'mostly efficient but includes some unnecessary explanation or could be tightened' anchor rather than the lean level 3.	2 / 3
Actionability	The skill provides multiple complete, executable Python examples plus concrete bash write-then-execute patterns that are copy-paste ready, matching the 'fully executable code/commands; specific examples' anchor.	3 / 3
Workflow Clarity	The recommended write-to-file-then-execute sequence is clear and an error-handling example exists, but there is no explicit validation/verification checkpoint before destructive spreadsheet writes, which per the scoring notes caps workflow clarity at 2.	2 / 3
Progressive Disclosure	The body is well-sectioned but is a single monolithic file over 50 lines with all examples inline and no external references, fitting the 'some structure but content that should be separate is inline' anchor rather than the cleanly split level 3.	2 / 3
	Total	9 / 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 conveys a clear purpose and a concrete mechanism, but lacks an explicit 'Use when' trigger and relies on tool-internal jargon rather than natural user terms. It is competent but not exemplary.

Suggestions

Add an explicit 'Use when...' clause listing natural triggers, e.g. 'Use when reading, writing, or formatting Excel/spreadsheet files with openpyxl or pandas.'

Replace tool-internal phrasing ('heredoc issues with shell_agent') with user-facing terms like 'Excel', 'xlsx', and 'spreadsheets' to improve trigger term quality.

Enumerate concrete actions (read, write, format, transform) to lift specificity from 'some actions' to a comprehensive list.

Dimension	Reasoning	Score
Specificity	It names a concrete action ('Execute Python scripts from files') and domain ('spreadsheet operations'), but does not enumerate the range of spreadsheet actions, so it matches the 'names domain and some actions, but not comprehensive' anchor rather than the multi-action level 3.	2 / 3
Completeness	The 'what' is clear ('Execute Python scripts from files for reliable spreadsheet operations'), but there is no 'Use when...' clause or equivalent explicit trigger, which per the judging guidelines caps completeness at 2.	2 / 3
Trigger Term Quality	'spreadsheet operations' and 'Python scripts' are relevant, but common user variations like 'Excel', 'xlsx', or 'spreadsheets' are missing, and 'heredoc issues with shell_agent' is internal tool jargon users would not naturally say, fitting the 'some relevant keywords but missing common variations' anchor.	2 / 3
Distinctiveness Conflict Risk	The file-based Python execution niche is somewhat specific, but 'spreadsheet operations' and 'Python scripts' could still overlap with general spreadsheet or code-execution skills, matching the 'somewhat specific but could still overlap' anchor rather than the clearly distinct level 3.	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/spreadsheet-direct-python-enhanced/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.