excel-unmerge-before-write

Unmerge merged cells in openpyxl worksheets before writing values to avoid AttributeError

Quality

73%

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-unmerge-before-write/SKILL.md

Quality

Content

87%

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

The content is lean, highly actionable, and well-organized with executable examples throughout. Its main gap is the absence of a verification step after the template-modifying write/save operation.

Suggestions

Add a validation checkpoint after saving, e.g. reload output.xlsx and assert the target cells hold the written values and the merged ranges are gone.

Include a quick "verify before relying on output" step (open the saved file / check ws.merged_cells.ranges) so the workflow has an explicit feedback loop.

Dimension	Reasoning	Score
Conciseness	The body is lean and code-forward with no padding or explanation of concepts Claude already knows; every section earns its place.	3 / 3
Actionability	It provides fully executable, copy-paste-ready openpyxl code across multiple concrete examples (core pattern, multi-sheet, complete function) rather than pseudocode.	3 / 3
Workflow Clarity	Steps are clearly sequenced, but this template-modifying/batch operation (unmerge -> write -> save) has no validation or verification checkpoint, which the rubric caps at 2 for destructive/batch workflows.	2 / 3
Progressive Disclosure	It is a compact, self-contained skill with well-organized sections and no external references needed, which the simple-skill note allows to score 3.	3 / 3
	Total	11 / 12 Passed

Description

60%

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 concrete and specific about actions and tooling but omits an explicit trigger clause and broader keyword coverage. It reads as a focused niche skill rather than a generic one.

Suggestions

Add an explicit trigger clause, e.g. "Use when writing to openpyxl/Excel templates that contain merged cells or when you hit an AttributeError on cell write."

Broaden trigger terms to include common phrasings users say: "Excel", "xlsx", "template", and "merged cells".

Dimension	Reasoning	Score
Specificity	Names concrete actions ("Unmerge merged cells", "before writing values") plus the specific library (openpyxl) and exact error (AttributeError), matching the anchor that lists multiple specific concrete actions.	3 / 3
Completeness	It clearly answers "what" but lacks an explicit "Use when..." trigger clause, which the guidelines state caps completeness at 2.	2 / 3
Trigger Term Quality	Includes relevant natural terms like "merged cells", "openpyxl", and "AttributeError", but omits common variations a user would say such as "Excel", "xlsx", or "template", so it does not reach full coverage.	2 / 3
Distinctiveness Conflict Risk	The openpyxl-merged-cells niche is fairly specific, but it could still overlap with general Excel/spreadsheet skills, so it is not a fully conflict-free niche.	2 / 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-unmerge-before-write/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.