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.

Quality

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

72%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is concise and well-organized for a simple skill, but it lists capabilities and guardrails rather than giving executable modeling instructions, formulas, or a sequenced workflow with validation. Actionability and workflow clarity are the weakest dimensions.

Suggestions

Add concrete modeling guidance — e.g., example formulas or a minimal model template for revenue projections and burn-rate/runway calculation — so the 'Skills' items become instructions rather than capability names.

Define an explicit build sequence with validation checkpoints (e.g., state assumptions → compute TAM/SAM/SOM → project revenue → derive burn/runway → sanity-check break-even), including how to flag and resolve inconsistent inputs.

Provide one short worked example with sample numbers so Claude has a concrete reference shape to follow.

Dimension	Reasoning	Score
Conciseness	Lean ~20-line body with no padding and no explanation of concepts Claude already knows; every section earns its place. Not below 3 because it assumes competence throughout rather than over-explaining.	3 / 3
Actionability	Some concrete guidance exists ('Use conservative estimates for SOM (5% of SAM)', 'Include monthly burn rate and team cost breakdown') but the 'Skills' section only names tasks rather than instructing how to perform them, and there are no formulas or example model structures. Not 1 because the guardrails give specific, executable rules; not 3 because key modeling details are missing.	2 / 3
Workflow Clarity	The 'Skills' list implies a loose sequence (market sizing → revenue → costs → funding → break-even) but there are no explicit validation checkpoints or error-recovery loops for the model-building process. Not 1 because a recognizable sequence is present; not 3 because no verification steps are defined.	2 / 3
Progressive Disclosure	A simple skill under 50 lines with no external references needed, organized into clear 'Skills' and 'Guardrails' sections; per the simple-skills note this qualifies for the top anchor. Not below 3 because the organization is clean and self-contained.	3 / 3
	Total	10 / 12 Passed

Description

100%

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 concise, well-targeted description that names concrete capabilities and provides an explicit 'Use when' trigger in third person, hitting all four anchors at the top level. No fluff or over-claims.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete capabilities — 'TAM/SAM/SOM, revenue projections, burn rate, runway, and break-even' — matching the 'multiple specific concrete actions' anchor; not the level below because it enumerates several distinct analyses rather than naming only a domain and one action.	3 / 3
Completeness	Explicitly states what ('Financial analyst for startup economics — TAM/SAM/SOM...') and when ('Use when building financial models or evaluating investment cases'), satisfying both halves with an explicit trigger; not below 3 because the 'Use when...' clause is present and concrete.	3 / 3
Trigger Term Quality	Includes natural terms a user would say — 'financial models', 'investment cases', 'burn rate', 'runway' — giving good coverage; not below 3 because it spans several common phrasings rather than a single keyword.	3 / 3
Distinctiveness Conflict Risk	Clear niche (startup finance) with distinct, domain-specific triggers unlikely to overlap with other skills; not below 3 because the terminology is specialized rather than generic.	3 / 3
	Total	12 / 12 Passed

Validation

87%

Warnings & errors only

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

Criteria	Description	Result
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
Path: modules/skills/src/main/resources/META-INF/skills/finance-agent/SKILL.md
Commit: 86693b6

Reviewed: about 2 hours ago

Table of Contents

Discovery Implementation Validation

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.