CtrlK
BlogDocsLog inGet started
Tessl Logo

openpyxl-merged-cell-safe-write

Safe pattern for writing values to merged cells in openpyxl spreadsheets

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

Quality

Content

67%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 content delivers executable, well-structured guidance for a focused single-topic skill with a clear procedure and validation, but it repeats the core pattern across sections and omits a few imports.

Suggestions

Consolidate the Correct Pattern, Incorrect Pattern, and Quick Reference sections to remove redundant restatements of the value→merge→format rule.

Add the missing imports (e.g., 'from openpyxl.styles import Font, Alignment' and 'from openpyxl import load_workbook') so code examples are copy-paste runnable.

Frame the Testing section as an explicit validate→fix→retry loop (re-run on reload failure) to strengthen the workflow feedback checkpoint.

DimensionReasoningScore

Conciseness

The body is mostly efficient and does not over-explain concepts Claude already knows, but the core value→merge→format rule is repeated across the Correct Pattern, Incorrect Pattern, and Quick Reference sections and could be tightened.

3 / 5

Actionability

It provides concrete, executable code for the correct and incorrect patterns plus multi-region and checking helpers, with only minor gaps such as missing imports for Font, Alignment, and load_workbook.

4 / 5

Workflow Clarity

The five-step procedure is clearly sequenced with a verify step, and the Testing section adds a save/reload validation loop, though the validation is not framed as an explicit error-recovery cycle.

4 / 5

Progressive Disclosure

The single-file skill is well organized with clear section headers and no external references are needed, but some content (the Quick Reference) duplicates earlier sections, a minor organization gap.

4 / 5

Total

15

/

20

Passed

Description

61%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 to a clear niche and uses natural trigger terms, but it omits an explicit 'Use when...' clause and lists only one action, limiting completeness and specificity.

Suggestions

Add an explicit 'Use when...' clause stating when Claude should apply this skill (e.g., 'Use when writing values to merged cells in openpyxl, or when you hit MergedCell errors').

Include a couple more concrete actions or synonyms (e.g., 'Excel', '.xlsx', 'formatting merged headers') to broaden trigger coverage.

Consider framing the description as a verb-led action ('Safely write values to merged cells in openpyxl spreadsheets') rather than a noun phrase for stronger actionability.

DimensionReasoningScore

Specificity

The description names the domain ('merged cells in openpyxl spreadsheets') and one concrete action ('writing values'), matching the anchor that names a domain plus 1-2 concrete actions without being comprehensive.

3 / 5

Completeness

It gives a clear 'what' (a safe pattern for writing to merged cells) but lacks any explicit 'Use when...' trigger clause, so completeness is capped at 3 per the rubric guidelines.

3 / 5

Trigger Term Quality

It includes natural terms a user would say ('openpyxl', 'merged cells', 'spreadsheets', 'writing values') with good coverage, though synonyms like 'Excel' or '.xlsx' are missing.

4 / 5

Distinctiveness Conflict Risk

The openpyxl merged-cell niche is specific and distinct with minimal conflict risk, with only minor overlap against a general openpyxl or spreadsheet-writing skill.

4 / 5

Total

14

/

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.