CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.

Quality

68%

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

52%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 delivers a clear, well-sequenced modeling workflow with genuinely useful startup-specific benchmarks and validation checks, but it is bloated with standard finance knowledge Claude already has, and its progressive-disclosure promise is broken: every referenced reference/example file is missing from the bundle while their would-be content is inlined. Tightening the overview and actually shipping the referenced files would fix the two weakest dimensions.

Suggestions

Actually create the referenced files (`references/model-templates.md`, `references/unit-economics.md`, `references/fundraising-scenarios.md`, and the three `examples/` files) and move the inlined Business Model Templates and step-level detail into them, or remove the dead references; also reconcile the inconsistent `resources/implementation-playbook.md` path to `references/`.

Trim sections explaining concepts Claude already knows (MRR/ARR definitions, basic dilution math, COGS/S&M/R&D/G&A category definitions) and the boilerplate "Use this skill when / Do not use this skill when" sections, keeping only the startup-specific heuristics (typical ratios, retention curves, pitfalls, sanity-check thresholds).

Convert the Model Validation sanity checklist into a feedback loop — e.g., "If LTV/CAC < 3 or payback > 18 months, revisit churn and CAC assumptions in Steps 2-3, then re-run the checklist" — so failed checks drive concrete next steps.

DimensionReasoningScore

Conciseness

The ~465-line body spends large sections on concepts Claude already knows ("ARR = MRR × 12", "Post-Money = Pre-Money + Investment", definitions of COGS/S&M/R&D/G&A, CAC/LTV) plus boilerplate padding ("Use this skill when"/"Do not use this skill when" sections, "Apply relevant best practices and validate outcomes"). It avoids the severely-padded tutorial style of the 1 anchor only because the domain-specific heuristics (retention curves, pitfalls, sanity-check thresholds) carry real value.

2 / 5

Actionability

Mostly concrete, executable guidance: worked formulas ("Runway = Ending Cash / Average Monthly Burn"), worked numbers ("Engineer: $150K salary × 1.35 = $202K fully-loaded"; "$5M at $20M pre-money → Dilution: 20%"), specific benchmarks ("LTV/CAC > 3, payback < 18 months"), and a 9-step sequence. Not a 5 because some sections are just consideration lists ("Clarify revenue model and pricing") and the complete worked examples are deferred to files that don't exist in the bundle.

4 / 5

Workflow Clarity

A clearly sequenced 7-step process, a 9-step Quick Start, and an explicit "Model Validation" sanity checklist ("[ ] Revenue growth rate is achievable (3x in Year 2, 2x in Year 3)") give most needed checkpoints. Not a 5 because there is no feedback loop — nothing instructs what to revise when a sanity check fails.

4 / 5

Progressive Disclosure

The body signals references to `references/model-templates.md`, `references/unit-economics.md`, `references/fundraising-scenarios.md`, and three `examples/` files — none of which exist in the bundle (which contains only SKILL.md) — and also points to an inconsistent `resources/implementation-playbook.md` path. Meanwhile the template-level detail that belongs in those files (four business-model templates, deep step-by-step material) is fully inlined, matching the anchor "content that clearly belongs in separate files is inlined".

2 / 5

Total

12

/

20

Passed

Description

71%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.

A specific, well-scoped description that names multiple concrete capabilities, but it omits any explicit "use when" trigger guidance and misses several natural synonyms (forecast, runway, burn rate) that users would likely say. Adding a trigger clause and broader keywords would round it out.

Suggestions

Append a trigger clause such as "Use when building startup financial models, projections, or fundraising scenarios, or when the user mentions runway, burn rate, ARR, or investor-ready models."

Include natural synonyms and variations users would say — "financial forecast/projections", "runway", "burn rate", "fundraising model", "budget" — to broaden trigger coverage.

Tie the scenario-planning mention to concrete trigger moments (e.g., pre-board reporting or pre-fundraise) to sharpen distinctiveness against generic spreadsheet/analysis skills.

DimensionReasoningScore

Specificity

Lists four concrete, specific actions ("revenue projections, cost structures, cash flow analysis, and scenario planning") scoped by horizon ("3-5 year") and audience ("early-stage startups"), matching the comprehensive-coverage anchor rather than the minor-gaps anchor below it.

5 / 5

Completeness

The "what" is clearly stated but there is no "Use when..." clause or equivalent trigger guidance, which caps completeness at 3 per the judging guidelines; the startup framing only weakly implies when to use it.

3 / 5

Trigger Term Quality

Good natural keyword coverage ("financial models", "revenue projections", "cash flow", "scenario planning", "startups") but missing common variations users would say such as "financial forecast/projections", "runway", "burn rate", or "fundraising model".

4 / 5

Distinctiveness Conflict Risk

"3-5 year financial models... for early-stage startups" carves a mostly distinct niche, though "financial model" generically could overlap with a general financial-analysis or spreadsheet-modeling skill.

4 / 5

Total

16

/

20

Passed

Validation

87%

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

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

referenced_paths_exist

Referenced path issues: 3 missing

Warning

Total

14

/

16

Passed

Repository

administrakt0r/AI-Agents-Safe-Coding-Skills

Path

skills/startup-financial-modeling/SKILL.md

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.