excel-heredoc-fallback

Create Excel files with openpyxl by falling back to shell-based Python heredoc when sandbox execution fails

Quality

67%

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-fallback/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 strongly actionable with executable heredoc examples and a clear validate-then-verify workflow, but it is longer than necessary due to repeated code blocks and keeps all advanced material inline rather than using progressive disclosure.

Suggestions

De-duplicate the header/styling code that recurs across Step 3, Advanced Formatting, and the Complete Workflow; reference one canonical example.

Move the Advanced Formatting Examples and Troubleshooting/comparison tables into reference files under references/ and link to them one level deep.

Trim basic openpyxl explanations that assume Claude does not already know the library.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient code-driven guidance, but header/styling logic is repeated across Step 3, 'Advanced Formatting Examples', and the 'Example Complete Workflow', and several basic openpyxl concepts are spelled out, so it could be tightened; not 1 because it is not a wall of explanatory prose.	2 / 3
Actionability	The skill provides multiple complete, executable Python heredoc blocks plus concrete verification commands (e.g. 'python3 << EOF ...', 'ls -lh output.xlsx') that are copy-paste ready, matching the fully executable anchor; not 2 despite a small '[from openpyxl code here]' placeholder because the bulk is concrete.	3 / 3
Workflow Clarity	The process is clearly sequenced (attempt sandbox, detect failure, fall back, run shell, verify) with an explicit verification checkpoint in Step 5 and a detect-then-retry feedback loop, matching the clear-sequence-with-validation anchor; not 2 because checkpoints are explicit rather than implicit.	3 / 3
Progressive Disclosure	Sections are well organized, but with no references/, scripts/, or assets/ bundle the file is a monolithic ~249-line document that keeps advanced formatting examples and troubleshooting inline rather than splitting them into one-level-deep reference files; not 1 because organization is clear, not a wall of text.	2 / 3
	Total	10 / 12 Passed

Description

57%

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 names a concrete, distinctive niche but reads more like a mechanism summary than a trigger-rich skill description. It lacks an explicit 'Use when' clause and natural user keywords, capping completeness and trigger quality.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when execute_code_sandbox fails to import or run openpyxl while creating Excel/spreadsheet files.'

Include natural user terms such as 'spreadsheets', '.xlsx', and 'workbooks' alongside 'openpyxl'.

Surface the concrete capabilities (styling, formulas, merged cells) directly in the description so it lists multiple distinct actions.

Dimension	Reasoning	Score
Specificity	Quotes a concrete domain ('Create Excel files with openpyxl') and a fallback mechanism ('shell-based Python heredoc'), but describes essentially one action plus its fallback rather than a list of multiple distinct concrete actions as required for a 3.	2 / 3
Completeness	It states what the skill does and embeds a when condition ('when sandbox execution fails'), but lacks an explicit 'Use when...' clause or equivalent trigger guidance, so completeness is capped at 2 per the guidelines.	2 / 3
Trigger Term Quality	'Excel files' is a natural user term, but 'openpyxl', 'Python heredoc', and 'sandbox execution' are technical jargon; common natural variations (e.g. 'spreadsheets', '.xlsx') are missing, matching the 'some relevant keywords but missing variations' anchor.	2 / 3
Distinctiveness Conflict Risk	The narrow niche (openpyxl Excel creation via shell heredoc fallback only when the sandbox fails) is distinctive and unlikely to trigger for unrelated skills; not score 2 because it is not a generic overlap-prone description.	3 / 3
	Total	9 / 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-fallback/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.