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

69%

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.

The skill delivers a well-sequenced, concrete 10-step modeling workflow with real formulas and benchmarks, but it is padded with generic filler sections and keeps all detail in one long file with no reference bundle. Trimming the boilerplate sections and splitting report templates/benchmarks into reference files would raise both conciseness and progressive disclosure.

Suggestions

Delete the generic filler sections — "Instructions", "Use this skill when", "Do not use this skill when", the redundant "What This Command Does", and the "Notes" list — none of them add information Claude does not already have.

Move the report table templates (Sections 1-10) and the benchmark lists (gross-margin, opex, and departmental-ratio targets) into a references/ file and link them from a short overview, so the main SKILL.md stays lean.

Make validation an explicit workflow step (e.g. Step 10: check totals reconcile, compare LTV:CAC and burn multiple against benchmarks, fix and re-check) instead of only a report section, and fix the "$Xم" typo in the scenario table.

DimensionReasoningScore

Conciseness

The core content (formulas, benchmarks, table templates) is efficient, but generic filler pads it out: an "Instructions" section ("Apply relevant best practices and validate outcomes"), boilerplate "Use this skill when / Do not use this skill when" lists, a "What This Command Does" section repeating the intro, duplicate Instructions headings, and a filler "Notes" section. This is 'mostly efficient but includes some unnecessary explanation or could be tightened' rather than the minor-trimming of anchor 4.

3 / 5

Actionability

Concrete guidance throughout: the cohort MRR formula, unit-economics formulas (LTV:CAC > 3.0, CAC payback < 18 months, burn multiple < 2.0, Rule of 40), explicit scenario deltas (±30% customers, ±20% churn), and report table templates. Mostly executable for an instruction-only skill with minor gaps — validation is named but not operationalized, and one table contains a stray typo ("$Xم").

4 / 5

Workflow Clarity

A clear 10-step sequence runs from gathering inputs through revenue, costs, headcount, cash flow, metrics, scenarios, report generation, and saving, with well-defined sub-steps. Validation exists only as report Section 10 ('Sanity checks performed') rather than an explicit workflow checkpoint with a fix-and-recheck loop, so the 'clear sequence with most checkpoints; minor validation gaps' anchor fits better than the explicit-feedback-loop anchor 5.

4 / 5

Progressive Disclosure

The body is a 353-line monolith with good section headers but no bundle files at all — report table templates and benchmark lists that clearly belong in separate reference files are inlined, and the only cross-references point to other skills rather than files in this bundle. This matches the 'some structure but content that should be separate is inline' anchor; it cannot reach 4 without any actual reference files.

3 / 5

Total

14

/

20

Passed

Description

58%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 states a clear, moderately specific capability set but omits any trigger guidance and misses several natural keywords users would say. Adding a 'Use when...' clause with synonyms like financial projections, forecast, and fundraising would lift both completeness and trigger quality.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user asks for financial projections, a financial model, forecasts, runway/burn analysis, or fundraising planning.'

Include natural synonyms and domain phrasings users actually say — 'financial projections', 'forecast', 'startup budget', 'fundraising model' — to improve trigger_term_quality.

Optionally mention distinctive components like headcount planning and scenario analysis to sharpen the 'what' and reduce overlap with generic budgeting skills.

DimensionReasoningScore

Specificity

"Create detailed 3-5 year financial model with revenue, costs, cash flow, and scenarios" names the domain plus four concrete components, matching the 'several specific actions; minor gaps in coverage' anchor; it stops short of 5 because headcount, key metrics, and the three-scenario structure are not mentioned.

4 / 5

Completeness

The 'what' is clear (create a 3-5 year financial model with named components) but there is no 'Use when...' trigger clause or equivalent, which per the judging guidelines caps completeness at 3.

3 / 5

Trigger Term Quality

"financial model", "revenue", and "cash flow" are natural terms, but common user phrasings like "financial projections", "forecast", "fundraising", "budget", "runway", and "startup" are absent, matching the 'some relevant keywords but missing common variations or synonyms' anchor rather than the good-coverage anchor 4.

3 / 5

Distinctiveness Conflict Risk

The 3-5 year startup financial-modeling niche has distinct triggers with only minor overlap risk against general budgeting or personal-finance skills, matching the 'mostly distinct' anchor rather than the clear-niche anchor 5.

4 / 5

Total

14

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

rmyndharis/antigravity-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.