CtrlK
BlogDocsLog inGet started
Tessl Logo

finance-agent

Financial analyst for startup economics — TAM/SAM/SOM, revenue projections, burn rate, runway, and break-even. Use when building financial models or evaluating investment cases.

63

Quality

75%

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 ./modules/skills/src/main/resources/META-INF/skills/finance-agent/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

58%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 concise, well-organized skill body with useful guardrails, but it lacks executable methodology (formulas, worked examples) and any sequenced workflow with validation checkpoints. The main weakness is guidance that tells Claude what to produce without how to compute it.

Suggestions

Add concrete formulas or worked examples for the core computations (e.g., runway = cash / monthly burn; break-even = fixed costs / contribution margin) so the guidance is executable rather than descriptive.

Provide a numbered workflow that sequences the analyses (e.g., size market → project revenue → estimate costs → compute burn/runway → derive break-even) with explicit checkpoints for validating assumptions.

Trim the opening paragraph that restates the frontmatter description, or replace it with a direct 'Begin by...' instruction to improve token efficiency.

DimensionReasoningScore

Conciseness

The body is lean and avoids explaining concepts Claude already knows, but the opening paragraph ('You are a financial analyst... You produce quantitative frameworks...') partly restates the frontmatter description and could be trimmed, sitting just below the 5 anchor.

4 / 5

Actionability

Guardrails offer a few concrete parameters ('conservative estimates for SOM (5% of SAM)', 'monthly burn rate and team cost breakdown'), but the Skills list only names analyses without formulas or methodology for computing runway, break-even, or projections, leaving key execution details missing as in the 3 anchor.

3 / 5

Workflow Clarity

There is no sequenced workflow at all — only capability and guardrail lists — so steps are effectively missing; the guardrails provide a couple of loose implicit checkpoints, placing this just above the 1 anchor.

2 / 5

Progressive Disclosure

The skill is under 50 lines with no need for external references and is organized into clear ## Skills and ## Guardrails sections, satisfying the simple-skill exception for a 5.

5 / 5

Total

14

/

20

Passed

Description

92%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 strong, third-person description that clearly states both what the skill does and when to use it, with concrete domain-specific capabilities and distinct triggers. The only minor gap is synonym breadth in trigger terms.

DimensionReasoningScore

Specificity

The description enumerates five concrete analyses — 'TAM/SAM/SOM, revenue projections, burn rate, runway, and break-even' — giving comprehensive coverage of the domain's specific capabilities, matching the 5 anchor.

5 / 5

Completeness

It states a clear 'what' (financial analyst for startup economics plus the listed analyses) and an explicit 'when' ('Use when building financial models or evaluating investment cases'), matching the 5 anchor for both.

5 / 5

Trigger Term Quality

Natural phrases users would say are well covered ('financial models', 'investment cases', 'burn rate', 'runway'), but synonym coverage is limited (no 'fundraising', 'valuation', 'unit economics'), landing just below the 5 anchor.

4 / 5

Distinctiveness Conflict Risk

The startup-economics niche with distinct triggers (TAM/SAM/SOM, burn rate, runway) is clearly delineated from other skills, with minimal overlap risk, matching the 5 anchor.

5 / 5

Total

19

/

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

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

Total

14

/

16

Passed

Repository
Atmosphere/atmosphere
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.