CtrlK
BlogDocsLog inGet started
Tessl Logo

financial-health

Run financial ratio analysis, DCF valuation, budget variance analysis, and rolling forecasts. Usage: /financial-health <ratios|dcf|budget|forecast> <data.json>

64

Quality

76%

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/financial-health/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

88%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 concise, well-structured, and actionable, with clear subcommand dispatch and one-level references to scripts. The main gap is that referenced script paths point outside the skill bundle and no inline executable code is shown.

Suggestions

Include a short inline code or command snippet showing how a script is actually invoked (e.g. a sample ratio_calculator.py call with expected output) to lift actionability.

Confirm referenced script paths resolve within the skill bundle, or relist them relative to the skill root so navigation is unambiguous.

Add a brief validation note for batch/forecast outputs (e.g. sanity-checking that forecasts are non-negative) to harden workflow clarity.

DimensionReasoningScore

Conciseness

Lean and efficient across ~30 lines with no concept explanations or padding; every line (commands, examples, script paths with one-line descriptions) earns its place.

5 / 5

Actionability

Provides concrete executable invocations and full script paths, but shows only command syntax rather than inline executable code for the underlying analyses, leaving minor gaps.

4 / 5

Workflow Clarity

As a single-purpose command dispatcher with four unambiguous subcommands, the simple-skill exception applies; each invocation is a clear single action and the operations are analytical rather than destructive.

5 / 5

Progressive Disclosure

Well-organized sections point one level deep to four scripts and a Skill Reference with clear one-line descriptions, but the referenced paths live outside this skill's bundle and cannot be verified as present.

4 / 5

Total

18

/

20

Passed

Description

63%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 is specific and distinct, clearly naming four financial analysis capabilities, but it lacks an explicit 'Use when...' trigger clause and broader keyword synonyms. Completeness and trigger-term quality are the main weaknesses.

Suggestions

Add an explicit 'Use when...' clause naming concrete trigger phrases (e.g. 'Use when valuing a company, analyzing financial ratios, explaining budget variances, or building revenue forecasts').

Broaden trigger terms with natural synonyms and file extensions users actually say (e.g. 'discounted cash flow', 'valuation model', '.json financials').

Differentiate more sharply from /saas-health by noting this skill targets general corporate finance rather than SaaS subscription metrics.

DimensionReasoningScore

Specificity

Names the domain and four concrete actions ('financial ratio analysis, DCF valuation, budget variance analysis, and rolling forecasts') with comprehensive coverage and no gaps.

5 / 5

Completeness

The 'what' is clearly stated via four named analyses, but 'when' is only weakly implied through the invocation-style 'Usage:' line rather than explicit trigger guidance, capping completeness at 3.

3 / 5

Trigger Term Quality

Relevant keywords like 'ratio analysis', 'DCF valuation', 'budget variance', and 'forecast' are present, but common synonyms (e.g. 'discounted cash flow', 'valuation model') and file extensions are missing, and there is no natural 'Use when...' phrasing.

3 / 5

Distinctiveness Conflict Risk

It carves a clear financial-analysis niche with distinct triggers and minimal conflict risk, but overlaps slightly with the related /saas-health skill on metrics territory.

4 / 5

Total

15

/

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
alirezarezvani/claude-skills
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.