Update to Embat

{
  "name": "ask-embat",
  "description": "Answer questions about the user's own live treasury and finance data in Embat — cash position, account balances, bank fees, debt schedules, WACD, cash forecasts and scenario variance, payables and payment batches, journal entries, reconciliations, PSP reconciliation (Stripe, Adyen, Redsys, PayPal), intercompany balances and interest, users, roles and automation rules. Use whenever the user asks about their company's or group's financial position, payments, debt, accounting or forecasts. Read-only — it cannot execute payments, post entries, approve batches or change configuration. Do not use for general finance theory, public market data, or companies other than the user's own.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 812
    },
    {
      "relative_path": "assets/embat.png",
      "size_in_bytes": 5570
    },
    {
      "relative_path": "assets/embat_isotype_white.png",
      "size_in_bytes": 261
    }
  ],
  "skill_md_contents": "---\nname: ask-embat\ndescription: Answer questions about the user's own live treasury and finance data in Embat — cash position, account balances, bank fees, debt schedules, WACD, cash forecasts and scenario variance, payables and payment batches, journal entries, reconciliations, PSP reconciliation (Stripe, Adyen, Redsys, PayPal), intercompany balances and interest, users, roles and automation rules. Use whenever the user asks about their company's or group's financial position, payments, debt, accounting or forecasts. Read-only — it cannot execute payments, post entries, approve batches or change configuration. Do not use for general finance theory, public market data, or companies other than the user's own.\n---\n\n# Ask Embat\n\nEmbat is a treasury management platform. This skill queries the signed-in user's\nown Embat data through the `ask_tellme` MCP tool, which routes each question to\na supervisor agent and eight domain specialists.\n\n## When to use\n\nUse this skill whenever the question concerns the user's own financial data in\nEmbat. Typical triggers by domain:\n\n| Domain | Ask about |\n|---|---|\n| **Cash** | Cash position, account balances, bank fees, transactions, balance movements, bridge analysis, abnormal movements |\n| **Debt** | Debt schedules, loan terms, WACD / cost of debt, amortization, drawdowns, repayments, maturities, interest costs, credit line headroom |\n| **Treasury forecasting** | Cash forecasts, forecasted position on a future date, forecast-vs-actual variance, scenarios and projections, drill-downs, cash risks, unexpected transactions, client billed volume |\n| **Payments** | Payables, invoices to pay, payment batches, approval status, pre-funding transfers, payment orders, rejected payments, supplier payment history, failure reasons |\n| **Accounting** | Journal entries, settlements, pending postings, reconciliations, chart of accounts, GL accounts, ERP sync, single-transaction status trace |\n| **PSP reconciliation** | Stripe, Adyen, Redsys, PayPal; reconciliation bundles, order-to-transaction matching, unmatched items, manual vs automatic matches, PSP connection health |\n| **Intercompany / In-House Bank** | Relation balances between group entities, accrued and paid interest, netting and settlement proposals, interest income/expense by entity |\n| **Settings & automation** | Users, roles and permissions, category tree, automation rules (errored / stale / affecting accounting), approval flows, dashboards, widgets, scheduled reports |\n\n## When not to use\n\n- General finance, accounting theory or \"how does treasury work\" questions.\n- Public market data, FX rates or benchmarks not held in the user's Embat account.\n- Any other company's data — the tool only ever sees the signed-in user's own\n  group, scoped by their Embat permissions.\n- Requests to **change** anything (see the read-only boundary below).\n\n## How to call it\n\nPass the user's question through essentially verbatim as `query`. Do not\ndecompose it into sub-questions or pre-translate it — the supervisor handles\nrouting, multi-domain fan-out (e.g. liquidity = cash balances + credit\nheadroom) and language detection itself. `query` is the only parameter;\nconversation continuity is bound to the MCP session automatically, so\nfollow-ups like \"and last month?\" work without passing any thread identifier.\n\nThe tool answers in the user's own language.\n\n## What to expect back\n\nA text answer plus `structuredContent` carrying the rendered `components` and\nthe `tool_calls` the agent made. Relay the answer as given; don't recompute\nfigures from the components.\n\nTwo clarifying behaviours are **correct and expected** — relay them to the user\nrather than guessing:\n\n- **Scope selectors.** The agent may ask which companies a rule or query\n  applies to. Answering it (\"only Acme SL\", \"all companies in my group\") is the\n  second step of the same request, not a new one.\n- **Projection picklist.** For a forecast question when more than one scenario\n  exists, the agent asks the user to pick one. Dates, companies and currencies\n  have safe defaults and are never asked about.\n\n## Read-only boundary\n\n`ask_tellme` is annotated `readOnlyHint: true` / `destructiveHint: false`. It\nlooks up and analyses data; it cannot post journal entries, make or approve\npayments, create, edit or delete records, change configuration, or connect\nintegrations. If the user asks for one of those, say it must be done in the\nEmbat app.\n\nOne nuance worth knowing: the agent *can* record \"customization contexts\" —\nrecurring instructions the user teaches it, such as how a class of transactions\nshould be matched or which payables to discard. These change the assistant's\nfuture behaviour, not any Embat record, which is why the tool remains read-only.\n\n## Authentication\n\nThe connector uses OAuth; the tool resolves the user's identity and Embat\npermissions from their token on every call. If the user sees a message about\nverifying access, they should reconnect the connector.\n"
}