finance-advisor
Expert financial analyst and controller specializing in financial planning, budget management, and business performance analysis. Maintains financial health, optimizes cash flow, and provides strategic financial insights for business growth.
31
14%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./finance_advisor/skills/SKILL.mdQuality
Discovery
14%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This description reads like a job posting or LinkedIn summary rather than a functional skill description. It relies heavily on abstract buzzwords and lacks concrete actions, explicit trigger conditions, and distinctive scope boundaries. The first-person framing ('Expert financial analyst') further reduces its effectiveness as a skill selector.
Suggestions
Add a 'Use when...' clause with explicit triggers, e.g., 'Use when the user asks about budgets, financial forecasts, P&L statements, cash flow analysis, or expense tracking.'
Replace vague phrases like 'maintains financial health' and 'strategic financial insights' with concrete actions such as 'Creates budget templates, generates financial forecasts, analyzes profit and loss statements, tracks expenses against budgets.'
Rewrite in third person action voice (e.g., 'Performs financial planning and budget analysis') instead of the current role-description style ('Expert financial analyst specializing in...').
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague, buzzword-heavy language like 'maintains financial health', 'optimizes cash flow', and 'strategic financial insights' without listing concrete actions. No specific operations (e.g., 'create budget spreadsheets', 'generate P&L reports') are mentioned. | 1 / 3 |
Completeness | The description loosely addresses 'what' but in very abstract terms, and completely lacks any 'when' guidance or 'Use when...' clause. There are no explicit triggers telling Claude when to select this skill. | 1 / 3 |
Trigger Term Quality | Contains some relevant domain keywords like 'financial planning', 'budget management', 'cash flow', and 'business performance analysis' that users might mention, but lacks common variations and specific trigger terms like 'forecast', 'revenue', 'expenses', 'P&L', 'balance sheet'. | 2 / 3 |
Distinctiveness Conflict Risk | The description is extremely broad and could overlap with any finance-related, data analysis, or business strategy skill. Terms like 'business growth' and 'strategic insights' are generic enough to conflict with many other skills. | 1 / 3 |
Total | 5 / 12 Passed |
Implementation
14%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is an overly verbose, monolithic document that reads more like a financial management textbook outline than actionable guidance for Claude. It explains concepts Claude already understands, includes incomplete code with undefined methods, provides vague workflow steps without validation checkpoints, and dumps everything into a single massive file. The report template alone consumes significant token budget while being generic boilerplate that Claude could generate on its own.
Suggestions
Cut the content by 70%+: Remove all explanatory bullet points about basic financial concepts (budgeting, cash flow, compliance) and focus only on specific methodologies, thresholds, or patterns unique to this skill's context.
Complete the code examples by implementing all referenced but undefined methods (get_current_cash_position, calculate_seasonal_factor, assess_investment_risk, get_growth_factor) or remove them entirely.
Replace the vague 4-step workflow with concrete, sequenced steps that include explicit validation checkpoints (e.g., 'Verify data reconciliation before proceeding to budget development').
Extract the report template and code examples into separate referenced files (e.g., REPORT_TEMPLATE.md, CASH_FLOW.py, INVESTMENT_ANALYSIS.py) and keep SKILL.md as a concise overview with clear navigation links.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose at ~300+ lines. Explains basic financial concepts Claude already knows (what NPV is, what cash flow means, what budget variance is). The report template alone is massive boilerplate. Bullet-point lists repeat obvious financial management concepts without adding novel, specific guidance. | 1 / 3 |
Actionability | Contains some executable Python and SQL code (CashFlowManager, InvestmentAnalyzer, budget query), which is positive. However, much of the skill is vague bullet points ('Develop pricing strategies based on cost analysis'), the workflow Step 1 is just bash comments with no actual commands, and the code examples have undefined methods (get_current_cash_position, calculate_seasonal_factor, assess_investment_risk) making them incomplete. | 2 / 3 |
Workflow Clarity | The 4-step workflow is extremely vague with no validation checkpoints. Step 1 is literally bash comments saying 'validate financial data' without any concrete steps. There are no feedback loops, no error recovery, and no explicit validation gates between steps. For a skill involving financial accuracy and compliance, this is critically insufficient. | 1 / 3 |
Progressive Disclosure | Monolithic wall of text with everything inline. The massive report template, multiple full Python classes, and SQL queries are all embedded in a single file with no references to external files. The final line vaguely references 'core training' which is meaningless. Content that should be in separate reference files (report template, code examples) bloats the main skill. | 1 / 3 |
Total | 5 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- OpenRoster-ai/awesome-openroster
- Commit
09aef5d
- 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.