well-skills

Read a profit and loss, balance sheet or cash flow statement from the user's connected QuickBooks, Xero or Pennylane, and state its key lines with their source. Use when the user asks "show me my P&L", "what does my balance sheet say", "the cash flow statement from QuickBooks", "montre-moi mon compte de résultat" or "mon bilan Pennylane au 30 septembre", or names QuickBooks, Xero or Pennylane for any report, an aged report from QuickBooks included. QuickBooks and Xero reports are stated as the tool returns them; Pennylane shares only its trial balance, so Well computes the totals from it. Do not use it for an aged report that names no tool (that is `accounts-payable-aging` or `accounts-receivable-aging`) or for a cash bridge from the bank feed (that is `cash-flow-waterfall`). Requires a connected QuickBooks, Xero or Pennylane in a Well workspace; guides the user to connect one first.

Set a Well workspace's accounting settings — the fiscal year start month above all, plus the first fiscal year start date, home/base currency, country, accounting framework, and chart-of-accounts confirmation — over Well's MCP server, writing only the value the user confirms, never a guessed one. Use when the user asks to "set our fiscal year start", "our accounting year starts in April", "change the reporting currency", "set the accounting framework", "confirm the chart of accounts", or when a close or period-scoped flow needs the fiscal year start confirmed before it derives fiscal periods. This is a WRITE flow — it shows the current value where it can read one, confirms the new one, then writes; the fiscal year start is refused when a period is locked or a close is in progress, and changing it discards regenerable draft journal entries. Requires a connected Well workspace and owner/admin rights; it never touches the own-company identity — that is `confirm-my-company`.

Answer "what do I owe my suppliers, and how overdue is it?" using Well's MCP financial graph: every supplier bill still carrying a balance, sorted into aging bands (current, 1-30, 31-60, 61-90, 90+ days past due), read from synced invoice data rather than guessed. Use when the user asks "accounts payable aging", "AP aging", "aged balance for suppliers", "aged creditors", "how overdue are our supplier bills", "what do we owe and since when", "which suppliers have we left unpaid the longest", or "balance âgée fournisseur". For a date-ordered payment calendar instead of past-due bands, use `bills-due`. A request that names Xero or QuickBooks goes to accounting-reports. It answers first from the invoices Well already holds. Well places the side of each invoice on the server; an invoice it cannot place is listed to check, with its issuer and receiver named, and nothing is asked about a company. A missing connection is asked for after the answer.

Answer "which customers owe us money, and since when?" using Well's MCP financial graph: every outstanding customer invoice bucketed into aging bands (current, 1-30, 31-60, 61-90, 90+ days past due), read from synced invoice data rather than guessed. Use when the user asks "accounts receivable aging", "AR aging", "outstanding receivables", "which customers haven't paid", "who's late paying us", "overdue invoices owed to us", or who owes them money and how late they are. The broad, unqualified "does anyone owe me money", where supplier refunds, credits and VAT could count too, goes to money-back. A request that names Xero or QuickBooks goes to accounting-reports. It answers first from the invoices Well already holds. Well places the side of each invoice on the server; an invoice it cannot place is listed to check, with its issuer and receiver named, and nothing is asked about a company. A missing connection is asked for after the answer.

Assign the settled expense transactions in one Well workspace that still have no supplier invoice for a month to a set of owners, split into no owner set, yours, and owned by others. Renders Well's owner-assignment card, one row per transaction with its owner set and a multi-select picker; picking owners replaces the set on that line, and several lines can take the same set at once. Assigning a (counterparty × month) gap to several people holds one task per owner, and one invoice resolves them all. Use when the user asks to assign missing invoices, "who owns these missing receipts", "assign these to Marie and Théo", or "assign these to me", or when a close-books flow needs expense ownership sorted. Assigns among workspace members only. Needs define-workspace, define-period, and a connected bank. Do not use to fetch or collect documents (fetch-missing-invoices, deploy-agents), to list gaps by counterparty or pick vendors to chase (show-missing-invoices), or to assign someone not in the workspace.

Answer "what is our burn rate?" using Well's MCP financial graph: the trailing average of real monthly outflows, computed here from the workspace's own transactions, with every check it rests on visible and repairable. Use when the user asks "what's our burn rate", "how much are we spending per month", "what's our monthly burn", "how much goes out each month", or for a full analysis of the spend over several months ("analyse complète de mes dépenses sur 12 mois"). Requires a connected Well workspace with bank data; if none is connected, this skill guides the user to connect one first.

