CtrlK
BlogDocsLog inGet started
Tessl Logo

excel-subtotal-audit

Audit generated Excel reports by enumerating populated output rows, exposing formulas, and checking that each subtotal range includes all visible detail rows.

62

Quality

72%

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/excel-subtotal-audit/SKILL.md
SKILL.md
Quality
Evals
Security

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 content is highly actionable and workflow-clear with strong validation checkpoints, but it is over-long for a single SKILL.md due to redundant restatements of the same flow and would benefit from splitting detailed material into reference files.

Suggestions

Consolidate the redundant flow descriptions (Workflow 1-7, Practical procedure A/B/C, Example audit logic, Example pseudocode) into a single canonical sequence to reduce token cost.

Move the full Python sketch and adaptation notes into a references/ file (e.g. reference/python-example.md) referenced one level deep from the body, enabling progressive disclosure.

DimensionReasoningScore

Conciseness

The body is substantive and avoids explaining concepts Claude already knows, but the ~438-line document restates the same audit flow several times (Workflow 1-7, Practical procedure A/B/C, Example audit logic, Example pseudocode, Python sketch), offering clear tightening opportunities.

2 / 3

Actionability

Provides an executable openpyxl Python sketch with real function definitions, regex formula parsing, and a concrete failure-message format, plus copy-paste-ready row-audit logic.

3 / 3

Workflow Clarity

A clearly sequenced multi-step workflow with explicit fail-fast validation checkpoints, checklists, minimum acceptance criteria, and a definition of done — including a feedback loop that treats mismatches as hard failures.

3 / 3

Progressive Disclosure

No bundle files exist (references/scripts/assets absent) and the entire ~438-line skill lives inline in SKILL.md with no file references; sections are well-organized, but content such as the long Python sketch and adaptation notes that could be split into reference files is kept inline.

2 / 3

Total

10

/

12

Passed

Description

67%

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 about a narrow subtotal-audit task, but it omits any explicit 'when to use' trigger clause and underuses natural user keywords, capping completeness and trigger quality.

Suggestions

Add an explicit 'Use when ...' clause listing natural triggers, e.g. 'Use when generating Excel workbooks with subtotal/total formulas or auditing financial statements, rollups, and grouped exports.'

Broaden trigger terms with common user phrasing such as 'spreadsheets', 'workbooks', '.xlsx files', and 'SUM/SUBTOTAL formulas'.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'enumerating populated output rows, exposing formulas, and checking that each subtotal range includes all visible detail rows' — matching the anchor for naming several specific actions.

3 / 3

Completeness

Clearly states what the skill does but lacks any 'Use when...' or equivalent explicit trigger guidance; the 'when' is only implied, capping completeness at 2 per the judging guidelines.

2 / 3

Trigger Term Quality

Contains relevant terms like 'Excel reports' and 'subtotal' but omits common user variations such as 'spreadsheet', '.xlsx', 'workbook', or 'SUM', and leans somewhat technical rather than capturing natural phrasing.

2 / 3

Distinctiveness Conflict Risk

Targets a clear, narrow niche — verifying that subtotal formula ranges cover all visible detail rows in generated Excel reports — making it unlikely to trigger for unrelated skills.

3 / 3

Total

10

/

12

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.