CtrlK
BlogDocsLog inGet started
Tessl Logo

openpyxl-merged-cell-safe-write

Safe pattern for writing values to merged cells in openpyxl spreadsheets

61

Quality

71%

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/openpyxl-merged-cell-safe-write/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

85%

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

The content is highly actionable with clear sequencing and a validation step, but it loses some token efficiency through repeated restatements of the same core pattern.

Suggestions

Consolidate the Correct Pattern, Multiple Merged Regions, and Quick Reference sections to remove repeated value→merge→format examples and tighten token use.

Add the missing imports (Font, Alignment, load_workbook) so the code blocks are fully copy-paste executable.

Trim explanatory filler such as 'This is a common pitfall that can consume multiple failed iterations' since Claude already understands MergedCell errors.

DimensionReasoningScore

Conciseness

The body is mostly efficient and actionable, but the value→merge→format pattern is restated across the Correct Pattern, Multiple Merged Regions, and Quick Reference sections, and lines like 'This is a common pitfall that can consume multiple failed iterations' add mild padding.

2 / 3

Actionability

It provides concrete, executable Python examples with copy-paste-ready value→merge→format patterns plus a checker helper function, giving clear direct guidance.

3 / 3

Workflow Clarity

A numbered Step-by-Step Procedure ends with an explicit 'Verify' step, and the Testing Your Spreadsheet section reloads the workbook to confirm no errors, providing a clear sequence with a validation checkpoint.

3 / 3

Progressive Disclosure

The single-file skill has no external references and is organized into clearly labeled sections (Problem, Core Rule, Patterns, Procedure, Guidelines, Quick Reference, Testing), making navigation easy.

3 / 3

Total

11

/

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 is specific and distinctive but stops short of stating when Claude should invoke it, capping completeness and trigger coverage at the mid level.

Suggestions

Add an explicit 'Use when...' trigger clause, e.g. 'Use when writing values to merged cells in openpyxl, or when you hit a MergedCell error.'

Broaden trigger terms to include common variations like 'Excel', '.xlsx', and 'cell formatting' that users actually mention.

Consider listing the concrete capabilities (write, merge, format, update existing merged cells) instead of a single 'writing values' action.

DimensionReasoningScore

Specificity

The phrase 'writing values to merged cells in openpyxl spreadsheets' names the domain (openpyxl, merged cells) and one concrete action (writing values), but it is a single action rather than a comprehensive list of capabilities.

2 / 3

Completeness

It states what the skill does (a safe write pattern) but has no 'Use when...' clause or equivalent explicit trigger guidance, so the 'when' is missing rather than stated.

2 / 3

Trigger Term Quality

It includes relevant natural terms ('merged cells', 'openpyxl', 'spreadsheets') a user might say, but coverage is limited and lacks common variations like 'Excel', '.xlsx', or 'cell formatting'.

2 / 3

Distinctiveness Conflict Risk

The combination of 'openpyxl' and 'merged cells' carves out a narrow, distinctive niche that is unlikely to trigger for unrelated skills.

3 / 3

Total

9

/

12

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.