CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

startup-business-analyst-financial-projections

Create detailed 3-5 year financial model with revenue, costs, cash flow, and scenarios

Quality

71%

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-business-analyst-financial-projections/SKILL.md
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.

A well-sequenced, highly concrete modeling workflow with specific benchmarks, formulas, and output templates. The main flaws are generic boilerplate sections, a broken reference to a nonexistent playbook file, and inlined report-template content that should live in a separate reference.

Suggestions

Delete the generic filler sections ('Use this skill when', 'Do not use this skill when', the first '## Instructions') that restate the obvious, and merge 'What This Command Does' into the intro to cut roughly 20 lines of padding.

Fix or remove the broken 'resources/implementation-playbook.md' reference — the file does not exist in the bundle — and move the Step 9 report table templates into it so SKILL.md stays a lean overview.

Convert Section 10 validation from a report deliverable into an explicit build-time feedback loop (compute, sanity-check against benchmarks, fix assumptions, re-verify), and fix the corrupted template cell '$Xم'.

DimensionReasoningScore

Conciseness

The core Steps 1-10 are dense with domain benchmarks and formulas that earn their tokens, but generic filler pads the body: 'Working on financial projections tasks or workflows', 'You need a different domain or tool outside this scope', two separate '## Instructions' sections, and '## What This Command Does' duplicating the intro. It is not 2 because most content is non-redundant domain guidance, and not 4 because several sections are pure boilerplate that could be deleted.

3 / 5

Actionability

Guidance is highly concrete: the cohort MRR formula, cost targets ('SaaS: 75-85%'), scenario deltas ('-30% vs. base'), metric targets ('LTV:CAC ratio (target > 3.0)'), and full report table templates. It falls short of 5 because the pointer to 'resources/implementation-playbook.md' targets a file that does not exist and a stray character corrupts one template cell ('$Xم').

4 / 5

Workflow Clarity

A clear 10-step sequence runs from gated input gathering (Step 1's explicit checklist) to saving the model (Step 10), with validation named in report Section 10 ('Sanity checks performed, benchmark comparisons') and in the Do list. It is not 5 because validation is an output deliverable rather than an explicit feedback loop (validate, fix, re-check) during the build.

4 / 5

Progressive Disclosure

Section structure is consistent and easy to navigate, but no bundle files exist at all while the body references 'resources/implementation-playbook.md' (nonexistent), and roughly 60 lines of report table templates are inlined that belong in a reference file. It is not 2 because references are clearly signaled rather than buried, and not 4 because the single reference is broken and heavy template content is inlined in SKILL.md.

3 / 5

Total

14

/

20

Passed

Description

66%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 concrete, domain-specific description that clearly states what the skill builds, but it omits any 'use when' trigger guidance and lacks common synonyms like 'financial projections' or 'forecast'. Adding an explicit trigger clause and a couple of natural user phrasings would lift it substantially.

Suggestions

Append an explicit trigger clause, e.g. 'Use when the user asks for financial projections, a financial model, forecasting, runway analysis, or fundraising numbers for a startup.'

Include natural synonyms users actually say — 'financial projections', 'forecast', 'fundraising model', 'runway' — alongside 'financial model'.

Optionally mention headcount planning or key metrics (CAC/LTV, burn rate) to round out coverage of what the body delivers.

DimensionReasoningScore

Specificity

The description names the domain and lists several concrete components ('3-5 year financial model with revenue, costs, cash flow, and scenarios'), matching the 'several specific actions; minor gaps' anchor. It falls short of 5 because it covers a single create action and omits headcount, metrics, and fundraising that the body actually delivers.

4 / 5

Completeness

The 'what' is clear (create a 3-5 year financial model with named components), but there is no 'Use when...' clause or equivalent trigger guidance, which caps completeness at 3 per the rubric guideline. It is not 2 because the 'what' half is concrete and specific.

3 / 5

Trigger Term Quality

Natural terms like 'financial model', 'revenue', 'cash flow', and 'scenarios' are present, giving good keyword coverage. It stays at 4 rather than 5 because common user phrasings like 'financial projections', 'forecast', 'runway', or 'fundraising model' are missing.

4 / 5

Distinctiveness Conflict Risk

The startup multi-year financial-modeling niche is mostly distinct with concrete differentiators (3-5 year horizon, scenarios, cash flow). Minor overlap risk remains with closely related budgeting or business-case skills, so it does not reach 5.

4 / 5

Total

15

/

20

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.

Validation — 15 / 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

administrakt0r/AI-Agents-Safe-Coding-Skills

Path

skills/startup-business-analyst-financial-projections/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.