Update to Mercury

{
  "description": "Review business or personal Mercury cash balances and cash flow. Analyze business burn and runway, or personal cash buffers and expense coverage using the personal-finance definitions. Use for cash questions, not detailed spend or duplicate reviews.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 387
    },
    {
      "relative_path": "references/metric-definitions.md",
      "size_in_bytes": 2593
    }
  ],
  "name": "mercury-cash-runway",
  "skill_md_contents": "---\nname: mercury-cash-runway\ndescription: Review business or personal Mercury cash balances and cash flow. Analyze business burn and runway, or personal cash buffers and expense coverage using the personal-finance definitions. Use for cash questions, not detailed spend or duplicate reviews.\n---\n\n# Mercury Cash and Runway\n\n## Personal and household use\n\nFor personal cash flow, emergency funds, savings goals, or \"how long will my money last,\" read `../mercury-personal-finance/SKILL.md` and use its personal definitions. Keep business operating runway distinct from expense coverage without income and cash depletion with income. Do not label household spending operating burn. A current balance question still needs no transaction history.\n\nUse only accounts in the selected personal, household, or business scope. Treasury is included only when requested or part of requested total liquidity and actually accessible. Missing products are a coverage limit, not zero balances.\n\n\nBuild a read-only cash and runway report. Separate observed data from classifications and scenarios.\n\nRead `../mercury-mcp-shared/SKILL.md` before retrieval. In `references/metric-definitions.md`, read liquidity for balance questions and only the other definitions required for the requested calculations.\n\n## Set the period\n\nUse the current date supplied by the host as the as-of date. Match the period to the request:\n\n- For current deposit balance or liquidity, retrieve current balances. Do not retrieve transactions.\n- For burn or runway, use the user-provided period. If the user does not provide one, use the trailing three complete calendar months.\n- For cash history or a monthly cash report, use the user-provided period. If the user does not provide one, use the last six complete calendar months.\n- Retrieve an additional comparison period only when the user requests a comparison.\n\nIf the live transaction call limit prevents a complete result, do not calculate from partial data. Ask for a narrower period.\n\n## Retrieve complete data\n\nInspect the live schemas. Use account tools for current deposit balances. Use Treasury tools only when Treasury is in scope. Treasury is in scope when the user asks for Treasury, total Mercury liquidity, or cash across Mercury. Use the transaction-list tool only when the requested result needs transaction history.\n\nUse Treasury transaction data when it is needed to confirm a deposit-to-Treasury transfer or explain a Treasury balance change. Use credit tools only for a separate credit-capacity section that the user requests. Credit is not liquidity.\n\nUse statements only when the user requests a month-end tie-out or transaction data cannot support it.\n\n## Reconcile the source\n\nCreate minimized account and transaction tables. Remove account and routing numbers before calculation.\n\nExclude failed, cancelled, reversed, and blocked activity. Exclude confirmed internal transfers from both inflow and outflow. Keep possible internal transfers in the primary cash-flow result and show a sensitivity result when material.\n\nDo not add a Treasury balance to deposit balances until the live result shows that it is separate and available. Do not infer restricted cash status. State when the MCP does not return this status.\n\nReport the account count and balance scope. When transactions are used, also report the page count, transaction count, exact filters, returned dates, statuses, missing rates, and exclusion reconciliation.\n\n## Calculate actuals with code\n\nUse exact programmatic arithmetic. Apply `references/metric-definitions.md`.\n\nCalculate only the measures required for the request. For each required complete month, calculate external inflow, external outflow, net cash flow, and unadjusted burn. Calculate adjusted operating burn only when the request needs it and evidence supports each classification. Do not remove a flow only because it is large or unusual.\n\nFor the as-of date, show available deposit balance, current deposit balance when different, separately verified Treasury balance, identified unavailable cash, and total available liquidity. Keep currencies separate.\n\n## Calculate runway\n\nUse the runway method that the user requests. If the user does not select a method, use the trailing three-month average. Add a most-recent-month or six-month method only when the user asks for a comparison or sensitivity result.\n\nIf burn is zero, state `cash-flow positive in the selected period`. Do not report infinite runway. If fewer than three complete months exist, label runway low confidence.\n\n## Explain drivers and scenarios\n\nExplain drivers only when the user requests them or when a material flow affects the selected burn result. Use the smallest supporting set of counterparties, shares, changes, and evidenced one-time flows. Cite abbreviated transaction IDs.\n\nAdd a scenario only when the user requests one. Use only user-supplied changes. State the amount, direction, start month, revised burn, revised runway, and difference from the base case. A scenario is not a forecast.\n\n## Deliver the report\n\nLead with the requested balance, liquidity, burn, or runway result. Include only the scope, data quality, components, monthly cash flow, method, driver evidence, scenarios, actions, and limits needed to support the answer.\n\n## Requests to make changes\n\nThis review workflow remains read-only. When the user explicitly requests a supported payment, transfer, category, or transaction metadata change, route that part to `../mercury-actions/SKILL.md`. Keep any requested analysis separate from the authorized change.\n"
}