CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

cfo-advisor

Financial leadership for startups and scaling companies. Financial modeling, unit economics, fundraising strategy, cash management, and board financial packages. Use when building financial models, analyzing unit economics, planning fundraising, managing cash runway, preparing board materials, or when user mentions CFO, burn rate, runway, fundraising, unit economics, LTV, CAC, term sheets, or financial strategy.

60

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 ./.gemini/skills/cfo-advisor/SKILL.md

The canonical home for this skill is cfo-advisor in alirezarezvani/claude-skills

SKILL.md
Quality
Evals
Security

Quality

Content

57%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 body is an efficient, well-organized strategic overview with genuinely useful domain content (metric targets, red flags, decision triggers), but its effectiveness is undermined by the bundle itself: every detailed reference and every executable script it points to is missing, and the Quick Start commands lack the input/output specifications needed to run them. As shipped, the skill functions as a dashboard of CFO heuristics rather than an actionable toolkit.

Suggestions

Ship the referenced files or inline their essentials: all six bundle paths (references/financial_planning.md, references/cash_management.md, references/fundraising_playbook.md, scripts/burn_rate_calculator.py, scripts/unit_economics_analyzer.py, scripts/fundraising_model.py) are referenced but absent, breaking the skill's core navigation and executability.

Specify inputs and outputs for each Quick Start script — expected data format, CLI arguments, and what the script produces — so the commands are executable rather than bare invocations that cannot be acted on.

Add a sequenced workflow with validation checkpoints for at least the flagship deliverables (e.g., board package or financial model: gather inputs → build → cross-check totals/tie-out against actuals → deliver) instead of deferring all process detail to the missing reference files.

DimensionReasoningScore

Conciseness

Dense, table-driven content with no explanations of concepts Claude already knows; every section adds domain-specific value (targets, thresholds, red flags). Not 5 because of trimmable duplication: reference paths appear in both the Core Responsibilities table and the Resources section, and the Keywords section re-lists the frontmatter description's triggers.

4 / 5

Actionability

Concrete thresholds and commands are present ("python scripts/burn_rate_calculator.py", "Burn Multiple < 1.5x", "CAC Payback < 18 mo"), but the three Quick Start scripts are invoked with no arguments or input-format specification, and none of the six referenced bundle files exist — the commands are not executable as shipped. This is more than the minor gaps of anchor 4, but the specific targets, red flags, and artifact specs keep it well above anchor 2's minimal guidance.

3 / 5

Workflow Clarity

Entry sequencing exists ("Key Questions (ask these first)", the Output Artifacts map) and the Internal Quality Loop ("Self-verify... Peer-verify... Critic pre-screen") provides an output checkpoint, but the core workflows — model building, fundraising prep, board pack assembly — have no sequenced steps or validation checkpoints in the body; all process detail is deferred to reference files that are absent. Sequence fragments are present but checkpoints are implicit, matching anchor 3 rather than anchor 4.

3 / 5

Progressive Disclosure

The body is a well-organized overview with a clearly signaled, one-level-deep Resources section — but scored against the actual bundle structure, none of the six referenced files (three references/*.md, three scripts/*.py) exist, and the body additionally depends on external ../agent-protocol/SKILL.md and company-context.md. Navigation is broken, which exceeds the "minor organization gaps" of anchor 4, but the structure is good and references are prominently signaled, not buried as in anchor 2.

3 / 5

Total

13

/

20

Passed

Description

83%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 description: it clearly states both what the skill covers and when to use it, with natural, domain-appropriate trigger terms that mirror how a founder or finance leader would actually phrase a request. The only weaknesses are discipline-broad capability labels rather than concrete actions and a few missing trigger synonyms.

DimensionReasoningScore

Specificity

Lists five concrete capability areas — "Financial modeling, unit economics, fundraising strategy, cash management, and board financial packages" — but these are discipline-level labels rather than the atomic concrete actions of the anchor-5 example. Coverage clearly exceeds the 1-2 actions of anchor 3, so 4 is the best fit.

4 / 5

Completeness

Explicitly answers both what ("Financial modeling, unit economics, fundraising strategy, cash management, and board financial packages") and when ("Use when building financial models, analyzing unit economics, planning fundraising, managing cash runway, preparing board materials, or when user mentions CFO, burn rate...") with concrete trigger phrases, matching the anchor-5 example structure. Not 4 because both halves are fully explicit, not merely present.

5 / 5

Trigger Term Quality

Natural triggers users would actually say: "CFO, burn rate, runway, fundraising, unit economics, LTV, CAC, term sheets, or financial strategy". A few common variations are missing ("raise a round", "Series A", "board deck"), so it falls short of the comprehensive synonym coverage of anchor 5 but is well above anchor 3.

4 / 5

Distinctiveness Conflict Risk

Clear startup-CFO niche with domain-distinct triggers (burn rate, runway, LTV, CAC, term sheets). Minor overlap risk with closely related skills (financial-analyst, SaaS-metrics, or fundraising skills) via the broader terms "financial modeling" and "financial strategy" — the body itself references a sibling analyst skill — so it does not fully meet anchor 5's minimal conflict risk.

4 / 5

Total

17

/

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

referenced_paths_exist

Referenced path issues: 16 missing

Warning

Total

15

/

16

Passed

Repository

alirezarezvani/claude-skills

Path

.gemini/skills/cfo-advisor/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.