finance-skills

Router/index for the 2 finance skills bundled in this plugin: financial-analyst (ratio analysis, DCF valuation, budget variance, rolling forecasts) and saas-metrics-coach (ARR/MRR, churn, CAC/LTV, NRR, quick ratio). Use when a finance request doesn't obviously match one skill and you need to pick the right one (e.g., 'analyze these financials', 'how healthy are my SaaS metrics').

Quality

96%

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

92%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 tight, well-structured router body: the routing table plus tie-break rule makes the single action unambiguous, the quick start is executable, and length is minimal. The only flaw is an inconsistent path prefix between the routing table and the quick start commands.

Suggestions

Reconcile the path prefixes: the routing table lists 'skills/financial-analyst/' while Quick start uses 'finance/skills/financial-analyst/' — pick one consistent plugin-root-relative form so the commands work as written.

Verify the referenced script paths (ratio_calculator.py, metrics_calculator.py) exist at the stated locations in the packaged bundle, since no scripts are shipped alongside this router.

Dimension	Reasoning	Score
Conciseness	A lean ~35-line router: routing table, tie-break rule, copy-paste quick start, related-skills note, and two rules — every token earns its place with no explanation of concepts Claude already knows.	5 / 5
Actionability	Gives concrete, mostly copy-paste-ready commands (e.g. 'python3 finance/skills/financial-analyst/scripts/ratio_calculator.py --help') and a concrete routing table, but the Path column ('skills/financial-analyst/') and Quick start ('finance/skills/financial-analyst/') use inconsistent path prefixes, so commands may fail as written.	4 / 5
Workflow Clarity	The single routing action is unambiguous: a signal-to-skill table, an explicit both-match tie-break ('ask whether the user wants statement-level analysis... or SaaS operating metrics'), and the rule 'Route to exactly one skill, then follow that skill's workflow'. No destructive or batch operations, so no validation cap applies.	5 / 5
Progressive Disclosure	Under 50 lines with well-organized sections; pointers to the bundled skills' SKILL.md files are clearly signaled one level deep, and out-of-bundle content is explicitly quarantined ('packaged separately, not in this bundle').	5 / 5
	Total	19 / 20 Passed

Description

100%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.

An exemplary description for a router skill: it names both sub-skills with their concrete capabilities, gives an explicit 'Use when' trigger clause with quoted user phrases, and cleanly scopes its routing role. It is concise, specific, and fully answers both what it does and when to use it.

Dimension	Reasoning	Score
Specificity	Enumerates concrete capabilities for both bundled skills ('ratio analysis, DCF valuation, budget variance, rolling forecasts' and 'ARR/MRR, churn, CAC/LTV, NRR, quick ratio') — comprehensive, specific coverage with no vague fluff.	5 / 5
Completeness	Clearly answers both 'what' (router/index for the two named skills with their capabilities) and 'when' (explicit 'Use when a finance request doesn't obviously match one skill' with concrete example triggers).	5 / 5
Trigger Term Quality	Includes an explicit 'Use when...' clause with verbatim natural user phrases ('analyze these financials', 'how healthy are my SaaS metrics') plus thorough domain keyword coverage (DCF, churn, CAC/LTV, NRR, quick ratio).	5 / 5
Distinctiveness Conflict Risk	Scopes itself precisely as a router between two named finance skills and even handles the both-match case, giving it a clear niche with distinct triggers and minimal conflict risk.	5 / 5
	Total	20 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: alirezarezvani/claude-skills
Path: finance/skills/finance-skills/SKILL.md
Commit: 19392f7

Reviewed: 12 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.