Answer "what bills are coming due, and how much do they add up to by date?" using Well's MCP financial graph: every bill the workspace still owes, ordered by due date, with a running total so the reader can see how much cash leaves and by when. Use when the user asks "what bills are due", "upcoming payments", "what do we owe this week", "AP due dates", "when are our bills due", "payment calendar", "quelles factures fournisseurs arrivent à échéance", "qu'est-ce que je dois payer cette semaine" or "mes échéances fournisseurs". It answers first from the invoices Well already holds. Well places the side of each invoice on the server; an invoice it cannot place is listed to check, with its issuer and receiver named, and nothing is asked about a company. A missing connection is asked for after the answer.

Assemble the board numbers in one pass using Well's MCP financial graph: cash, burn, runway, recurring revenue, and what is owed on each side, every figure computed here from the workspace's own balances, transactions and invoices, each one carrying the scope it was measured under and the window it covers. Use when the user asks "what numbers do I put in front of the board", "put my board pack together", "board numbers for this quarter", "what do I report to my investors this quarter", "the finance section of my board update", "prépare mon board pack", "les chiffres pour mon board" or "qu'est-ce que je présente à mes investisseurs ce trimestre". Requires a connected Well workspace with bank data and a resolved own company; an invoicing source adds the revenue pages. It reads and changes nothing.

