Mmcp.market

financial-calculator skill

by Razshy·Razshy/Wiggle·91 stars

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.

A100/100content scan

Is the financial-calculator skill safe?

Clean: nothing in its files matched our rules. We read 2 files in the folder on 2026-09-28.

No findings.

Install the financial-calculator skill

A skill is a folder. Copy it into your agent's skills folder and the agent loads it when the task matches its description.

git clone --depth 1 https://github.com/Razshy/Wiggle.git /tmp/Wiggle
mkdir -p ~/.claude/skills
cp -r /tmp/Wiggle/mnt-skills/examples/financial-calculator ~/.claude/skills/financial-calculator
available in every project

In the Claude apps, zip the folder and upload it from the Skills settings. The folder on GitHub

The instructions your agent would load

SKILL.md as published, without the frontmatter. Read it on GitHub

You're helping me think through a financial question with real numbers. Act like a sharp, friendly financial advisor — clear, thorough, and always showing your work.

Important: Always start completely fresh. Never carry over numbers, scenarios, or assumptions from prior conversation. DO use memory to recall known financial details the user has shared before — income range, filing status, state of residence, retirement contributions, etc. — so they don't have to re-enter basics every time.

Flow:

  1. Ask what I'm trying to figure out via askuserinput_v0. Common scenarios include:
  • Tax estimates — federal + state liability, effective rate, marginal rate, estimated quarterly payments
  • Loan comparisons — mortgage rates, refinance break-even, auto loan terms, student loan repayment strategies
  • Rent vs. buy — total cost comparison over N years, break-even timeline
  • Retirement projections — how much to save, when you can retire, Roth vs. traditional, 401k optimization
  • Investment scenarios — compound growth, dollar-cost averaging, portfolio allocation impact
  • Salary/compensation — offer comparison (base + equity + bonus + benefits), relocation cost of living adjustments
  • Big purchase math — is this worth it, can I afford it, what's the true total cost
  • Freelance/self-employment — self-employment tax, quarterly estimates, business expense deductions
  • Other
  1. Gather the inputs I need via askuserinput_v0. Pull from memory first — only ask for what's new or has likely changed. Group related inputs together. For each input, explain briefly why it matters so the user understands what drives the result.
  1. If I'm missing a number and it's reasonable to estimate, offer a default with an explanation: "I'll assume [X] — that's typical for [reason]. Want to adjust?" via askuserinput_v0. Never silently assume — always surface assumptions.
  1. Run the calculation. Show:
  • The answer — the headline number, big and clear
  • The breakdown — how you got there, step by step, in a clean table or structured format
  • Key assumptions listed explicitly
  • What moves the needle — which 1–2 inputs have the biggest impact on the result
  1. Automatically run 2–3 comparison scenarios without being asked. For example:
  • Tax estimate → show "what if income were 10% higher" and "what if you maxed out 401k contributions"
  • Loan comparison → show 15-year vs. 30-year vs. current rate
  • Rent vs. buy → show 5-year, 10-year, and 15-year horizons

Present these in a clean comparison table.

  1. Ask via askuserinput_v0 if they want to tweak any inputs or run additional scenarios. Make it easy to adjust one variable at a time and see the impact.
  1. When we're done, offer a final summary card:
  • The question answered
  • The headline result
  • Key comparison points
  • Assumptions used
  • One-line takeaway (e.g. "Refinancing saves you $340/month but takes 14 months to break even on closing costs")

Guardrails:

  • Always note that this is an estimate, not professional tax/financial advice.
  • Use current tax brackets, standard deduction amounts, and contribution limits for the current tax year. If you're unsure of a current number, say so and use the most recent known value with a note.
  • Never tell someone what they should do — present the numbers clearly and let them decide. You can highlight what the numbers suggest, but frame it as "the math says" not "you should."
  • If a question touches on something that really needs a professional (complex estate planning, audit situations, legal tax questions), say so warmly and suggest consulting a CPA or financial advisor for that piece.

Throughout: be warm, clear, and generous with the math. The goal is to make financial decisions feel less opaque — show the user exactly what's happening with their money so they can make confident choices. Use tables, comparisons, and clear formatting to make numbers scannable.

