CtrlK
BlogDocsLog inGet started
Tessl Logo

startup-financial-modeling

Build comprehensive 3-5 year financial models with revenue projections, cost structures, cash flow analysis, and scenario planning for early-stage startups.

49

Quality

54%

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 ./skills/startup-financial-modeling/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

42%Scale 1-5

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

This skill reads more like a comprehensive finance textbook chapter than a concise, actionable skill file. It extensively explains concepts Claude already understands (basic financial terminology, what different business models are, standard SaaS metrics) while lacking truly executable guidance like code to generate spreadsheets or concrete output templates. The referenced supporting files don't exist in the bundle, making the progressive disclosure structure hollow.

Suggestions

Cut the content by 60-70%: remove explanations of basic financial concepts (COGS categories, what a marketplace is, what CAC means) and focus only on the specific methodology and formulas Claude should apply when building a model.

Add executable code or concrete output specifications—e.g., a Python script that generates a CSV/Excel financial model, or a precise JSON/markdown output schema for the model structure.

Integrate validation checkpoints into the workflow steps (e.g., after Step 2, verify unit economics are within benchmarks before proceeding to Step 3) rather than having a disconnected checklist at the end.

Move the business model templates, fundraising integration, and common pitfalls sections into the referenced files (references/ and examples/) and provide those bundle files, keeping SKILL.md as a lean overview with clear pointers.

DimensionReasoningScore

Conciseness

The skill is severely verbose at ~350+ lines, extensively explaining concepts Claude already knows (what COGS is, what SaaS means, basic financial formulas like ARR = MRR × 12). It reads like a finance textbook rather than a skill file. Typical ratios, business model definitions, and common pitfalls are all general knowledge that don't need to be spelled out at this length.

2 / 5

Actionability

The skill provides structured steps and formulas, but lacks executable code or concrete tool-based commands. The 'code' blocks are just arithmetic formulas and example numbers, not executable implementations. There's no actual spreadsheet generation code, no script to run, and no concrete output format specification—it's more of a conceptual guide than an actionable skill.

3 / 5

Workflow Clarity

The 7-step process is clearly sequenced and logical, but validation is only present as a checklist at the end rather than integrated as checkpoints between steps. There are no feedback loops (e.g., 'if metrics look unrealistic, revisit Step 2 assumptions'). The model validation section is separate from the workflow rather than embedded within it.

3 / 5

Progressive Disclosure

The skill references external files in `references/` and `examples/` directories, which is good structure, but no bundle files are provided so these references are dead links. Meanwhile, the main file inlines enormous amounts of content (business model templates, fundraising integration, common pitfalls) that should be in those referenced files. The overview is far too long for a SKILL.md that claims to delegate to reference files.

3 / 5

Total

11

/

20

Passed

Description

66%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 does a good job specifying concrete financial modeling capabilities and narrowing the domain to early-stage startups. Its main weakness is the lack of an explicit 'Use when...' clause, which would help Claude know precisely when to select this skill. Adding trigger phrases and a few more natural synonyms would strengthen it significantly.

Suggestions

Add an explicit 'Use when...' clause with trigger phrases like 'Use when the user asks about startup financial projections, fundraising models, burn rate calculations, or building a pro forma.'

Include additional natural synonyms users might say, such as 'forecasting,' 'pro forma,' 'burn rate,' 'runway,' or 'financial plan.'

DimensionReasoningScore

Specificity

Lists several specific actions: 'revenue projections, cost structures, cash flow analysis, and scenario planning.' These are concrete financial modeling activities, though it could be more granular (e.g., mentioning specific outputs like balance sheets, income statements, or cap tables).

4 / 5

Completeness

The 'what' is clearly stated (build financial models with specific components), but there is no explicit 'when' clause (e.g., 'Use when...'). The absence of a 'when' clause caps this at 3 per the rubric guidelines.

3 / 5

Trigger Term Quality

Includes strong natural keywords like 'financial models,' 'revenue projections,' 'cash flow,' 'scenario planning,' and 'startups.' Missing some common synonyms users might say like 'pro forma,' 'forecasting,' 'burn rate,' 'runway,' or 'financial plan.'

4 / 5

Distinctiveness Conflict Risk

The combination of '3-5 year financial models' and 'early-stage startups' creates a fairly distinct niche. There's minor overlap risk with general financial analysis or spreadsheet skills, but the startup focus and specific modeling scope help differentiate it.

4 / 5

Total

15

/

20

Passed

Validation

90%

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

Validation10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

10

/

11

Passed

Repository
administrakt0r/AI-Agents-Safe-Coding-Skills
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.