CtrlK
BlogDocsLog inGet started
Tessl Logo

excel-author

Build auditable financial workbooks headless via openpyxl.

60

Quality

71%

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 ./optional-skills/finance/excel-author/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

88%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 body is a strong, executable banker-grade workbook skill: lean rule-driven prose, copy-paste-ready openpyxl code, a real recalc helper script, and an explicit checkpoint-based workflow with balance validation and a recalc feedback loop. The main gaps are minor conciseness trims and the absence of a deeper reference-file split for the larger convention/sensitivity material.

DimensionReasoningScore

Conciseness

The body is mostly lean: rules-driven, code-first, and assumes Claude knows Python/openpyxl, with only minor trimmable lines like the adaptation backstory; it is not quite a 5 because a few explanatory asides ('That's the sanity check', 'A reviewer can then scan...') and the full skeleton could be slightly tighter.

4 / 5

Actionability

Fully executable guidance throughout: a copy-paste-ready skeleton workbook, concrete formula patterns (e.g. '=D19*(1+$B$8)'), openpyxl snippet styles, a LibreOffice recalc command, and a referenced scripts/recalc.py helper that exists and is runnable.

5 / 5

Workflow Clarity

Clear sequenced process with explicit checkpoints: model-layout planning (define rows -> headers -> dividers -> formulas), a 'Verify step-by-step with the user' checkpoint list, a Checks-tab balance validation pattern, and a validate-before-deliver recalc step with feedback loops.

5 / 5

Progressive Disclosure

Well-organized sections with a one-level-deep reference to scripts/recalc.py that is real and clearly signaled; it is not a 5 because almost all detail lives inline in SKILL.md with no references/ or assets/ split for the larger reference material (sensitivity tables, conventions) that could be offloaded.

4 / 5

Total

18

/

20

Passed

Description

53%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 concise and names a specific niche (headless openpyxl financial workbooks) but stops short of listing multiple concrete actions and omits any explicit 'Use when...' trigger guidance, which caps completeness at 3. Adding natural trigger terms (Excel, .xlsx, spreadsheet, financial model) and a use-when clause would lift it toward the top anchors.

Suggestions

Add a 'Use when...' clause naming concrete triggers, e.g. 'Use when building auditable Excel/.xlsx financial models (DCF, 3-statement, LBO, comps) headless via openpyxl.'

List 2-3 specific actions beyond 'Build' (e.g. apply blue/black/green color coding, add named ranges, build balance-check tabs, generate sensitivity tables) to raise specificity.

Include natural user vocabulary (Excel, spreadsheet, .xlsx, financial model, DCF) that users actually say so trigger_term_quality matches the metadata tags.

DimensionReasoningScore

Specificity

Names the domain ('financial workbooks') and one concrete action ('Build'), but 'Build auditable financial workbooks headless via openpyxl' lists only a single high-level action rather than multiple specific actions like styling, named ranges, or balance checks.

3 / 5

Completeness

Has a clear 'what' (build auditable financial workbooks via openpyxl) but no 'Use when...' clause or explicit trigger guidance, capping completeness at 3 per the missing-trigger-clause rule.

3 / 5

Trigger Term Quality

Contains relevant terms ('financial workbooks', 'openpyxl') but omits common natural phrases users say ('Excel', 'spreadsheet', '.xlsx', 'DCF model') that appear in the skill's own metadata tags.

3 / 5

Distinctiveness Conflict Risk

The 'headless via openpyxl' + 'auditable financial workbooks' niche is fairly distinct from generic spreadsheet skills, with only minor overlap risk against a sibling xlsx skill; it is not quite at the minimal-conflict anchor of 5 because it lacks explicit trigger phrases.

4 / 5

Total

13

/

20

Passed

Validation

81%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

13

/

16

Passed

Repository
NousResearch/hermes-agent
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.