financial-calculator
Run financial calculations and scenario comparisons — tax estimates, loan comparisons, retirement projections, rent vs. buy, investment scenarios, and more. Pure math, no accounts or logins needed.
78
72%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./examples/financial-calculator/SKILL.mdQuality
Discovery
82%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 is a strong description with excellent specificity and natural trigger terms covering a wide range of financial calculation scenarios. The main weakness is the absence of an explicit 'Use when...' clause, which would help Claude know precisely when to select this skill. The scope clarification ('Pure math, no accounts or logins needed') is a nice touch for distinctiveness.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about financial math, budgeting calculations, comparing financial options, or running numeric scenarios involving money.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: tax estimates, loan comparisons, retirement projections, rent vs. buy, investment scenarios. Also clarifies scope with 'Pure math, no accounts or logins needed.' | 3 / 3 |
Completeness | Clearly answers 'what does this do' with specific financial calculation types, but lacks an explicit 'Use when...' clause or equivalent trigger guidance. The 'when' is only implied by the listed capabilities. | 2 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'tax estimates', 'loan comparisons', 'retirement projections', 'rent vs. buy', 'investment scenarios', 'financial calculations'. These are terms users naturally use when seeking financial computation help. | 3 / 3 |
Distinctiveness Conflict Risk | The combination of financial calculations with specific scenario types (tax, loan, retirement, rent vs. buy) and the clarification 'Pure math, no accounts or logins needed' creates a clear niche that is unlikely to conflict with other skills like general math or account-based financial tools. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
62%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides a well-structured conversational workflow for financial calculations with good scenario coverage and clear guardrails. Its main weakness is the lack of concrete computational content — no formulas, tax bracket tables, or calculation templates that would make Claude's outputs more reliable and consistent. The tone-coaching and motivational language adds tokens without adding value.
Suggestions
Add concrete formulas and calculation templates for the most common scenarios (e.g., amortization formula, compound interest, effective tax rate calculation with current bracket tables) to make the skill truly actionable rather than relying on Claude's general knowledge.
Extract current tax brackets, standard deductions, contribution limits, and other reference data into a separate REFERENCE.md file that can be updated annually, improving both progressive disclosure and maintainability.
Remove tone-coaching sentences like 'be warm, clear, and generous with the math' and 'make financial decisions feel less opaque' — Claude understands tone instructions implicitly and these consume tokens without improving output quality.
Add a concrete worked example showing a complete calculation (e.g., a sample tax estimate with real numbers) so Claude has a template for output format and level of detail.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is moderately efficient but includes unnecessary filler phrases ('be warm, clear, and generous with the math', 'make financial decisions feel less opaque') and some explanatory padding that Claude doesn't need. The scenario list is useful but could be tighter. The tone-coaching sentences at the end are largely redundant. | 2 / 3 |
Actionability | The workflow is clearly described with specific steps and good examples of scenario types, but there are no concrete formulas, code snippets, or executable calculation templates. For a financial calculation skill, providing actual formulas (e.g., amortization, compound interest, tax bracket math) would make this significantly more actionable. The guidance is specific in structure but abstract in computation. | 2 / 3 |
Workflow Clarity | The 7-step flow is clearly sequenced with logical progression: identify question → gather inputs → handle missing data with explicit assumptions → calculate with structured output → automatic comparisons → iterate → summarize. The assumption-surfacing step (step 3) and the iteration loop (step 6) serve as validation checkpoints. The workflow is well-defined for a conversational, non-destructive task. | 3 / 3 |
Progressive Disclosure | The content is a single monolithic file with no references to supporting materials. Given the breadth of scenarios covered (tax, loans, retirement, investments, etc.), this would benefit from separate reference files for tax brackets, common formulas, or scenario-specific templates. However, for a conversational skill without bundle files, the inline organization with clear sections is adequate but not optimal. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- douglasvought/wiggle-skills
- Commit
b27906e
- 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.