spreadsheet-struct-verified

Create and modify Excel workbooks with mandatory deterministic Python verification of workbook structure, required sheets, populated columns, and sample counts before reporting completion.

Quality

68%

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/spreadsheet-audit-edit-validate-enhanced/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 highly actionable and workflow-clear, with executable verification code and strong validation checkpoints, but it is monolithic and repetitive — the inline 225-line script and duplicated modify/create checklists should be split out and tightened.

Suggestions

Move the verification script template into a scripts/ file (e.g. scripts/verify_workbook.py) and reference it from the body to reduce the monolithic wall of code.

De-duplicate the modify-mode and create-mode checklists into a single parameterized checklist rather than restating similar steps twice.

Consolidate the repeated 'Phase 4 is MANDATORY' reminders into one clearly marked mandate to tighten conciseness.

Dimension	Reasoning	Score
Conciseness	It avoids explaining concepts Claude already knows, but it is repetitive — the modify-vs-create checklist is duplicated, "Phase 4 is MANDATORY" is restated many times, and a ~225-line verification script sits inline — so it could be tightened, matching the score-2 anchor.	2 / 3
Actionability	It provides a complete, copy-paste-ready Python verification script with a main() entry point, a concrete spec-JSON schema, and an exact execution command (`python3 verify_workbook.py ... '<spec_json>'`), meeting the score-3 'fully executable, copy-paste ready' anchor.	3 / 3
Workflow Clarity	Four phases are explicitly sequenced with go/no-go decisions at Phase 2 and Phase 4, an explicit feedback loop (fix → re-verify → iterate until PASSED), and a minimum verification checklist — exactly the score-3 anchor of clear sequence plus validation and feedback loops.	3 / 3
Progressive Disclosure	The body is well-sectioned with clear headers, but it is a ~560-line monolith with no bundle files and the large verification script/checklists inlined where a scripts/ file would be appropriate, matching the score-2 anchor of 'content that should be separate is inline'.	2 / 3
	Total	10 / 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 specific and action-oriented about Excel workbook structure verification, but it omits explicit "Use when..." trigger guidance and natural term variations, which leaves completeness and trigger quality at the mid level.

Suggestions

Add a 'Use when...' clause with explicit triggers (e.g., when the user requires verified sheet names, column populations, or sample counts before delivery).

Include natural term variations users would say — 'spreadsheets', '.xlsx', 'tabs', 'row counts' — to broaden trigger coverage.

Lead with the distinguishing trait (deterministic post-write verification) to reduce overlap with a generic Excel-creation skill.

Dimension	Reasoning	Score
Specificity	It lists multiple concrete actions — "Create and modify Excel workbooks" plus "verification of workbook structure, required sheets, populated columns, and sample counts" — rather than vague language, matching the score-3 anchor that lists several specific actions.	3 / 3
Completeness	The description clearly states what the skill does, but there is no "Use when..." clause or equivalent explicit trigger for when to invoke it, so the "when" is only implied — per the judging guideline this caps completeness at 2.	2 / 3
Trigger Term Quality	"Excel workbooks" and "sheets/columns" are natural terms, but common variations a user would actually say ("spreadsheets", ".xlsx", "tabs") are absent, leaving keyword coverage incomplete like the score-2 anchor.	2 / 3
Distinctiveness Conflict Risk	The verification-gated niche is somewhat specific, but the generic opening "Create and modify Excel workbooks" overlaps with ordinary spreadsheet skills and there are no explicit distinct triggers, so it could still conflict with a sibling Excel skill.	2 / 3
	Total	9 / 12 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (565 lines); consider splitting into references/ and linking	Warning

	Total	15 / 16 Passed

Repository: HKUDS/OpenSpace
Path: benchmarks/gdpval/skills/spreadsheet-audit-edit-validate-enhanced/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.