spreadsheet-proof-gate

Edit Excel workbooks only after anchored preflight audit, then require deterministic Python/openpyxl post-write proof that every requested criterion is satisfied or explicitly reconciled before finalizing.

Quality

78%

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

Quality

Content

77%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 is highly actionable and exceptionally well-sequenced with strong validation gates, but it is monolithic and noticeably repetitive, restating the same proof/finalization rules across many sections. Splitting the verification script and decision rules into reference files and deduplicating the gate language would improve both conciseness and progressive disclosure.

Suggestions

Move the full openpyxl verification script template into a references file (e.g. references/verify_template.py) and keep only a short snippet plus a pointer in SKILL.md.

Consolidate the repeated finalization/FAIL/anchoring rules — currently restated in Core rule, Finalization gate, Decision rules, Practical checklist, Anti-patterns, and Why this skill exists — into a single authoritative section.

Split the criteria examples and status-vocabulary reference into a one-level-deep reference file so SKILL.md reads as an overview with clear navigation.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient and free of concept over-explanation, but the same gate/proof/anchoring rules are restated across roughly six sections (Core rule, Finalization gate, Decision rules, Practical checklist, Anti-patterns, Why this skill exists) and could be tightened considerably.	3 / 5
Actionability	A complete, executable openpyxl verification script template plus a rigid 'CRITERION\|<name>\|<STATUS>\|<reason>' checklist format give copy-paste-ready guidance covering the common cases.	5 / 5
Workflow Clarity	Phases 1-6 are clearly sequenced with explicit go/no-go gates, pre-edit audit, deterministic post-write proof, and feedback loops (repair FAIL then re-run verification), satisfying the validation-heavy workflow anchor.	5 / 5
Progressive Disclosure	The skill is well-organized with clear section headers but is a monolithic ~590-line single file with no bundle/reference files; the verification script template and repeated decision checklists could be split into one-level-deep references.	3 / 5
	Total	16 / 20 Passed

Description

71%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 and actionable with a distinctive proof-gate framing, but it omits an explicit 'when to use' trigger clause and underuses natural synonyms like 'spreadsheets' and '.xlsx'. Adding a 'Use when...' clause with broader trigger terms would raise completeness and trigger-term quality.

Suggestions

Append a 'Use when...' clause naming concrete triggers, e.g. 'Use when editing Excel workbooks where the result must be proven against a specification, or when verifying .xlsx changes after a delegated edit.'

Add natural synonyms and file extensions — 'spreadsheets', 'worksheets', '.xlsx', '.xlsm' — to broaden trigger-term coverage.

Keep the existing specificity; it is already strong and should be preserved verbatim.

Dimension	Reasoning	Score
Specificity	The description lists multiple concrete actions — 'anchored preflight audit', 'deterministic Python/openpyxl post-write proof', 'criterion is satisfied or explicitly reconciled' — giving comprehensive coverage of the skill's behavior.	5 / 5
Completeness	The description clearly answers 'what' but contains no 'Use when...' clause or equivalent explicit trigger guidance, which per the judging guidelines caps completeness at 3.	3 / 5
Trigger Term Quality	'Excel workbooks' and 'openpyxl' are natural terms users would say, but common synonyms like 'spreadsheets', 'worksheets', and the '.xlsx' extension are missing.	4 / 5
Distinctiveness Conflict Risk	The proof-gate framing is a clear niche, but trigger terms still overlap with generic Excel-editing skills, leaving minor conflict risk with closely related skills.	4 / 5
	Total	16 / 20 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 (593 lines); consider splitting into references/ and linking	Warning

	Total	15 / 16 Passed

Repository: HKUDS/OpenSpace
Path: benchmarks/gdpval/skills/spreadsheet-audit-edit-validate-merged/SKILL.md
Commit: 3827781

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