spreadsheet-audit-edit-validate

Safely update Excel workbooks by first locating candidate files, verifying workbook structure before editing, and running post-write validation against required sheets, populated columns, and sample counts.

Quality

64%

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

Quality

Content

62%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 workflow is exceptionally well-sequenced with strong validation checkpoints and feedback loops, and the instruction-style guidance is concrete and actionable. However, the body is repetitive and verbose, and all content is inlined in a single monolithic file with no progressive disclosure.

Suggestions

Remove the duplicated opening paragraph (lines 8-9) and consolidate the sampling-criterion fallback clause into a single stated rule referenced where needed instead of repeating it verbatim ~6 times.

Move the audit-record template, example validation plan, pseudo-code, and common-failure-modes list into reference files under ./references/ and link to them from SKILL.md to improve progressive disclosure.

Trim the redundant restatements of the post-write checks across the practical checklist, decision rules, and output-expectations sections to a single canonical checklist.

Dimension	Reasoning	Score
Conciseness	The body is noticeably verbose: the opening paragraph is duplicated verbatim (lines 8-9), the sampling-criterion fallback clause is repeated ~6 times, and the same checks are restated across Phase 4, the practical checklist, the example plan, pseudo-code, output expectations, and the rule of thumb.	2 / 5
Actionability	As an explicitly tool-agnostic instruction skill it provides concrete, specific guidance — explicit go/no-go conditions, required-check checklists, an example validation plan, and pseudo-code — with only minor gaps from the absence of actual executable commands.	4 / 5
Workflow Clarity	The four phases are clearly sequenced with explicit validation checkpoints (pre-edit go/no-go, independent direct-read verification, post-write validation), feedback loops (validate → fix → re-validate), and checklists for a destructive/batch operation.	5 / 5
Progressive Disclosure	Section organization is good, but the ~460-line skill is entirely monolithic with no bundle files and no one-level-deep references; content like the audit-record template, example plan, and pseudo-code could live in separate reference files.	3 / 5
	Total	14 / 20 Passed

Description

66%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 clearly states what the skill does with concrete, domain-specific actions, but omits an explicit 'when to use' trigger clause. Trigger term coverage is good though missing common synonyms and file extensions.

Suggestions

Add a 'Use when...' clause naming concrete triggers, e.g. modifying an existing .xlsx whose path must be discovered, or when the user specifies required tabs/columns/sample counts.

Include natural synonyms and extensions ('spreadsheets', '.xlsx', '.xlsm') to broaden trigger term coverage.

Consider listing the post-write checks (tabs, columns, sample counts) more concisely to push specificity toward 5 without padding.

Dimension	Reasoning	Score
Specificity	Names the Excel domain and three concrete actions — 'locating candidate files', 'verifying workbook structure before editing', and 'running post-write validation against required sheets, populated columns, and sample counts' — but stops short of the comprehensive multi-action list of a 5.	4 / 5
Completeness	The 'what' is clear (safely update workbooks via locate/verify/validate), but there is no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the rubric.	3 / 5
Trigger Term Quality	Includes natural terms users would say ('Excel workbooks', 'sheets', 'columns', 'sample counts') but omits common synonyms and extensions like 'spreadsheets' or '.xlsx', so a few natural terms are missing.	4 / 5
Distinctiveness Conflict Risk	The audit-then-validate framing around required sheets, columns, and sample counts is a fairly distinct niche with only minor overlap risk against generic spreadsheet skills.	4 / 5
	Total	15 / 20 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/spreadsheet-audit-edit-validate/SKILL.md
Commit: 3827781

Reviewed: 11 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.