excel-heredoc-workaround

Create Excel files with openpyxl by falling back to run_shell with inline Python heredoc when execute_code_sandbox fails

Quality

72%

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/excel-heredoc-workaround/SKILL.md

Quality

Content

77%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is highly actionable with a clear, validated step-by-step workflow and executable examples. Its main weaknesses are redundant code blocks that bloat token usage and a long monolithic structure that could be split into referenced files.

Suggestions

Consolidate the repeated openpyxl workbook/setup blocks in Step 2 and the 'Example Complete Workflow' to avoid duplication and reduce tokens.

Move the 'Common Styling Patterns' and full example workflow into a referenced reference file (e.g., EXAMPLES.md) with a clear one-level link, keeping SKILL.md as a lean overview.

Dimension	Reasoning	Score
Conciseness	Mostly actionable code, but the near-identical openpyxl setup appears in both Step 2 and the 'Example Complete Workflow', and the styling-pattern snippets repeat header/fill idioms, so it could be tightened to remove redundancy.	2 / 3
Actionability	Fully executable, copy-paste-ready Python and bash heredocs plus concrete verification commands ('ls -lh *.xlsx', 'read_file ...'), matching the score-3 anchor for specific executable examples.	3 / 3
Workflow Clarity	A clear four-step sequence (attempt sandbox -> heredoc fallback -> verify with ls -> read back) with explicit validation checkpoints and a troubleshooting section for error recovery.	3 / 3
Progressive Disclosure	Well-organized single-file sections, but at over 200 lines the styling patterns and example workflow are inline rather than split into referenced files, leaving room for clearer separation.	2 / 3
	Total	10 / 12 Passed

Description

67%

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, clearly naming the tooling and fallback mechanism. Its weaknesses are the absence of an explicit 'Use when...' trigger clause and limited keyword variation (no 'spreadsheet'/'xlsx').

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when creating .xlsx files, spreadsheets, or workbooks and execute_code_sandbox fails.'

Include natural keyword variations such as 'spreadsheet', 'xlsx', and 'workbook' alongside 'Excel files'.

Dimension	Reasoning	Score
Specificity	Quotes 'Create Excel files with openpyxl', 'falling back to run_shell with inline Python heredoc', and 'execute_code_sandbox fails' name multiple concrete, specific actions rather than vague language, matching the score-3 anchor.	3 / 3
Completeness	It clearly states what it does, but 'when execute_code_sandbox fails' is a failure condition rather than explicit user-facing 'Use when...' trigger guidance, so per the guideline when is only implied and completeness is capped at 2.	2 / 3
Trigger Term Quality	It includes 'Excel files' and 'openpyxl' but omits common natural variations like 'spreadsheet', 'xlsx', or 'workbook', so it has some relevant keywords but missing common variations.	2 / 3
Distinctiveness Conflict Risk	The niche — openpyxl execution via run_shell heredoc as a sandbox fallback — is distinctive and unlikely to trigger for the wrong skill.	3 / 3
	Total	10 / 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/excel-heredoc-workaround/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.