CtrlK
BlogDocsLog inGet started
Tessl Logo

3-statement-model

Build integrated IS/BS/CF financial workbooks in Excel.

53

Quality

61%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./optional-skills/finance/3-statement-model/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

70%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 a strong, domain-rich skill with excellent workflow clarity — explicit step-by-step user-confirmation gates, integrity checks, and a debug feedback loop — plus concrete formulas, hex codes, and Excel settings that make it highly actionable. Its main weaknesses are structural redundancy between the completion steps and validation sections, and progressive-disclosure gaps where an orphaned formatting.md and inlined validation categories should be split into references.

Suggestions

De-duplicate the validation content: merge the Step 5 cross-statement integrity table with the "Core Linkages (Must Always Hold)" table, and consolidate Step 4 per-sheet quality checks with the "Check Categories" sections to remove the repetition penalized in conciseness.

Wire up the orphaned references/formatting.md — replace the inlined Formatting palette table with a pointer ("See [references/formatting.md](references/formatting.md) for the full color palette") so the bundle file is used and the body shrinks.

Move the detailed Check Categories (Sections 1-9) and the margin/credit-metric catalogs into a dedicated reference file, keeping the body as an overview that links out, which would lift progressive_disclosure toward 4-5.

DimensionReasoningScore

Conciseness

The body is mostly valuable domain-specific content (formulas, sign conventions, NOL rules, hex codes) but contains real structural redundancy — the cross-statement integrity checks appear in both Step 5 (lines 286-295) and "Core Linkages" (lines 310-323), and Step 4 quality checks overlap the later "Check Categories" (lines 342-402) — plus over-explanation of basic Excel mechanics (Trace Precedents, Name Manager, font-color conventions stated twice), matching score 3 (mostly efficient but could be tightened); not a 4 because the redundancy is more than minor, not a 2 because the bulk is domain knowledge Claude does not already have rather than generic concept padding.

3 / 5

Actionability

Concrete executable guidance throughout — openpyxl formula-string example ("ws[\"D15\"] = \"=D14*(1+Assumptions!$B$5)\""), a recalc command ("python /path/to/excel-author/scripts/recalc.py ./out/model.xlsx"), exact check formulas ("Assets - Liabilities - Equity = 0"), specific hex codes, and Excel iterative-calc settings ("maximum iterations to 100, maximum change to 0.001") — matching score 4 (mostly executable with minor gaps); not a 5 because there is no complete end-to-end workbook-building script and some mechanics depend on the external excel-author skill, not a 3 because the guidance is specific and concrete rather than pseudocode.

4 / 5

Workflow Clarity

Exemplary sequencing and validation: an explicit 6-step user-confirmation gate sequence (after mapping, historicals, IS, BS, CF, finalize), a Step 1-6 completion process, integrity checks with "Expected Result = 0", and a Quick Debug Workflow feedback loop (find red → identify category → navigate → fix → verify) plus per-sheet checklists — matching the score-5 anchor of clear sequence with explicit validation, feedback loops, and checklists; it satisfies the destructive/batch feedback-loop requirement that would otherwise cap the score.

5 / 5

Progressive Disclosure

Two of three bundle references are well-signaled one level deep ("see [references/sec-filings.md]… only needed when…" and "See [references/formulas.md] for all formula details"), but formatting.md exists in the bundle yet is never linked (its content is inlined in the Formatting table) and roughly 150 lines of validation check categories are inlined in the body rather than split into a reference, matching score 3 (content that should be separate is inline); not a 4 because the orphaned bundle file and inlined bulk exceed minor gaps, not a 2 because the references that exist are clearly signaled and the body has good section structure.

3 / 5

Total

15

/

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 clear, specific niche (integrated IS/BS/CF financial modeling in Excel), but it states only the "what" with a single action verb and omits any "when/Use when" trigger guidance. Adding natural trigger phrases ("three-statement model", "financial model", spelled-out statement names) and an explicit use-when clause would raise completeness and trigger-term quality.

Suggestions

Add a "Use when…" clause specifying when to invoke this skill (e.g., "Use when building or completing an integrated three-statement financial model linking the income statement, balance sheet, and cash flow statement") to satisfy the completeness 'when' requirement.

Include natural trigger synonyms users actually say — "three-statement model", "financial model", and spelled-out "income statement / balance sheet / cash flow" — rather than relying on the "IS/BS/CF" abbreviation alone.

Expand beyond the single verb "Build" to list 1-2 more concrete actions (e.g., "Build, populate, and validate integrated IS/BS/CF financial workbooks") to improve specificity.

DimensionReasoningScore

Specificity

Quotes "Build integrated IS/BS/CF financial workbooks in Excel" — it names the domain concretely (integrated three-statement workbooks, Excel) but supplies only a single concrete action verb ("Build"), matching the score-3 anchor of domain plus 1-2 actions without comprehensive coverage; not a 4 because there are not several distinct actions, not a 2 because the action is concrete rather than generic and the domain is well specified.

3 / 5

Completeness

The description gives a clear "what" ("Build integrated IS/BS/CF financial workbooks in Excel") but no "when" — there is no "Use when…" clause or equivalent trigger guidance, so per the judging guideline completeness is capped at 3, fitting the score-3 anchor of clear what with missing when; not a 4 because no use-when guidance exists.

3 / 5

Trigger Term Quality

Natural keywords present ("financial workbooks", "Excel") but the most common user phrasings are absent — no "financial model", "three-statement", or spelled-out "income statement / balance sheet / cash flow" — and "IS/BS/CF" is professional jargon rather than a natural trigger, matching score 3 (relevant keywords missing common synonyms); not a 4 because key synonyms are missing, not a 2 because several relevant terms do appear.

3 / 5

Distinctiveness Conflict Risk

The "integrated IS/BS/CF" framing carves a mostly distinct three-statement niche with only minor overlap risk against closely related financial skills (dcf-model, lbo-model, excel-author) listed in metadata, matching score 4; not a 5 because "financial workbooks in Excel" still overlaps with general Excel skills, not a 3 because the IS/BS/CF integration framing is more specific than broad overlap-prone phrasing.

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.