Claim a refund or a compensation from one business for one purchase or one service: a delayed or cancelled flight, an order never delivered, a charge for something not received. It reads the evidence in Well first (the supplier's invoice or booking, and its bank debits), names a right only when the records and the person's own facts hold every fact it needs, else marks it "to confirm" (« à confirmer » in French), prepares the call as a script the person reads, and writes the claim email. Use when the user asks "réclame une indemnisation pour mon vol en retard", "claim compensation for my delayed flight", "ma commande n'a jamais été livrée, réclame le remboursement", "get my money back from this supplier", "prépare l'appel au service client" or "what do I say when I call them". It never promises an amount, it never places a call, and it sends nothing without the person's confirmation.

Answer "where did the cash go?" using Well's MCP financial graph: a bridge from the opening cash position to the closing one, computed here from the workspace's own balances and its own transactions, with every rule it rests on stated and any gap between them reported rather than hidden. Use when the user asks "where did the cash go", "reconcile our cash movement", "why did our balance change", "show me the cash flow bridge", or "how did we get from last month's balance to this one". Requires a connected Well workspace with a banking connector; if none is connected, this skill guides the user to connect one first.

Answer "what will our cash look like?" and "how has our cash moved month by month?" using Well's MCP financial graph: settled month-end balances followed by a worst-case projection computed here from the workspace's own balances and its own trailing burn, counting only the inflows its bank shows arriving every month. Use when the user asks "what will our cash look like", "show me our cash forecast", "project our cash forward", "when do we hit zero", "how has our cash moved month by month", "chart our cash over time", "is our cash going up or down", "what does our cash runway look like month by month", or "put our actual cash against our forecast in a Google Sheet" (the table comes back in the reply; Well reads and writes no Google Sheet). Requires a connected Well workspace with a banking connector; if none is connected, this skill guides the user to connect one first.

Answer "how much cash do we have right now?" using Well's MCP financial graph: the total of your real bank balances, computed here from the workspace's own accounts, with every rule it rests on visible and repairable. Use when the user asks "what's our cash position", "how much cash do we have right now", "current bank balance", "how much money is in the bank", "what's our total cash on hand today", or what they can look at on their cash right now ("que puis-je regarder sur ma trésorerie ?"). It reads the bank's state before it offers any reading, so an ask that forbids a change or wants to see first still loads it: a read changes nothing. Requires a connected Well workspace with a banking connector; if none is connected, this skill guides the user to connect one first.

Raise category coverage on the counterparties (suppliers and customers) behind one Well workspace's spend — for a given month's still-missing invoices, or workspace-wide across everything still uncategorized. Renders Well's counterparties card, where each listed row carries a catalog-category select, every pick saves immediately, and Continue hands the turn back; the skill reads one list, points at the card, and proposes categories only when the user explicitly asks it to. Use when the user asks to categorize or tag their suppliers, vendors, or counterparties, says "which suppliers have no category", "categorize the companies behind my spend", "clean up my vendor categories before I close the books", or when a fetch-missing-invoices flow reaches its counterparty categorization step. Never invents a category outside the catalog. Do not use to categorize individual transactions (that is `unposted-and-blocked`), to compute a spend figure (that is `cost-structure`), or to connect a tool (that is `connect-tools`).

Read the chart of accounts a Well workspace posts to, account number by account number, using Well's MCP context graph. Use when the user asks "what chart of accounts are we on", "show me our chart of accounts", "list our ledger accounts", "what account numbers do we use", "which accounts can a transaction post to", "do we have a 606 account", or "what is account 1112". The accounts are put on screen as a table ordered by number, with the account type and class each row carries. It emits no statutory code and no Well role binding, because the Well to statutory translation runs at export time and no chart level read reaches it. Requires a connected Well workspace; the chart is seeded when the workspace is provisioned, and an imported accounting book adds the accounts its own chart carries.

Rank overdue customer invoices by how much is owed and how late it is, look up each customer's contact info already stored in Well, and draft a ready-to-send chase message per customer, using Well's MCP financial graph and backed by real invoice data rather than guesswork. Use when the user asks "who should I chase for payment", "draft a late-payment email", "who do I need to follow up with", "chase overdue invoices", "collections reminder", "relance le client de la facture d'août", or "help me get paid faster". It drafts the messages and, for each customer the user names (a month names the customer of that invoice) or picks, opens the draft as an email card; on WhatsApp it sends it from the user's Gmail only after their tap on Confirmer. It answers first from the invoices Well holds: an invoice whose side Well cannot place is listed to check with its issuer and receiver named and gets no draft, and nothing is asked about a company.

Read the purchase invoices, the payment rail and any employment contract Well holds for a supplier who looks like a freelancer, and state the facts a requalification question turns on (cadence, repeating amounts, share of your spend, contract type where a record exists), next to the papers your country expects you to keep. Use when the user asks "is this freelancer really a contractor", "am I at risk of requalification", "do I need a W-9 from this supplier", "what is a Statusfeststellung", "do I need a 30bis retention check", "do I need an attestation de vigilance from my sous-traitant", or "which papers should I hold for my freelancers". Requires a connected Well workspace with purchase invoices, and the country each supplier works from, which you name because Well does not derive it. It states observed facts and the papers to check, it never classifies anyone as an employee, it cannot see which papers are in your drawer, and it files nothing with any authority.

For one French payroll month, list the payslip lines that are neither salary, tax nor contribution, with the label and the amount the payslip printed, set the receipt gaps Well already found beside them, and state the country rule each item has to be judged against. Use when the user asks "should this reimbursement have been on the payslip", "is this gift card taxable", "is the company car a benefit in kind", "are my notes de frais covered", "what about avantages en nature", "titres restaurant", "accountable plan expense report", or "note de frais". Requires payslips in Well for the month, from a payroll connector or from pay documents dropped into the workspace, and the receipts Well already holds. It refuses to rule on taxability: the taxable flag lives on the payroll rubric dictionary and is not readable here, a line is never classified from its label text, and this skill files nothing with a tax or social security authority.

Read one person's payslip for a month, list the lines it printed beside the same contract's earlier payslips, and name every line whose amount changed, appeared or disappeared, with the contract terms Well holds stated next to it. Use when the user asks "is this payslip right", "why is this payslip different from last month", "check my employee's payslip", "what changed on the bulletin de paie", "check this Entgeltabrechnung", "read this fiche de paie", "check the cedolino paga", "does this nómina look right", or "what moved on this pay statement since March". Requires payslips in Well for the same employment contract, at least one month to compare against, and a month to read. It refuses to file anything with any authority, refuses to recompute gross, tax, contributions or net, and refuses to check a deduction against a withholding form such as a W-4, an IT-2104, an ELStAM notice, a modulo detrazioni, a modelo 145 or a taux PAS notice, because none is a readable field in Well.

Check whether the bank and the books match for one month, or for every open month, and re-run the steps that missed rows: the invoice matching and the posting. Use when the user asks "do my bank and my books match", "compare ma banque et la compta d'août", "ma banque et ma compta collent ?" or "corrige les écarts". It reports what matched, what posted and what is blocked, from Well's own ledger. This is a WRITE flow: it re-runs the invoice matching and the posting on your ask; on "ne modifie rien" it re-runs nothing and asks first. It sends nothing to the accounting tool and picks no category and no ledger account. Do not use to list missing invoices (that is `show-missing-invoices`), to close a month (that is `close-books`) or to compare against the records inside an accounting tool. Requires a connected bank in a company workspace; if none is connected, this skill guides the user to connect one first.

For each employee Well can reach from a payslip or an uploaded contract, say which working time record the workspace country expects, whether a timesheet is on file for the period, and how long it has to be kept, over Well's MCP server. Use when the user asks "do I have to track my employee's hours", "what working time record do I need", "is a timesheet required for this hire", or names the record: FLSA time records, Arbeitszeitnachweis, Libro Unico del Lavoro, registro diario de jornada, décompte du temps de travail, suivi forfait jours. The faq lists every form by country. Requires a workspace with a country of incorporation set, and at least one payslip or uploaded contract. It is an existence and kind check, not an audit of hours: Well never reads the hours inside a timesheet, never decides whether a company is compliant, and never files any of these records with a labour inspectorate, a tax authority or a social security body.

Drive a month-end close for a Well workspace from open to sent — start the close for a named month, read what is blocking it, clear the blockers one at a time, prepare the package, mint the approval offer, and once it locks, send the entries to the connected accounting tool. Use when the user asks to "close the books", "close last month", "run the month-end close", "close March", "finish the close", or "what's left to close the period". A "just show me" ask reads the state and starts nothing. Otherwise this is a WRITE flow — it advances a real close run and can resolve tasks, so it shows the state before every step and asks first before retrying reconciliation or queuing a vendor invoice fetch, the two that need an explicit yes. It never locks the period itself; the final approval is a first-party click in Well by design. Requires a connected Well workspace with its bank synced — the only connection the close blocks on; an accounting tool is optional. If none, it walks the user through connecting first.

Compose everything Well knows about one named company — customer or vendor — into a single 360 view using Well's MCP financial graph — profile info, contact channels, and the invoice relationship (as issuer, receiver, or both). Use when the user asks "build a customer 360 view", "customer 360", "give me a 360 view of X", "everything about [company name]", "vendor across every rail", "who is this company", "show me our history with X", or "tell me about our relationship with [vendor/customer]". Requires a connected Well workspace with at least one connector that has synced company/invoice data; if none is connected or the company can't be found, this skill says so instead of guessing.

Build a board in Well from the measures a person names — cash, burn, runway, recurring revenue, cost structure, a forecast, a cash bridge — and save it as a canvas that stores the question each block asks rather than an answer. Use when the user says "build me a board", "put cash and burn on one screen", "make me a dashboard", "save this as a board", "add MRR to my board", or "show July burn next to August burn". Each block states the feed it draws and the window it asks that feed for, so two blocks on one feed can cover two months. It stores an arrangement and no figure, so nothing on the board can quietly stop being true. After the write the run continues into `resolve-board`, which measures every block through its own skill and draws the board with its figures. Requires a connected Well workspace and a resolved own company. Do not use it to answer a figure question, which the figure skills do.

Resolve which company in a Well workspace is the user's own legal entity — the `own_company` pointer that decides which side of an invoice is a payable and which is a receivable — fold in its duplicate records, and hand the confirmed identity off as a typed result; and, when asked to persist it, set the anchor via `well_set_own_company` on the user's explicit confirmation. Use when a Well skill needs to tell its own invoices from a counterparty's, when the user asks "which company is mine" or "set our company to X", or when the workspace's stored own-company anchor is null, unreadable, or ambiguous. Setting the anchor is an accounting-critical, admin-only write, taken only on an explicit confirmation and never inferred. Do not use to pick the workspace, to look up an arbitrary company by name, to merge or edit duplicate company records in Well, or to compute any financial figure.

Get an accounting tool connected to a Well workspace and confirm the feed is live — read whether an accounting system (Pennylane, QuickBooks, Xero, Sage…) is already connected, still running its first sync, or in error, hand the user Well's one-click install link, and return a typed accounting-coverage result to the flow that follows. Use when the user asks to connect their accounting software, link Pennylane/QuickBooks/Xero/Sage, asks "is my accounting connected", or when a Well skill (like closing the books) needs posted-ledger data in the workspace before it continues. Do not use to connect a bank (that is connect-bank), to connect invoicing or payment portals or several kinds at once (that is connect-tools), to compute a figure, to force a re-sync, or to disconnect a tool.

Get a bank account connected to a Well workspace and confirm the feed is live — read which banks are already connected, still running their first sync, or in error, hand the user Well's one-click bank install link, and return a typed bank-coverage result to the flow that follows. Use when the user asks to connect a bank, link a bank account, add Qonto or a Plaid-supported bank, asks "is my bank connected", "why are my transactions missing", or when a Well skill needs settled bank spend in the workspace before it continues. Do not use to connect accounting or invoicing tools (that is connect-tools), to compute a figure, to force a re-sync, or to disconnect an account.

Check which data sources a workspace has connected (bank, accounting, invoicing, payment portals), connect the missing ones with one-click install links, and hand off a typed coverage result. Use when asked to connect a bank or their finance tools, link an accounting tool (Pennylane, QuickBooks, Xero…), add Stripe or Shopify, asked "which tools are connected", "is my Gmail or Outlook inbox connected", "what can I connect to Well", or when a skill needs bank / accounting / invoicing data first. Also use when the user names or asks about one tool, such as what it would bring to Well, including a tool Well does not carry yet. Also use when they name a tool to connect but bar actions (« ne lance aucune action sans me demander », "no action without asking me"): reading the connection state is not an action, so load this skill and read it first. Do not use to compute figures, to trigger a sync, to disconnect a tool, to run a connector's own actions, or for export-fed providers like Gusto (fetch-provider-exports).

Build a Well workspace's context graph from a conversation. Connects Well to the user's AI apps when none is connected yet, gets the bank, accounting and invoicing sources connected with Well's connect card, recaps in one line per source what was connected or skipped, then draws the context graph those sources feed. Use when the user asks to "build my context graph", "set up my context graph", "show me my context graph", "connect Well to my AI apps", or wants to see how their business data connects. Needs define-workspace and connect-tools. Do not use to compute a figure, to check coverage for another skill (that is connect-tools), to explore one company's links (draw the graph directly), or to invite a teammate (invite-teammates).

Read the purchase invoices for one calendar year, list every contractor and supplier you paid with the total for each, name the ones carrying no tax identifier on file, and say which year-end statement each jurisdiction expects and roughly when, over Well's MCP business graph. Use when the user asks "who do I owe a 1099 this January", "1099-NEC list", "who needs a W-9", "DAS2", "fiche 281.50", "Certificazione Unica", "Modelo 190", "contractor year end", or "which freelancers did I pay last year". Requires a connected Well workspace with invoicing or accounting data and the workspace's own company confirmed, because the purchase side is resolved from it. This skill never files: it produces the recipient list and the per-recipient totals, and the founder, the accountant or the filing engine submits. Every figure is gross, no reporting threshold is applied, and amounts are never split by payment rail.

Answer "what are we spending on?" by breaking one complete month's outflow into categories computed here, under a grouping ladder the answer states. Use when the user asks "what are we spending on", "break down our expenses", "where is the money going", "what are our biggest costs", "what did we spend per category", "dépenses par catégorie" or "dépenses par fournisseur". Also answers, from the same bank rows, the suppliers paid the most in one month (a longer period is asked down to one month), a trend by category over up to 12 complete months, and a household space by category ("mes dépenses du foyer par catégorie"); one category against its usual month is personal-spending. Spend per supplier that names no invoice comes here; an ask that names invoices (factures) is supplier-spend-register. A single total with no breakdown is spend-total. Where to save is subscription-spend. Requires bank data (accounting data adds the reader's chart of accounts); with no bank, it guides connecting one.

