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.

57

Quality

67%

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 ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/startup-financial-modeling/SKILL.md

The canonical home for this skill is startup-financial-modeling in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

63%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 well-structured and actionable with concrete formulas, benchmarks, and a clear multi-step workflow plus validation checklist, but it is noticeably padded with basic finance concepts Claude already knows and its progressive-disclosure references point to files that are not present in the bundle.

Suggestions

Trim explanations of concepts Claude already knows (the COGS/S&M/R&D/G&A line-item breakdowns, the definition of MRR/ARR, generic 'Use/Do not use/Instructions' boilerplate) and keep only the domain-specific benchmarks and formulas.

Create the referenced bundle files (references/model-templates.md, references/unit-economics.md, references/fundraising-scenarios.md, examples/*.md, resources/implementation-playbook.md) and move the inlined business-model templates and fundraising section into them so SKILL.md stays a lean overview.

Embed explicit validation checkpoints inside each step of the Step-by-Step Process (e.g. 'after Step 5, verify runway > 12 months before proceeding') instead of consolidating all validation in a trailing section.

DimensionReasoningScore

Conciseness

The body is mostly efficient reference material (formulas, benchmark ratios, example projections) but pads with concepts Claude already knows — e.g. enumerating what belongs in 'COGS', 'G&A', 'S&M', 'R&D' and defining MRR/ARR — plus generic 'Use this skill when' / 'Do not use' / 'Instructions' boilerplate that could be trimmed.

3 / 5

Actionability

Provides concrete formulas (MRR = Σ(Cohort Size × Retention Rate × ARPU); Runway = Cash / Monthly Burn; Dilution % = Investment / Post-Money), worked examples ($150K × 1.35 = $202K; Year 1 $500K ARR / 50 customers), and specific benchmark ranges, giving mostly executable guidance with only minor gaps.

4 / 5

Workflow Clarity

A clear 7-step 'Step-by-Step Process' (Define Model → Revenue → Costs → Headcount → Cash Flow → Metrics → Scenarios) is mirrored by a 9-step Quick Start, and a 'Model Validation' section provides a sanity-check checklist; however the validation gates are a separate end section rather than explicit inline checkpoints within the steps.

4 / 5

Progressive Disclosure

There is reasonable structure and a dedicated 'Additional Resources' section with bold, clearly signaled references to references/* and examples/* files, but the referenced files do not exist in the bundle and large template content (four business-model templates, fundraising integration, pitfalls) is inlined in SKILL.md that would more properly live in those separate files.

3 / 5

Total

14

/

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.

The description is specific and covers the domain comprehensively with mostly natural trigger terms, but it lacks an explicit 'Use when...' trigger clause, which caps completeness at 3, and is missing a few common synonyms.

Suggestions

Add an explicit trigger clause, e.g. 'Use when building startup financial models, projections, or fundraising scenarios for early-stage companies.'

Include common synonyms users might say such as 'forecast', 'financial projections', 'runway', or 'fundraising model' to broaden trigger coverage.

Tighten the niche signal (e.g. mention 'investor-ready' or 'board/ fundraising') to further reduce overlap with general financial-analysis skills.

DimensionReasoningScore

Specificity

Lists multiple concrete capabilities — 'revenue projections, cost structures, cash flow analysis, and scenario planning' — plus the '3-5 year' scope and 'early-stage startups' target, giving comprehensive coverage rather than just naming the domain.

5 / 5

Completeness

The 'what' is clearly stated (build 3-5 year financial models with the listed components), but there is no 'Use when...' clause or equivalent explicit trigger guidance; the phrase 'for early-stage startups' only weakly implies the 'when', so per the rubric completeness is capped at 3.

3 / 5

Trigger Term Quality

Includes natural terms a user would say ('financial models', 'revenue projections', 'cash flow analysis', 'scenario planning', 'startups'), but misses common synonyms a user might equally say such as 'forecast', 'financial projections', 'budget', 'runway', or 'fundraising model'.

4 / 5

Distinctiveness Conflict Risk

'startup financial modeling' with 3-5 year models and scenario planning is a mostly distinct niche with minimal conflict risk, though there is minor overlap risk with more general business-planning or financial-analysis skills.

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.

Validation14 / 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
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.