build-model

Build a multi-tab Excel financial model

Quality

53%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./plugins/daloopa/skills/build-model/SKILL.md

Quality

Content

50%

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

The skill is well-structured into clear phases with specific formulas and formatting specs, but it lacks executable code, validation checkpoints, and offloading of large specs into reference files. These keep every dimension at the mid-level anchor.

Suggestions

Add explicit validation checkpoints after the build, e.g. 'Verify the balance sheet balances, confirm the .xlsx opens, and sanity-check that the DCF implied price is within a plausible range before reporting.'

Provide an executable code anchor (openpyxl snippet or bundled script) for tab creation and the sensitivity/color-scale formatting, rather than the vague 'best available workflow'.

Move the long income-statement/balance-sheet/cash-flow line-item lists and full tab specs into a reference file (e.g. references/model-spec.md) and keep SKILL.md as a phase overview pointing to it.

Dimension	Reasoning	Score
Conciseness	The body is dense and assumes Claude's competence (no explanation of what revenue or WACC is), but it is lengthy with long inline line-item lists and tab specs that could be tightened; it is mostly efficient rather than lean, matching the level-2 anchor.	2 / 3
Actionability	It gives concrete formulas, hex colors, file-naming, and tab/row structures, but provides no executable code (e.g. an openpyxl script) and the generation instruction 'best available spreadsheet-generation workflow' is vague, so it stops at 'some concrete guidance but incomplete'.	2 / 3
Workflow Clarity	The six phases are clearly sequenced, but there are no validation/verification checkpoints (e.g. balance-sheet balance check, DCF sanity check, file-open verification) for a complex batch operation, which the rubric caps at 2.	2 / 3
Progressive Disclosure	External references ('../data-access.md', '../design-system.md') are well-signaled and one level deep with section pointers, but with no bundle files present the body itself is a monolithic detailed spec that could be split, matching 'some structure but could be better organized'.	2 / 3
	Total	8 / 12 Passed

Description

57%

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 concisely states a concrete, distinctive capability but stops at one action and omits any explicit 'when to use' trigger guidance. Adding a 'Use when...' clause would lift completeness and trigger coverage.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user asks to build a financial model, DCF, or multi-tab Excel workbook for a company or ticker.'

Expand specificity by naming a couple of concrete sub-actions, e.g. 'Build a multi-tab Excel financial model: pull historical financials, project forward periods, and run a DCF with sensitivity tables.'

Include natural keyword variations users say ('financial model', 'DCF', 'valuation', '.xlsx') to improve trigger-term coverage.

Dimension	Reasoning	Score
Specificity	The description names a concrete artifact ('multi-tab Excel financial model') and the action 'Build', but it lists a single action rather than multiple specific concrete actions, so it falls short of the level-3 anchor.	2 / 3
Completeness	It answers 'what' (build a multi-tab Excel financial model) but provides no 'when'/'Use when' clause or equivalent trigger guidance, which the rubric explicitly caps at 2.	2 / 3
Trigger Term Quality	'Excel financial model' are terms a user might naturally say, but the description omits common variations (e.g. 'DCF model', 'financial statements', '.xlsx') and any explicit trigger phrase, matching the 'some relevant keywords but missing common variations' anchor.	2 / 3
Distinctiveness Conflict Risk	Excel financial modeling is a clear, narrow niche with a distinct artifact, making it unlikely to trigger for unrelated skills; it cannot drop below 3 because it is specific, not a level below.	3 / 3
	Total	9 / 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: openai/plugins
Path: plugins/daloopa/skills/build-model/SKILL.md
Commit: 11c74d6

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