List the Attio tasks that are due today or overdue, with the company and the Attio link of each, from the tasks Well syncs from Attio. For a member who turned the morning reminder on, a routine runs it with nobody present (`run: unattended`) and sends the one WhatsApp message it words. Use when the user asks "which Attio tasks are due today", "what CRM follow-ups are late", "what is overdue in Attio", or "remind me of my CRM tasks". Requires a connected Attio workspace. It reads only: it never creates, completes or moves an Attio task.

Answer "do I have everything I need on this customer to invoice them properly?" using Well's MCP context graph: the legal identity Well holds about one customer you bill, each value with where it came from, and the ones still blank. Use when the user asks "what is this customer's SIREN", "do we have their VAT number", "what is missing on this customer before I invoice them", "check this customer's billing details", "is this customer's legal name on file", or "what do we hold on [customer name]". Answers about one customer per call, reads only the workspace's own company records, and checks no public directory. Requires a connected Well workspace holding a company record for that customer.

Lay out what a new hire needs before day one in the country you hire in, name the forms to collect and the notices to hand over, and, on your explicit yes, record the person in Well and file the signed contract as a document. Use when the user asks "I just signed someone, what do I do before day one", "new hire checklist", "what forms does my first employee sign", "onboarding an employee in France", or names a form: W-4, I-9, the state new hire report, DPAE, Dimona, UniLav, DEUEV Anmeldung, Modelo 145 or contrat de travail. Requires a connected Well workspace, the country you employ in, and the hire's name, job title and start date. This is a WRITE flow, so it shows what it is about to write and asks first. This skill never files: it submits no DPAE, Dimona IN, UniLav, alta, DEUEV Anmeldung or new hire report, holds no field for a national identity number, and does not read the signed contract's terms into a record.

