CtrlK
BlogDocsLog inGet started
Tessl Logo

spreadsheet-python-file-exec

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

52

Quality

57%

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

Quality

Content

61%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 actionable with solid executable examples and clear structure, but is somewhat verbose with redundant section framing and lacks an explicit validation checkpoint in the core workflow for what are effectively file-overwriting operations.

Suggestions

Add an explicit validation step to the recommended pattern (e.g. verify the output file opens or print a success check) so destructive overwrite operations have a checkpoint.

Consolidate the four examples — the repeated 'Write to file first, then execute' headers and '# Your operations here' placeholders add tokens without adding guidance.

Merge or trim the overlapping 'When to Use This Skill' and 'Why Direct Execution?' sections to reduce redundancy.

DimensionReasoningScore

Conciseness

Content is mostly efficient and the shell_agent heredoc rationale is non-obvious and valuable, but the 'When to Use' and 'Why Direct Execution?' sections overlap, the 'Write to file first, then execute' header is repeated across four examples, and some boilerplate (e.g. placeholder '# Your operations here') could be trimmed.

3 / 5

Actionability

Provides concrete, mostly copy-paste-ready code in four executable Python examples plus a clear bash write-then-execute pattern; minor gaps are the '# ... operations ...' and 'pass' placeholders in early examples that keep it just short of fully ready.

4 / 5

Workflow Clarity

The two-step write-file-then-execute sequence is clear and Example 4 adds try/except error handling, but spreadsheet writes overwrite output files (a destructive/batch operation) and the main recommended pattern lacks an explicit output-validation checkpoint, capping workflow clarity at 3 per the rubric.

3 / 5

Progressive Disclosure

No bundle files exist and none are needed; the body is well-organized with clear section headers (When to Use, How to Use, Best Practices, Troubleshooting, Common Libraries), though it is a single ~200-line monolith with four examples that could be consolidated.

4 / 5

Total

14

/

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 specific and distinctive about its mechanism, but lacks an explicit 'Use when' trigger clause and natural user-facing keywords like 'Excel' or '.xlsx'. It conveys the what clearly while the when is only weakly implied.

Suggestions

Add an explicit 'Use when...' trigger clause, e.g. 'Use when performing multi-step spreadsheet operations with openpyxl or pandas, or when shell_agent heredoc execution fails.'

Include natural user-facing terms such as 'Excel', '.xlsx', and 'spreadsheets' so the description matches how users actually phrase requests.

Broaden the action list beyond a single mechanism to mention reading, writing, and formatting spreadsheets for more comprehensive coverage.

DimensionReasoningScore

Specificity

Names the domain ('spreadsheet operations') and a concrete action ('Execute Python scripts from files') plus the mechanism ('avoiding heredoc issues with shell_agent'), but coverage is limited to one core action rather than a comprehensive set of spreadsheet capabilities.

3 / 5

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 guidance, which caps completeness at 3 per the rubric guidelines.

3 / 5

Trigger Term Quality

Relevant keywords ('Python scripts', 'spreadsheet operations', 'heredoc', 'shell_agent') are present but technical-leaning, missing natural user-facing terms like 'Excel', '.xlsx', or 'spreadsheets' that a user would actually say.

3 / 5

Distinctiveness Conflict Risk

The niche is fairly distinct — file-based Python execution to avoid shell_agent heredoc failures — with minor overlap risk against general spreadsheet skills; it would not commonly trigger for the wrong skill.

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.