CtrlK
BlogDocsLog inGet started
Tessl Logo

excel-heredoc-workaround

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

56

Quality

64%

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

Quality

Content

75%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 body is highly actionable with complete executable examples and a clear sequenced workflow including verification. Its main weakness is redundancy between the Step 2 and Example Complete Workflow code blocks, which inflates length without adding guidance.

Suggestions

Remove or collapse the 'Example Complete Workflow' heredoc, which duplicates Step 2, or repurpose it as a single consolidated reference example.

Tighten 'Common Styling Patterns' by cross-referencing the main heredoc instead of re-declaring header fill/font snippets.

Make the error-recovery loop explicit in the steps (verify → if missing, check stdout for Python errors → fix → re-run) rather than only in Troubleshooting.

DimensionReasoningScore

Conciseness

Mostly efficient code without concept over-explanation, but the Step 2 heredoc and the 'Example Complete Workflow' heredoc are largely redundant, repeating workbook creation, styled headers, borders, and column-width logic.

3 / 5

Actionability

Fully executable, copy-paste-ready heredoc scripts plus standalone styling snippets cover the common cases (headers, fills, borders, alternating rows, auto-width).

5 / 5

Workflow Clarity

Clear 4-step sequence with explicit verification (Step 3 'ls -lh *.xlsx', Step 4 read-back) and a troubleshooting section, but the validate→fix→retry feedback loop is only weakly integrated into the steps.

4 / 5

Progressive Disclosure

Well-organized sections with clear headers and no external bundle files needed, though all content is inline and the duplicated full-workflow example could be trimmed or split out.

4 / 5

Total

16

/

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 distinct but frames its trigger around an internal tool failure rather than a user need, and lacks natural trigger synonyms. It communicates the what clearly but the when is only weakly user-facing.

Suggestions

Add a 'Use when...' clause with user-facing triggers, e.g. 'Use when creating .xlsx spreadsheets with openpyxl and the sandbox fails.'

Include natural synonyms such as 'spreadsheets', '.xlsx', or 'styled spreadsheets' to improve trigger-term coverage.

Reframe the 'when' around the user's goal (creating styled Excel files) rather than only the internal fallback condition.

DimensionReasoningScore

Specificity

Names the domain ('Excel files with openpyxl') and a concrete workaround action ('falling back to run_shell with inline Python heredoc'), but lists only one main action rather than several specific capabilities.

3 / 5

Completeness

Clearly states what it does, but the only 'when' is a tool-internal failure condition ('when execute_code_sandbox fails') with no user-facing 'Use when...' trigger clause, capping completeness at 3.

3 / 5

Trigger Term Quality

Includes 'Excel files' and 'openpyxl' but leans on internal/technical terms ('run_shell', 'execute_code_sandbox', 'heredoc') that users would not naturally say, and misses synonyms like 'spreadsheet' or '.xlsx'.

3 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (openpyxl Excel creation via heredoc fallback) with a distinct trigger, though there is minor overlap risk with general Excel/spreadsheet skills.

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.