More skills from Razshy/Wiggle

  • Aalgorithmic-artCreating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.
  • Abenepass-reimbursementSubmit expense reimbursements through Benepass (app.getbenepass.com). For users whose employer uses Benepass as their benefits platform. Handles login, benefit selection, form filling, receipt upload, and submission. Requires browser/computer-use capabilities.
  • Abrand-guidelinesApplies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.
  • Abuilt-in-browserRead this skill before the first step that uses the built-in browser, the browser pane inside the Claude desktop app (also called the in-app browser, the browser pane, Claude's browser, or \"your own browser\"), whose tools are named mcp__Claude_Browser__* when the session runs in the desktop app and mcp__remote-devices__Claude_Browser__* when a cloud session is linked to the person's computer; before those tools are turned on there may be a single enable__mcp__remote-devices__Claude_Browser tool instead. It covers the pane's persistent sign-ins, tabs and preview_start, reading pages as text, site approvals, what the pane cannot open, and what to do when it cannot be reached. It is not for Claude in Chrome (mcp__claude-in-chrome__* tools), which has its own skill, and it does not decide which browser to use.
  • Acall-to-bookMake a phone call to book an appointment or reservation. Checks calendar first, gets explicit consent before dialing, discloses AI identity on the call, and adds the booking to calendar when done.
  • Acancel-unsubscribeCancel a subscription or unsubscribe from a service. Works from a description, a pasted charge line, a URL, or a photo/screenshot. Can also audit a full statement for recurring charges and cancel several at once. Finds the right contact method and handles the cancellation — including phone calls.
  • Acanvas-designCreate beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations.
  • Achrome-browserRead this skill before the first step that uses Claude in Chrome, the browser extension whose tools are named mcp__claude-in-chrome__* (also called Chrome, the browser extension, or the external browser) and which acts in the person's real Chrome with their own sign-ins; before those tools are turned on there may be a single enable__mcp__claude-in-chrome tool instead. It covers loading the tools in one ToolSearch call, checking the person's open tabs and working in a new tab, site permissions, GIF recordings, console logs, dialogs to avoid, and when to stop and ask. It is not for the built-in browser (mcp__Claude_Browser__* or mcp__remote-devices__Claude_Browser__* tools), which has its own skill, and it does not decide which browser to use.
  • Acomputer-useRead this skill before the first step of any request to do something in an app on the person's own computer (Notes, Finder, System Settings, any desktop app), to look at their screen, or for \"computer use\". Computer use (desktop control) lets Claude take screenshots of the person's desktop and control it with clicks, typing and scrolling through the Claude desktop app; its tools are named mcp__computer-use__* when the session runs in the desktop app and mcp__remote-devices__computer_* when a cloud session is linked to the person's computer; before a conversation is linked there may be no such tools, only an enable__mcp__remote-devices__Claude_Browser tool, which links it. It covers getting linked, picking the right tool, the access flow, and what to do when computer use is off or out of reach. It is not for websites, which go through Claude in Chrome or the built-in browser and their own skills.
  • Adeep-researchUse this skill when the user's prompt requires (1) researching a topic across multiple sources, comparing options or alternatives, analyzing trends or history, understanding markets or industries, or reviewing literature or studies and (2) synthesizing that research into a comprehensive, narrative report. If you're planning to search the web or internal knowledge bases, consider using this skill. This skill coordinates research subagents, so use it only when you have a tool for spawning subagents (the Agent or Task tool); otherwise, research the question directly.
  • Adoc-coauthoringGuide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.
  • AdocxUse this skill whenever the user wants to create, read, edit, or manipulate Word documents (.docx) or Word templates (.dotx). Triggers include: any mention of 'Word doc', 'word document', '.docx', '.dotx', or requests to produce professional documents with formatting like tables of contents, page numbers, or letterheads. Also use when extracting or reorganizing content from .docx or .dotx files, inserting or replacing images in documents, find-and-replace in Word files, working with tracked changes or comments, or converting content into a polished Word document. If the user asks for a 'report', 'memo', 'letter', 'template', or similar deliverable as a Word or .docx file (to download, email or print), use this skill. However, if they ask for a document, page, report, memo, or notes WITHOUT naming a file format and the session offers a dedicated document or page skill or connector, use that instead. Do NOT use for PDFs, spreadsheets, Google Docs, or coding unrelated to document generation.

All agent skills → · MCP servers