Pin the calendar month or months — with their fiscal coordinates — a Well workspace job works on, written server-side by the user's click on the period picker card, and hand the selection off as a typed result; or, in `collect` mode, hand one month's coordinates back to a caller that commits the period by starting a run, where naming the month is starting and this skill writes no commit. Use when the user says "last month", "March", "2026-03", "the period we're working on", asks which month a job covers, when a Well skill needs the period fixed before it reads data, or when a close or other start-a-run flow needs one month collected first. Defaults to the last complete month, refuses a month that has not ended, derives fiscal coordinates from the workspace's fiscal-year start month, and reports whether the selection has any activity. Do not use to close, lock, or reopen a period, to run a month-end close, to resolve which workspace the conversation is about, or to list what is missing inside the month.

Resolve which Well workspace (legal entity / company account) a conversation works in, and hand it off as a typed result — workspace_id, name, identity, and how it was resolved — to any Well skill or flow that follows. Use when the user asks to select, choose, switch, or confirm a workspace, says "use my FR entity" / "work in workspace X" / "which company account is this", or when a Well skill needs one workspace pinned before it reads or writes data. Resolves several entities too — "do both my companies", "FR and US" — as a pin plus a server-held queue the caller walks one workspace per pass. Do not use to connect a bank or accounting tool, to compute any financial figure, or to confirm the company identity inside the Well app.

