Household money

See every bill before it is due, cut unused subscriptions, plan your debt payoff, and track net worth.

Install the 6 skills below in order, one at a time. Each block is one complete install prompt. After the last skill, list each skill with its trigger phrases.

===== SKILL 1 OF 6: Bill Due Radar =====

Set up the "Bill Due Radar" workflow. Its full source is below.
Default schedule: Sunday at 18:00 local time. Ask me to confirm or
change this time before you create the recurring job. Once I
confirm, create the job. Tell me the job name and the confirmed
schedule when it is set up.

--- SOURCE ---
name: bill-due-radar
description: Weekly scan of the inbox for bills and statements; one list of what is due in the next 14 days, with amounts and due dates. Trigger phrases: "what bills are due", "check upcoming bills", "run bill radar".

schedule: weekly, Sunday at 18:00 local time (cron: 0 18 * * 0). Confirm the time with the user before the first scheduled run.

trigger: the scheduled time, or a manual "what bills are due" request.

steps:
  1. Search the inbox for billing statements, payment reminders, and autopay notices from the last 30 days, through the assistant's own connected accounts.
  2. For each biller, take the most recent statement: amount due and due date.
  3. Keep only bills due within the next 14 days. Drop anything already marked paid or covered by an autopay confirmation.
  4. Sort by due date, soonest first.
  5. Write the report in the Output shape and send it. If nothing is due, send the all-clear line and nothing else.

output:
  - One line per bill: biller, amount, due date, autopay status (yes / no / unknown)
  - Total due across the list
  - All-clear line when nothing is due: "Nothing due in the next 14 days."

rules:
  - Read only. Never pay a bill, open a payment page, or move money.
  - Never ask the user for banking logins or payment credentials.
  - If a statement is ambiguous about the amount or date, mark it "check manually" rather than guess.
  - Run only on the confirmed schedule or when asked.

===== END OF SKILL 1 OF 6 =====

===== SKILL 2 OF 6: Subscription Audit =====

Install the "Subscription Audit" workflow. Its full source is below. Create it at
~/workspace/skills/subscription-audit/SKILL.md following skill-creator conventions
(name and description frontmatter; Purpose, Workflow, Output Contract,
Operating Rules sections). Confirm it is installed and tell me the
trigger phrases. Then, as a separate step, propose the default schedule
(monthly, the 1st at 08:00 local time) and wait for me to confirm or change it before you create
any recurring job.

--- SOURCE ---
name: subscription-audit
description: Monthly recurring-charge audit from email receipts and a user-supplied bank
  export. Groups by merchant, estimates annual cost, and names what to cut with a reason.
  Read-only, never logs into a bank. Trigger phrases: audit my subscriptions, find recurring
  charges, what should I cancel.

schedule: monthly, the 1st at 08:00 local time (cron: 0 8 1 * *). Confirm the timing with
the user before the first scheduled run.

trigger: the scheduled date, or a manual "audit my subscriptions now" request, in either
case gated on the user supplying a bank export for the period.

inputs:
  - email receipts: read from the user's own connected email account, for the period since
    the last run.
  - bank export: a CSV or similar file the user exports from their bank or card portal and
    provides directly. The assistant never logs into a bank or card site itself, and never
    asks for banking credentials.

