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

47%

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

The workflow is clearly sequenced with strong validation checkpoints, but the skill is a verbose, repetitive monolith with no bundle-file structure and only pseudocode-level actionability.

Suggestions

Eliminate duplication: remove the repeated opening paragraph, the duplicated 'When to use' bullet, and the ~6 verbatim recurrences of the sampling-criterion-fallback sentence (state it once and reference it).

Split large sections (audit-record template, example validation plan, pseudo-code) into reference files under references/ and link to them from SKILL.md to apply progressive disclosure.

Replace abstract pseudocode with at least one concrete executable snippet (e.g., an openpyxl/pandas read-validate snippet) or name the specific tooling to use.

Dimension	Reasoning	Score
Conciseness	The body is heavily padded with redundancy: the opening paragraph is duplicated verbatim, the 'When to use' section repeats a bullet, and the sampling-criterion-fallback sentence recurs ~6 times across phases, decision rules, and the 'Rule of thumb' — far exceeding the token budget.	1 / 3
Actionability	Provides specific checklist guidance (count marked rows, confirm count equals N, spot-check top/middle/bottom rows) but offers only pseudocode and no executable code or commands, matching the 'pseudocode instead of executable code' anchor.	2 / 3
Workflow Clarity	Clear four-phase sequence with explicit go/no-go gates, independent-verification requirements, and feedback loops (validate → fix → re-validate), plus checklists for the destructive/batch write operations.	3 / 3
Progressive Disclosure	No bundle files exist and the skill is a single ~400-line monolithic SKILL.md with the audit-record template, examples, and detailed checklists all inline — content that should be split into references is embedded, though sections are well-organized.	2 / 3
	Total	8 / 12 Passed

Description

82%

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 with good natural trigger terms, but lacks an explicit 'Use when...' clause, leaving the 'when to use' guidance implied rather than stated.

Suggestions

Add an explicit 'Use when...' clause naming common user phrasings (e.g. 'Use when updating an Excel workbook whose path must be discovered, or when required tabs, columns, or sample counts must be verified after writing').

Include natural variations like '.xlsx', '.xlsm', or 'spreadsheets' to broaden trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions: 'locating candidate files', 'verifying workbook structure before editing', and 'running post-write validation against required sheets, populated columns, and sample counts' — matching the anchor for several specific concrete actions.	3 / 3
Completeness	Clearly answers 'what' (the audit-edit-validate process) but has no explicit 'Use when...' trigger clause, so the 'when' is only implied — capping completeness at 2 per the guidelines.	2 / 3
Trigger Term Quality	Uses natural terms a user would say — 'Excel workbooks', 'sheets', 'populated columns', 'sample counts' — giving good coverage beyond a single keyword, though it omits variations like '.xlsx' or 'spreadsheets'.	3 / 3
Distinctiveness Conflict Risk	The audit-edit-validate niche with pre-edit audit and post-write validation is a distinct, specific trigger unlikely to conflict with most other skills.	3 / 3
	Total	11 / 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/spreadsheet-audit-edit-validate/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.