CtrlK
BlogDocsLog inGet started
Tessl Logo

financial-model-review

Investor-first workflow for reviewing an existing financial model, forecast, or sensitivity analysis. Use for prompts like "review this model", "stress test these assumptions", "what breaks in this forecast", or "is this model decision-ready". Best when you have a spreadsheet export, pasted assumptions, key drivers, and the decision the model supports. Optional Open Brain search and capture can pull prior model context and store the final review memo.

79

Quality

100%

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

SKILL.md
Quality
Evals
Security

Quality

Content

100%

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

A well-crafted, lean instruction skill: a clear sequenced process, specific actionable checklists for what to flag, explicit judgment/triage rules as quality checkpoints, and clean section organization. It respects Claude's competence and stays within scope.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence — it never explains basic finance or spreadsheet concepts, and each section (Problem, When to Use, Process, Evidence Rules, Output) is brief and load-bearing, so it stays at the top anchor rather than the 'could be tightened' anchor 2.

3 / 3

Actionability

Provides concrete, specific checklists rather than vague direction — e.g. flag 'unsupported growth, margin leaps, pricing optimism, CAC efficiency, churn stability, and timing shortcuts' and 'circular reasoning, hidden hard-codes, inconsistent periods, or unsupported roll-forwards'; per the scoring note, absence of code in an instruction-only skill is not penalized when guidance is this actionable.

3 / 3

Workflow Clarity

A clear 7-step sequenced Process (Frame → Identify shape → Review assumptions → Review structure → Review scenarios → Convert to judgment → Optionally Open Brain) paired with a dedicated 'Evidence and Judgment Rules' checklist that acts as explicit judgment checkpoints; no validation loop is required because this is a non-destructive review task.

3 / 3

Progressive Disclosure

No bundle files exist (references/scripts/assets are empty), so disclosure is judged on organization: the body is split into well-labeled sections with no monolithic wall and no content that cries out for a separate file, satisfying the well-organized anchor.

3 / 3

Total

12

/

12

Passed

Description

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, third-person description that clearly states what the skill does, when to use it via natural user phrasing, and the context it needs. It is concise, specific, and well-differentiated from neighboring skills.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — reviewing a financial model/forecast/sensitivity analysis, stress testing assumptions, pulling prior model context, and storing the final review memo — matching the 'lists multiple specific concrete actions' anchor rather than the single-action anchor 2.

3 / 3

Completeness

Explicitly answers both what ("Investor-first workflow for reviewing an existing financial model, forecast, or sensitivity analysis") and when ("Use for prompts like..." plus "Best when you have...") with explicit triggers, satisfying the top anchor.

3 / 3

Trigger Term Quality

Quotes natural prompt phrasing a user would actually say — "review this model", "stress test these assumptions", "what breaks in this forecast", "is this model decision-ready" — giving good coverage of real trigger terms, not jargon.

3 / 3

Distinctiveness Conflict Risk

Occupies a clear niche — investor-first financial model review — with distinct triggers unlikely to fire for adjacent skills; the body's 'When Not to Use' routing to deal-memo-drafting and research-synthesis further reduces conflict risk.

3 / 3

Total

12

/

12

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

Repository
NateBJones-Projects/OB1
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.