steps:
  1. At run time, ask the user for the bank export file covering the period since the last
     run, if it has not already been provided. If the user cannot supply it, end the run
     and report that the audit needs the export to proceed.
  2. Read email receipts from the connected account for the same period.
  3. Extract candidate recurring charges from both sources: same or near-identical amount,
     same merchant name, repeating on a roughly monthly, quarterly, or annual interval.
  4. Group extracted charges by merchant. Merge obvious name variants of the same merchant
     (e.g. "NETFLIX.COM" and "Netflix").
  5. For each merchant group, compute the billing interval, the per-charge amount, and the
     estimated annual cost (per-charge amount times charges per year).
  6. Rank merchant groups by estimated annual cost, highest first.
  7. For each group, decide a recommendation: keep, review, or cut. Attach one concrete
     reason to every "cut" or "review" call (e.g. "no matching login or usage found in
     receipts for 4 months", "duplicate of another active plan", "price rose 40% since
     last charge with no note of a plan change").
  8. Produce the report: total estimated annual recurring spend, then the ranked merchant
     table, then the cut list with reasons.

output: a report with three parts. First, total estimated annual recurring spend across all
groups. Second, a table of merchant, interval, amount, estimated annual cost, and
recommendation. Third, a short cut list naming each "cut" recommendation with its one-line
reason.

stop_conditions:
  - Stop and ask if the bank export is missing, unreadable, or covers the wrong period.
    Never guess at bank data from email receipts alone.
  - Never treat a single one-off charge as recurring; a merchant needs at least two charges
    at a consistent interval before it is grouped as a subscription.
  - Never recommend "cut" without a specific reason tied to the data.

operating_rules:
  - Read-only. Never logs into a bank, card portal, or any financial site.
  - Never asks the user for a bank password, card number, or any account credential.
  - Never cancels, pauses, or modifies any subscription. Recommendations only.
  - Never sends the bank export or its contents to any third party or outside service.
  - A run with no bank export provided produces no report; it asks for the file instead.

===== END OF SKILL 2 OF 6 =====

===== SKILL 3 OF 6: Bill Negotiation Script =====

Install the "Bill Negotiation Script" prompt pack. Its full
source is below. Save it to
~/workspace/prompts/bill-negotiation-script.md (create the
folder if needed). Then confirm it is installed and show me the
full text.

--- SOURCE ---
This prompt pack writes a call script for negotiating a lower bill.
Paste it into Muse along with your bill details.

> Write me a phone script for negotiating down my [cable /
> internet / insurance] bill. Current bill: [amount], paying
> for [plan details]. Include: (1) the opening line and the
> exact ask, (2) responses to the five most common pushbacks
> ("that's the best we can do", "let me transfer you",
> retention offers that aren't really discounts), (3) what
> competing offers to cite, look up current competitor pricing
> for my area if you can, and (4) when to ask for a supervisor
> and when to hang up and call back. Keep it firm but polite.
> No bluffs I can't back up.

===== END OF SKILL 3 OF 6 =====

===== SKILL 4 OF 6: Debt Payoff Planner =====

To install the Debt Payoff Planner skill, save the skill source below as ~/workspace/skills/debt-payoff-planner/SKILL.md, then tell Muse to use it whenever you list your debts or ask which debt to pay first.

--- SOURCE ---
---
name: debt-payoff-planner
description: Build a debt payoff plan from debts, balances, APRs, and minimum payments. Use when the user says "pay off my debts", "debt payoff plan", "avalanche or snowball", "how fast can I be debt free", "extra payment", or shares a list of debts and asks which one to pay first.
---

## Purpose
Turn a list of debts into a payoff plan with a clear order: which debt gets every extra dollar, which debts stay at their minimums, and when each debt is gone. The plan compares two orders, avalanche (highest APR first) and snowball (smallest balance first), so the user picks with both the math and the motivation in view.

## Workflow
1. Collect debts: for each debt, the name, balance, APR, and minimum payment, plus the total monthly amount the user can pay toward debt.
2. Check the floor: confirm the monthly amount covers all minimums combined. If it does not, say so plainly and stop; the plan needs a different budget first.
3. Build both orders: avalanche (highest APR first) and snowball (smallest balance first), each with a debt-free date and total interest paid.
4. Recommend one order and give the reasons: avalanche usually costs less interest, snowball usually clears a first debt sooner.
5. Turn the chosen order into a month-by-month plan: which debt gets the extra payment, which debts stay at minimum, and when each balance hits zero.
6. Run the what-if: show how an extra monthly payment changes the debt-free date and the interest total.
7. Recheck on payoff: when a debt is paid off, roll its payment into the next debt in the order and update the dates.

## Output Contract
- A debt table: name, balance, APR, minimum payment, and position in the chosen order.
- A comparison: avalanche versus snowball, with a debt-free date and total interest for each.
- A monthly plan for the chosen order, naming the target debt each month.
- An extra-payment what-if: the new debt-free date and the interest saved.
- No payment is made, moved, or scheduled. The plan is text the user reviews.

## Operating Rules
- Never ask for logins, card numbers, or account access. Work only from numbers the user types in.
- Never move money, schedule a payment, or contact a lender.
- Never invent a balance, APR, or minimum. If a figure is missing, ask for it or mark the plan as partial.
- Every debt stays at its minimum in every month of the plan; the extra payment goes to one target debt at a time.
- Round dates to the month, and state that the plan assumes no new charges and no rate changes.
- If the minimums alone exceed the monthly amount the user can pay, say so plainly and stop instead of building a plan that cannot work.

===== END OF SKILL 4 OF 6 =====

===== SKILL 5 OF 6: Net Worth Snapshot =====

Set up the "Net Worth Snapshot" workflow. Its full source is
below. Default schedule: first of each month at 09:00 local
time. Ask me to confirm or change this time before you create
the recurring job. Once I confirm, create the job. Tell me the
job name and the confirmed schedule when it is set up.

--- SOURCE ---
name: net-worth-snapshot
description: Monthly net worth snapshot, every account in one page, with the month-over-month change and what moved. Trigger phrases: "net worth snapshot", "what is my net worth", "monthly money summary".

schedule: monthly, first of the month at 09:00 local time. Confirm the time with the user before the first scheduled run.

trigger: the scheduled time, or a manual "net worth snapshot" request.

steps:
  1. Pull balances from the user's connected accounts: checking, savings, investments, retirement, debts.
  2. Compute total assets, total liabilities, net worth.
  3. Compare against last month's snapshot. Note the change in dollars and percent, and which accounts moved the most.
  4. One line per account: name, balance, change. Then the totals.
  5. Write the snapshot in the Output shape and send it. Save it for next month's comparison.

output:
  - Net worth: total, with month-over-month change
  - Assets: one line per account with balance and change
  - Liabilities: one line per account with balance and change
  - What moved: the 2-3 biggest movers, one line each

rules:
  - Read only. Never move money or change anything.
  - Balances come from connected accounts, not estimates. If an account can't be read, list it as "unavailable" rather than guessing.
  - Keep the first snapshot as the baseline even if it's partial; note what's missing.
  - Run only on the confirmed schedule or when asked.

===== END OF SKILL 5 OF 6 =====

===== SKILL 6 OF 6: Unclaimed Money Scout =====

Install the "Unclaimed Money Scout" skill. Its full source is
below. Create it at
~/workspace/skills/unclaimed-money-scout/SKILL.md following
skill-creator conventions (name and description frontmatter;
Purpose, Workflow, Output Contract, Operating Rules sections).
Then confirm it is installed and tell me the trigger phrases.

--- SOURCE ---
---
name: unclaimed-money-scout
description: Search class-action settlements and state unclaimed-property databases for money you may be owed. Trigger phrases: "am I owed any settlement money", "check unclaimed property for me", "find money owed to me".
---
# Purpose

People leave money on the table every year: class-action
settlements they never heard about, forgotten security deposits,
uncashed checks sitting in state unclaimed-property funds. This
skill checks the public sources and points at what might be
yours.

# Workflow

1. Ask the user for: full name (and past spellings or maiden
   name if relevant), and every state they have lived or worked
   in. Nothing else. Never ask for SSN, bank details, or
   passwords.
2. Check these public sources:
   - State unclaimed property: missingmoney.com (multi-state
     NAUPA search) and each relevant state's official .gov
     unclaimed-property site.
   - Open class-action settlements: topclassactions.com and
     classaction.org: filter to settlements still accepting
     claims, and match by the user's purchase or membership
     history (ask what products, services, or employers apply).
   - FTC refunds: ftc.gov enforcement refunds page for
     government-administered payouts.
3. For each potential match, report: what it is, the estimated
   payout range if published, the claim deadline, and the
   official claim link.
4. Report in the Output Contract shape.

# Output Contract

- Checked: the sources searched and the name/states used
- Potential matches: one line each, what, payout range,
  deadline, official claim link
- Long shots: settlements that might apply but need more info
  from the user
- Nothing found: say so in one line, and suggest re-checking
  yearly

# Operating Rules

- Public sources only. Link to official claim sites (.gov or
  the settlement administrator), never to aggregator sign-up
  funnels.
- Never file a claim on the user's behalf. The user files their
  own claims.
- Never ask for or accept SSN, bank account numbers, or
  passwords. If the user offers them, the skill refuses and
  explains why.
- Payout ranges come from the published settlement terms, not
  from anecdotes. If no range is published, say so.
- Re-checking is a yearly habit, not a weekly one. Say that.

===== END OF SKILL 6 OF 6 =====

Ready to copy.

Before you install

A shared skill carries somebody else's instructions. Read the source before you install it.
Never paste an API key, password, or token into anything a skill asks for. Legitimate skills use Muse's own secure flows.
Installing copies the setup into your own environment. It gives the author nothing.

Skills in this pack

Bill Due Radar
Weekly inbox scan; one list of every bill due in the next 14 days.
Tested in MuseworkflowMoney & financeinstructionsworkflowschedule
by Muse Skills editors · Written for this directory
ViewSet up the "Bill Due Radar" workflow. Its full source is below. Default schedule: Sunday at 18:00 local time. Ask me to confirm or change this time before you create the recurring job. Once I confirm, create the job. Tell me the job name and the confirmed schedule when it is set up. --- SOURCE --- name: bill-due-radar description: Weekly scan of the inbox for bills and statements; one list of what is due in the next 14 days, with amounts and due dates. Trigger phrases: "what bills are due", "check upcoming bills", "run bill radar". schedule: weekly, Sunday at 18:00 local time (cron: 0 18 * * 0). Confirm the time with the user before the first scheduled run. trigger: the scheduled time, or a manual "what bills are due" request. steps: 1. Search the inbox for billing statements, payment reminders, and autopay notices from the last 30 days, through the assistant's own connected accounts. 2. For each biller, take the most recent statement: amount due and due date. 3. Keep only bills due within the next 14 days. Drop anything already marked paid or covered by an autopay confirmation. 4. Sort by due date, soonest first. 5. Write the report in the Output shape and send it. If nothing is due, send the all-clear line and nothing else. output: - One line per bill: biller, amount, due date, autopay status (yes / no / unknown) - Total due across the list - All-clear line when nothing is due: "Nothing due in the next 14 days." rules: - Read only. Never pay a bill, open a payment page, or move money. - Never ask the user for banking logins or payment credentials. - If a statement is ambiguous about the amount or date, mark it "check manually" rather than guess. - Run only on the confirmed schedule or when asked.
Subscription Audit
Finds recurring charges in your email receipts and bank exports, then names what to cut.
Tested in MuseworkflowMoney & financescheduleworkflowmerchant groupingcut list
by Muse Skills editors · Written for this directory
ViewInstall the "Subscription Audit" workflow. Its full source is below. Create it at ~/workspace/skills/subscription-audit/SKILL.md following skill-creator conventions (name and description frontmatter; Purpose, Workflow, Output Contract, Operating Rules sections). Confirm it is installed and tell me the trigger phrases. Then, as a separate step, propose the default schedule (monthly, the 1st at 08:00 local time) and wait for me to confirm or change it before you create any recurring job. --- SOURCE --- name: subscription-audit description: Monthly recurring-charge audit from email receipts and a user-supplied bank export. Groups by merchant, estimates annual cost, and names what to cut with a reason. Read-only, never logs into a bank. Trigger phrases: audit my subscriptions, find recurring charges, what should I cancel. schedule: monthly, the 1st at 08:00 local time (cron: 0 8 1 * *). Confirm the timing with the user before the first scheduled run. trigger: the scheduled date, or a manual "audit my subscriptions now" request, in either case gated on the user supplying a bank export for the period. inputs: - email receipts: read from the user's own connected email account, for the period since the last run. - bank export: a CSV or similar file the user exports from their bank or card portal and provides directly. The assistant never logs into a bank or card site itself, and never asks for banking credentials. steps: 1. At run time, ask the user for the bank export file covering the period since the last run, if it has not already been provided. If the user cannot supply it, end the run and report that the audit needs the export to proceed. 2. Read email receipts from the connected account for the same period. 3. Extract candidate recurring charges from both sources: same or near-identical amount, same merchant name, repeating on a roughly monthly, quarterly, or annual interval. 4. Group extracted charges by merchant. Merge obvious name variants of the same merchant (e.g. "NETFLIX.COM" and "Netflix"). 5. For each merchant group, compute the billing interval, the per-charge amount, and the estimated annual cost (per-charge amount times charges per year). 6. Rank merchant groups by estimated annual cost, highest first. 7. For each group, decide a recommendation: keep, review, or cut. Attach one concrete reason to every "cut" or "review" call (e.g. "no matching login or usage found in receipts for 4 months", "duplicate of another active plan", "price rose 40% since last charge with no note of a plan change"). 8. Produce the report: total estimated annual recurring spend, then the ranked merchant table, then the cut list with reasons. output: a report with three parts. First, total estimated annual recurring spend across all groups. Second, a table of merchant, interval, amount, estimated annual cost, and recommendation. Third, a short cut list naming each "cut" recommendation with its one-line reason. stop_conditions: - Stop and ask if the bank export is missing, unreadable, or covers the wrong period. Never guess at bank data from email receipts alone. - Never treat a single one-off charge as recurring; a merchant needs at least two charges at a consistent interval before it is grouped as a subscription. - Never recommend "cut" without a specific reason tied to the data. operating_rules: - Read-only. Never logs into a bank, card portal, or any financial site. - Never asks the user for a bank password, card number, or any account credential. - Never cancels, pauses, or modifies any subscription. Recommendations only. - Never sends the bank export or its contents to any third party or outside service. - A run with no bank export provided produces no report; it asks for the file instead.
Bill Negotiation Script
A call script to lower cable, internet, and insurance bills, with replies to pushback.
Tested in Museprompt packMoney & financeprompt-text
by Muse Skills editors · Written for this directory
ViewInstall the "Bill Negotiation Script" prompt pack. Its full source is below. Save it to ~/workspace/prompts/bill-negotiation-script.md (create the folder if needed). Then confirm it is installed and show me the full text. --- SOURCE --- This prompt pack writes a call script for negotiating a lower bill. Paste it into Muse along with your bill details. > Write me a phone script for negotiating down my [cable / > internet / insurance] bill. Current bill: [amount], paying > for [plan details]. Include: (1) the opening line and the > exact ask, (2) responses to the five most common pushbacks > ("that's the best we can do", "let me transfer you", > retention offers that aren't really discounts), (3) what > competing offers to cite, look up current competitor pricing > for my area if you can, and (4) when to ask for a supervisor > and when to hang up and call back. Keep it firm but polite. > No bluffs I can't back up.
Debt Payoff Planner
Turns your debts, APRs, and minimums into a payoff order and a monthly plan.
skillMoney & financePayoff order by avalanche or snowballMonthly payment plan with a debt-free dateInterest comparison between payoff ordersWhat-if check for an extra monthly paymentPayoff plan template
by Muse Skills editors · Written for this directory
ViewTo install the Debt Payoff Planner skill, save the skill source below as ~/workspace/skills/debt-payoff-planner/SKILL.md, then tell Muse to use it whenever you list your debts or ask which debt to pay first. --- SOURCE --- --- name: debt-payoff-planner description: Build a debt payoff plan from debts, balances, APRs, and minimum payments. Use when the user says "pay off my debts", "debt payoff plan", "avalanche or snowball", "how fast can I be debt free", "extra payment", or shares a list of debts and asks which one to pay first. --- ## Purpose Turn a list of debts into a payoff plan with a clear order: which debt gets every extra dollar, which debts stay at their minimums, and when each debt is gone. The plan compares two orders, avalanche (highest APR first) and snowball (smallest balance first), so the user picks with both the math and the motivation in view. ## Workflow 1. Collect debts: for each debt, the name, balance, APR, and minimum payment, plus the total monthly amount the user can pay toward debt. 2. Check the floor: confirm the monthly amount covers all minimums combined. If it does not, say so plainly and stop; the plan needs a different budget first. 3. Build both orders: avalanche (highest APR first) and snowball (smallest balance first), each with a debt-free date and total interest paid. 4. Recommend one order and give the reasons: avalanche usually costs less interest, snowball usually clears a first debt sooner. 5. Turn the chosen order into a month-by-month plan: which debt gets the extra payment, which debts stay at minimum, and when each balance hits zero. 6. Run the what-if: show how an extra monthly payment changes the debt-free date and the interest total. 7. Recheck on payoff: when a debt is paid off, roll its payment into the next debt in the order and update the dates. ## Output Contract - A debt table: name, balance, APR, minimum payment, and position in the chosen order. - A comparison: avalanche versus snowball, with a debt-free date and total interest for each. - A monthly plan for the chosen order, naming the target debt each month. - An extra-payment what-if: the new debt-free date and the interest saved. - No payment is made, moved, or scheduled. The plan is text the user reviews. ## Operating Rules - Never ask for logins, card numbers, or account access. Work only from numbers the user types in. - Never move money, schedule a payment, or contact a lender. - Never invent a balance, APR, or minimum. If a figure is missing, ask for it or mark the plan as partial. - Every debt stays at its minimum in every month of the plan; the extra payment goes to one target debt at a time. - Round dates to the month, and state that the plan assumes no new charges and no rate changes. - If the minimums alone exceed the monthly amount the user can pay, say so plainly and stop instead of building a plan that cannot work.
Net Worth Snapshot
Monthly one-page net worth with the month-over-month change.
Tested in MuseworkflowMoney & financeinstructionsworkflowschedule
by Muse Skills editors · Written for this directory
ViewSet up the "Net Worth Snapshot" workflow. Its full source is below. Default schedule: first of each month at 09:00 local time. Ask me to confirm or change this time before you create the recurring job. Once I confirm, create the job. Tell me the job name and the confirmed schedule when it is set up. --- SOURCE --- name: net-worth-snapshot description: Monthly net worth snapshot, every account in one page, with the month-over-month change and what moved. Trigger phrases: "net worth snapshot", "what is my net worth", "monthly money summary". schedule: monthly, first of the month at 09:00 local time. Confirm the time with the user before the first scheduled run. trigger: the scheduled time, or a manual "net worth snapshot" request. steps: 1. Pull balances from the user's connected accounts: checking, savings, investments, retirement, debts. 2. Compute total assets, total liabilities, net worth. 3. Compare against last month's snapshot. Note the change in dollars and percent, and which accounts moved the most. 4. One line per account: name, balance, change. Then the totals. 5. Write the snapshot in the Output shape and send it. Save it for next month's comparison. output: - Net worth: total, with month-over-month change - Assets: one line per account with balance and change - Liabilities: one line per account with balance and change - What moved: the 2-3 biggest movers, one line each rules: - Read only. Never move money or change anything. - Balances come from connected accounts, not estimates. If an account can't be read, list it as "unavailable" rather than guessing. - Keep the first snapshot as the baseline even if it's partial; note what's missing. - Run only on the confirmed schedule or when asked.
Unclaimed Money Scout
Checks class-action settlements and unclaimed property for money owed to you.
Tested in MuseskillMoney & financeinstructionsworkflowclaim-links
by Muse Skills editors · Written for this directory
ViewInstall the "Unclaimed Money Scout" skill. Its full source is below. Create it at ~/workspace/skills/unclaimed-money-scout/SKILL.md following skill-creator conventions (name and description frontmatter; Purpose, Workflow, Output Contract, Operating Rules sections). Then confirm it is installed and tell me the trigger phrases. --- SOURCE --- --- name: unclaimed-money-scout description: Search class-action settlements and state unclaimed-property databases for money you may be owed. Trigger phrases: "am I owed any settlement money", "check unclaimed property for me", "find money owed to me". --- # Purpose People leave money on the table every year: class-action settlements they never heard about, forgotten security deposits, uncashed checks sitting in state unclaimed-property funds. This skill checks the public sources and points at what might be yours. # Workflow 1. Ask the user for: full name (and past spellings or maiden name if relevant), and every state they have lived or worked in. Nothing else. Never ask for SSN, bank details, or passwords. 2. Check these public sources: - State unclaimed property: missingmoney.com (multi-state NAUPA search) and each relevant state's official .gov unclaimed-property site. - Open class-action settlements: topclassactions.com and classaction.org: filter to settlements still accepting claims, and match by the user's purchase or membership history (ask what products, services, or employers apply). - FTC refunds: ftc.gov enforcement refunds page for government-administered payouts. 3. For each potential match, report: what it is, the estimated payout range if published, the claim deadline, and the official claim link. 4. Report in the Output Contract shape. # Output Contract - Checked: the sources searched and the name/states used - Potential matches: one line each, what, payout range, deadline, official claim link - Long shots: settlements that might apply but need more info from the user - Nothing found: say so in one line, and suggest re-checking yearly # Operating Rules - Public sources only. Link to official claim sites (.gov or the settlement administrator), never to aggregator sign-up funnels. - Never file a claim on the user's behalf. The user files their own claims. - Never ask for or accept SSN, bank account numbers, or passwords. If the user offers them, the skill refuses and explains why. - Payout ranges come from the published settlement terms, not from anecdotes. If no range is published, say so. - Re-checking is a yearly habit, not a weekly one. Say that.