Preview what Well would fetch for the vendors the user picked — which agents would run, over which counterparties and transactions, which rows need a manual upload, and which providers need connecting — then, on the Deploy click, create the durable fetch tasks and hand the user the collect link that starts the runs. Nothing is queued until Deploy, and the Well browser extension collects only after the user opens the collect link. This is a WRITE skill: a supplier Well lacks joins its catalog on the user's yes. Use when the user asks to fetch, collect, or chase the invoices of the picked vendors, says "launch the agents", "go get those invoices", "deploy the collectors", or when the fetch-missing-invoices flow reaches its last step after the missing rows have been picked. Do not use to run a collection from the session, to invoke a connector's own actions, to create or edit an invoice, to connect a provider, to list the missing invoices, or to design a team of assistants from a goal (use design-agent-team).

Draft an invoice in Well from a plain request, then issue it and print its PDF in the customer's design. Use when the user asks to "draft an invoice for Acme Corp, 3 consulting days at 600 euros", "bill [client] for [work]", "invoice [client] [amount]", "fais une facture à Acme pour 3 jours de conseil à 600 €" or "facture [client] [montant]". This is a WRITE flow: a first explicit yes saves the draft only, and Well shows the saved draft with its PDF; a second explicit yes, in a later turn, issues the invoice (numbered, final, with its Stripe payment link when Stripe is connected). It never invents an amount, a tax id, a date or a line, and it sends nothing. Do not use to find an existing invoice (that is `payment-invoice-lookup`), to change a design (that is `invoice-design`) or to push invoices to an accounting tool (that is `export-to-accounting-tool`). Requires a connected Well workspace; guides the user to connect one first.

Read a month of payslips, or each of several months, and state, per person, gross pay plus the employee deductions and the employer charges the payslip printed, split by the rubric side Well holds, then list separately, at company level, the payroll related bills paid from the bank that no payslip carries. Use when the user asks "what does my employee really cost me", "fully loaded cost of employment", "employer charges last month", "combien me coûte ma paie", "coût employeur", "payroll register", "Lohnjournal", "BG Beitragsbescheid", "workers' compensation policy", "bulletin de paie", "fiche de paie", "nomina", "DmfA", "mutuelle and prevoyance", or "taux AT/MP". Requires payslips in Well and, for the off payslip bills, bank transactions with their payees categorised. This skill never files anything with an authority or a fund, it never allocates an off payslip bill to a named person, and a blank amount is reported as unread rather than as zero.

Send a closed period's native journal entries to the workspace's connected accounting tool, on a card the user confirms. Use it as the last step of a close, once the period has reached `period_closed`: it reads whether a write-capable accounting connector is present and whether its grant can post, draws the export card when it can, and hands back `resolution: exported | nothing_to_send | no_tool | failed`. Never call it before the period is closed — the underlying write refuses on any earlier checkpoint. Requires a connected Well workspace; the accounting connection and its write scope are read, never assumed.

Walk Well's missing-invoice flow: pin the workspace, confirm fiscal year and currency, fix the months, get the bank feed or a statement in, offer an accounting tool if none is connected, categorize uncategorized counterparties, assign owners to settled lines missing invoices, list settled spend with no supplier invoice, pick vendors to chase, connect services Well has a connector for, and on Deploy queue Well's browser agents to fetch that pick. Use on "fetch the invoices I'm missing", "chase my missing supplier invoices" or "run the missing-invoice flow", or for close-books. It is click-chained and queues nothing until Deploy. It is a WRITE flow: a supplier Well lacks joins its catalog on your yes. A caller that fixed workspace, period and scope starts mid-flow. Also use when the user only asks to be reminded of each missing invoice: Well does not send a reminder per invoice; say so and offer the current list of missing invoices. Do not use to compute a spend total, close a period, or run one brick alone.

Get a provider's own exports into Well when Well has no connector for it, such as Gusto's payroll journal, employee roster and time off balances as CSV files. Shows a card with one row per provider, the files its run fetches and how the last run ended. Deploy opens Well's collect page, then the Well browser extension opens the provider in a new tab and downloads each file in the user's own signed-in session. Use when the user asks to sync, synchronize, fetch or refresh data from a provider with no Well connector, says "sync my Gusto", "download the payroll CSV from Gusto", "export my Gusto reports", asks whether the last export worked, or when a connect step fails because the provider offers Well no API. Do not use for a provider Well has a connector for (that is connect-tools), to import a file the user already has (that is import-statement), or to fetch supplier invoices from portals (that is deploy-agents).

Lay out the one time employer setup list for the country your company is registered in, counted back from the start date you give, with the portal link, who to contact, and your own company details written out for each step to copy. Use when the user asks "I am hiring my first employee, what do I need to set up", "how do I register as an employer", "what do I need before my first hire starts", or names a step by the name it goes by: SS-4, EIN, NYS-100, workers' comp, DBL and PFL, Betriebsnummer, BG-Anmeldung, Krankenkasse, ONSS employer identification, SEPP, règlement de travail, INPS and INAIL, delega intermediario, DVR, CCC, Sistema RED, PRL, SPSTI, DUERP. Requires a pinned Well workspace, a confirmed own company, and a start date you type, since no contract or hire record is read. This skill never files any of these. It reads your company, its public registry record and your accounting country, then hands you the list and the links, and you or your payroll bureau submit.

Read the payslips Well holds for the founder and state gross pay, tax withheld, contributions and net pay per period, beside the legal form and country of incorporation on the own company record, so the founder can take the right paperwork to their accountant. Use when the user asks "am I paying myself the right way", "what did I pay myself this year", "show me my own payslips", "what do I hand my accountant for my own pay", or names the paperwork: bulletin de paie, W-2, Lohnkonto, UniEmens, RETA. Requires a Well workspace holding the founder's payslips, from a payroll connector sync or pay documents dropped in, and an own company set if you want the legal form and country reported. This skill never files, submits or transmits any of these documents: it reads what it holds, names the paperwork that goes with them, and the founder or their accountant clicks submit. It states no filing date, derives no obligation from a legal form, and offers no bank side total of money moved to the founder.

Measure how exposed a company is to foreign-currency risk using Well's MCP financial graph — outstanding invoice balances and cash balances summed by each currency other than the reporting currency and converted to the reporting currency at real exchange rates. Use when the user asks "measure our FX exposure", "FX exposure", "currency risk", "how much of our cash/receivables is in foreign currency", "what's our exposure to EUR/USD/GBP", or "currency breakdown of our cash and invoices". It answers first from the cash and the invoices Well already holds. The reporting currency it converts into is the one the user names, the one in the accounting settings, or the one the accounts show; a missing connection is asked for after the answer.

Put a bank statement the user already has — a pdf, a csv, an ofx, an xml, or a photo of the page — through Well's own extraction, so the statement, its lines and the transactions behind them land as records in one Well workspace. Takes the file three ways: the claim token from a drop on Well's website, which collects every statement dropped together, an upload of bytes the user attaches to the conversation, or pasted text. Use when the user has a statement in hand and nothing connected yet, says "read this statement", "import my bank statement", "I have a pdf of my account", "I dropped a file on your site", or when a gap-list or close flow needs transactions for a period no connector covers. It is the cold-start on-ramp: the only Well skill that produces transactions without a bank connector. Do not use to connect a bank for ongoing sync — that is connect-bank — to read balances, or to list what invoices are missing.

Compare an insurance contract with the offers the person received, and explain how to end the current contract: the facts side by side (premium, cover, deductible), the end of the cover period read from the contract on file, and a termination letter drafted for the person to send themselves. Use when the user asks "mon assurance a augmenté, aide-moi à comparer", "compare ces devis d'assurance", "comment résilier mon assurance auto", "lettre de résiliation d'assurance", "my insurance went up, help me switch", "compare these insurance quotes" or "how do I cancel my insurance". Business and personal insurance. Informative only: it ranks no offer, gives no advice on which to take, never estimates a date, and sends, signs or pays nothing.

Invite teammates into one Well workspace from a conversation. It offers the people Well detected on the owner's email domain who hold no membership yet; a calling flow can pass a set instead. Shows Well's invite card; Send invitations creates the memberships and sends the emails; each address reports its result. Use when the user asks to invite a teammate ("invite Marie to this workspace"), gives a mobile number ("invite +33 6 00 00 00 01 as admin"), asks how inviting someone with only a number works ("comment tu invites quelqu'un qui n'a qu'un numéro ?"), asks for the invitation link ("donne-moi le lien d'invitation") or to stop it, answers an invite Well suggested ("oui", "plus tard", "non": a later or a first no waits 30 days, a second no stops it for good), or when a close-books or fetch-missing-invoices flow needs its owners invited. Needs define-workspace. Do not use to assign expense ownership (assign-missing-invoices), set the own company (confirm-my-company), or connect a tool (connect-tools).

Choose how one invoice prints — its design, the ink it is set in, the language it speaks, and which of the workspace's own notes, tax rate and payment means it carries — over Well's MCP server, writing only what the user picks. Use when the user asks to "change how my invoice looks", "pick an invoice template", "use a different invoice layout", "print my invoice in French", "put my terms on the invoice", "which bank account shows on my invoices", or "make this the design of all my invoices". This is a WRITE flow — it draws the current design as a gallery, and the gallery writes the user's pick itself when they press Apply. Every option it offers is read from this workspace's own records, so a note or account from another workspace can never be selected. Requires a connected Well workspace and an invoice to design; it does not create the invoice — that is `draft-invoice` — and it never sends anything to a customer. To only see the designs, without a change, use `show-invoice-designs`.

Answer which newsletters the member receives from Well's email records, and save one private keep, skip or unsubscribe choice for one sender. Use for "which newsletters do I get", "quelles newsletters je reçois" or "ignore this sender". Do not use for weekly mail triage or reading what a sender wrote; that is mailbox. Do not unsubscribe, delete mail, move labels or send messages.

Summarize the important mail observed this week, find the last mail from one sender, named by an address or by a role such as the accountant, or list the threads that still wait for the member's reply, from Well's records. Use it for "who am I late replying to", "à qui je dois une réponse", "which messages still need a follow-up", also across WhatsApp, Instagram or LinkedIn: Well answers from the mail and says it does not read those apps. It reads the member's own notes and person records and applies their private skipped-sender choices. Do not list newsletters or save a sender choice; mail-senders owns those asks. It also answers what a meeting said or decided, also when the ask names no recorder, from the summaries a meeting recorder (Fathom, Granola, Circleback) sent by mail when that recorder is not connected. A read-only question about the member's own mail is in scope: load this skill and answer with no yes first. Do not write mail or commitments.