wellapp-ai
- 66 skills
- 0 followers
- 9 hours ago last updated
- ▌ Runway · wellapp-aiAnswer "how much runway do we have?" using Well's MCP financial graph — months of cash left, computed from real synced balances divided by actual trailing burn, with the dividend and divisor shown so the number can be challenged. Use when the user asks "what's my runway", "how much runway do we have", "when do we run out of cash", or "how many months of cash are left". Requires a connected Well workspace with bank or accounting data; if none is connected, this skill guides the user to connect one first.
- ▌ Avg Burn · wellapp-aiAnswer "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", or "how much goes out each month". Requires a connected Well workspace with bank data; if none is connected, this skill guides the user to connect one first.
- ▌ Bills Due · wellapp-aiShow what bills are coming due and when, as a date-ordered cash-planning view of accounts payable with a running cumulative total, using Well's MCP financial graph. Use when the user asks "what bills are due", "upcoming payments", "what do we owe this week/month", "AP due dates", "what's our cash outflow looking like", "when are our bills due", or "payment calendar". Requires a connected Well workspace with invoicing/bills data; if none is connected, this skill walks the user through connecting one first.
- ▌ Close Books · wellapp-aiDrive a month-end close for a Well workspace to the point of approval — start the close for a named month, read what is blocking it, clear the blockers one at a time, prepare the close package, and mint the approval offer the user accepts in the Well app. 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". 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 connection is optional and makes the close richer. If none, it walks the user through connecting first.
- ▌ Fx Exposure · wellapp-aiMeasure how exposed a company is to foreign-currency risk using Well's MCP financial graph — outstanding invoice balances and cash balances summed by non-home currency and converted to the workspace's home/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". Requires a connected Well workspace with invoicing and/or banking data plus a resolvable home currency; if either is missing, this skill walks the user through connecting one or confirming the home currency first.
- ▌ Connect Bank · wellapp-aiGet 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.
- ▌ Cash Forecast · wellapp-aiAnswer "what will our cash look like?" using Well's MCP financial graph — settled month-end balances followed by a worst-case projection that assumes no incoming revenue. 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", or "what does our cash runway look like month by month". Requires a connected Well workspace with a banking connector; if none is connected, this skill guides the user to connect one first.
- ▌ Cash Position · wellapp-aiAnswer "how much cash do we have right now?" using Well's MCP financial graph — a fast, point-in-time snapshot of current bank/cash balances across all connected accounts, per currency, backed by real synced balances rather than guesswork. 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", or "what's our total cash on hand today". Requires a connected Well workspace with a banking connector; if none is connected, this skill walks the user through connecting one first.
- ▌ Connect Tools · wellapp-aiCheck which data sources a Well workspace has connected — bank accounts, accounting software, invoicing and payment portals — get the missing ones connected with Well's one-click install links, and hand off a typed coverage result to the flow that follows. Use when the user asks to connect a bank, connect their finance tools, link an accounting tool (Pennylane, QuickBooks, Xero…), add Stripe or Shopify, asks "which tools are connected", "what can I connect to Well", or when a Well skill needs bank / accounting / invoicing data present before it continues. Do not use to compute figures, to trigger a sync, to disconnect a tool, or to run a connector's own actions.
- ▌ Define Period · wellapp-aiPin 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.
- ▌ Deploy Agents · wellapp-aiPreview 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 creating the tasks launches nothing — the Well browser extension collects only after the user opens the collect link. Use when the user asks to fetch, collect, or chase the invoices they are missing, 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 listed and 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, or to list which invoices are missing in the first place.
- ▌ Draft Invoice · wellapp-aiDraft and create a real invoice record in Well from a conversational description — e.g. "invoice Acme Corp $2,500 for consulting work, due in 30 days." Use when the user asks to "draft an invoice", "create an invoice for [client]", "bill this client for Y", "send an invoice to [company] for [amount]", or "invoice [client] $[amount] for [description]". This is a WRITE skill — it composes the invoice from user-supplied fields (never inventing an amount, tax id, date, or line item) and always shows the full draft for explicit confirmation before creating it. Once created, it also renders the invoice into a print-ready A4 PDF on the issuer's own letterhead and attaches it to the invoice record. Requires a connected Well workspace; if none, this skill walks the user through connecting one first. It creates the invoice record and its attached PDF only — it does not email or send anything to the client.
- ▌ Cost Structure · wellapp-aiAnswer "what are we spending on?" using Well's MCP financial graph — a deterministic category breakdown of one month's outflow, with the share each category takes and which grouping produced it. Use when the user asks "what are we spending on", "break down our expenses", "where is the money going", "what are our biggest costs", or "show me our cost structure". Requires a connected Well workspace with bank or accounting data; if none is connected, this skill guides the user to connect one first.
- ▌ Company Profile · wellapp-aiCompose 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.
- ▌ Define Workspace · wellapp-aiResolve 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.
- ▌ Invite Teammates · wellapp-aiInvite teammates into one Well workspace from a conversation. Out of the box it offers the people Well detected from the workspace owner's email domain who hold no membership yet; a calling flow can instead pass a specific set of people to invite. Renders Well's invite card, one row per candidate with a checkbox and a state chip (`has access` or `invited`), a contact search with email chips, a role select (admin or member), and a target picker (this workspace or a workspace group). Picking who to invite and clicking Send invitations creates the memberships and sends the invitation emails, each address reporting its own result. Use when the user asks to invite a teammate, add a member, "invite Marie to this workspace", or when a close-books or fetch-missing-invoices flow needs the owners it just assigned invited so they can open their task. 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).
- ▌ Missing Receipts · wellapp-aiFind invoices (and optionally transactions) with no source document attached — a compliance/expense-hygiene check backed by Well's MCP financial graph. Use when the user asks "which expenses are missing receipts", "find missing receipts", "compliance check on receipts", "which invoices have no document attached", "do we have documentation for all our expenses", or "missing documentation". This is a find-only check — it surfaces the gap but cannot fetch a missing receipt from a vendor portal or inbox. Requires a connected Well workspace with invoicing data; if none is connected, this skill walks the user through connecting one first.
- ▌ Confirm My Company · wellapp-aiResolve 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 `workspaces.own_company` is null, missing from the schema, 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.
- ▌ Connect Accounting · wellapp-aiGet 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.
- ▌ Normalize Currency · wellapp-aiTurn a set of amounts in different currencies into one auditable answer — either a single converted total carrying the exchange rate and as-of date behind it, or a clean per-currency breakdown — and never a blended figure. Use when a Well skill has totals spanning more than one currency, needs a rate from the `exchange_rates` root, or must state which date's rate a converted number used. Do not use when a Well tool already returned a converted figure, to fetch live market rates from outside Well, or to compute any business metric.
- ▌ Accounting Settings · wellapp-aiSet 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`.
- ▌ Cash Flow Waterfall · wellapp-aiAnswer "where did the cash go?" using Well's MCP financial graph — a bridge from the opening cash position to the closing one, showing total inflows and total outflows for the period. 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.
- ▌ Rank Clients By Ltv · wellapp-aiRank customers by total realized revenue paid to date — sum of paid invoices per customer — using Well's MCP financial graph, backed by real invoice data rather than guesswork. Use when the user asks "rank our clients by lifetime value", "who are our best customers", "rank clients by revenue", "biggest customers", "customer lifetime value", or "which customers have paid us the most". This is a realized-revenue ranking (paid invoices to date), not a predictive churn/retention-based LTV model. Requires a connected Well workspace with invoicing data and a resolvable `own_company`; if either is missing, this skill walks the user through connecting one or confirming their company first.
- ▌ Show Missing Invoices · wellapp-aiList the settled spend in one Well workspace that still has no supplier invoice for a given month or fiscal period, one row per counterparty, each row carrying how the gap can be closed — Well's agent fetches it, connect the provider, or upload it by hand — and hand the list off as a typed result. The card carries a checkbox per vendor, and its Continue click writes the picked vendors into the session as identifiers so the fetch step acts on the user's pick. Use when the user asks which invoices or receipts are missing, "what am I missing for March", "which vendor invoices do I still owe my accountant", "show me the gaps before I close the books", or when a close-books or fetch-missing-invoices flow needs the period's gap list before it collects anything. Needs a workspace pinned by define-workspace and a period resolved by define-period. Do not use to fetch, download, or collect the documents themselves, to compute a spend total, or to list unpaid customer invoices.
- ▌ Fetch Missing Invoices · wellapp-aiWalk Well's whole missing-invoice flow end to end — pin the workspace, fix the months, get the bank feed in, categorize the counterparties with no industry label, assign owners to the settled lines still missing an invoice, list the settled spend with no supplier invoice, take the user's pick of vendors to chase, connect the services Well holds a connector for, and on an explicit Deploy click queue Well's browser agents to fetch that pick. Use when the user says "fetch the invoices I'm missing", "what am I missing for March", "chase my missing supplier invoices before I close", or "run the missing-invoice flow", or when a flow like closing the books needs the missing-invoice remediation walked in order. The flow is click-chained (Use / Validate / Continue / Deploy clicks drive it) and queues nothing until the user clicks Deploy. A caller that already fixed the workspace, period and scope can start it mid-flow in composed mode. Do not use to compute a spend total, close a period, or run one brick alone.
- ▌ Payment Invoice Lookup · wellapp-aiFind the reconciliation counterpart for a specific invoice, payment, or transaction ("what payment settled this invoice", "what invoice does this payment belong to"), or list every transaction/invoice with no reconciliation match at all — a compliance/reconciliation gap — using Well's MCP financial graph. Use when the user asks "what happened with this payment", "find the invoice for this transaction", "why is this payment unmatched", "show me unreconciled payments", "find the details behind this invoice/payment", "which payments have no invoice", or "catch payments with no invoice". Requires a connected Well workspace with invoicing and banking/accounting data; if none is connected, this skill walks the user through connecting one first.
- ▌ Assign Missing Invoices · wellapp-aiAssign 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.
- ▌ Accounts Receivable Aging · wellapp-aiAnswer "who owes us money, and since when?" using Well's MCP financial graph — every outstanding customer invoice bucketed into standard aging bands (current, 1-30, 31-60, 61-90, 90+ days overdue), backed by real invoice data rather than guesswork. Use when the user asks "who owes us money", "accounts receivable aging", "AR aging", "outstanding receivables", "which customers haven't paid", "who's late paying us", or "overdue invoices owed to us". Requires a connected Well workspace with invoicing data and a resolvable `own_company`; if either is missing, this skill walks the user through connecting one or confirming their company first.
- ▌ Categorize Counterparties · wellapp-aiRaise 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, to compute a spend figure, or to connect a tool.
- ▌ Debug · wellapp-aiSystematic debugging with MCP integration, auto-invoke from qa-commit, Phase 7 Harden
- ▌
- ▌
- ▌
- ▌ Connect · wellapp-aiConnect and verify the Well MCP — authenticate, confirm the tools work, and show what to ask. Use when the user runs /well:connect, just installed the Well plugin, or says the Well connection/MCP "isn't working" / "nothing happened".
- ▌ Ar Aging · wellapp-aiProduce an accounts-receivable aging report and surface overdue invoices for a Well workspace. Use when the user asks who owes them money, an AR aging report, overdue invoices, days sales outstanding (DSO), or which customers to chase.
- ▌
- ▌ QA Commit · wellapp-aiVerify implementation against QA Contract (G#N, AC#N), auto-invoke debug on RED
- ▌
- ▌
- ▌
- ▌ QA Planning · wellapp-aiGenerate QA Contract with numbered Gherkin scenarios (G#N) and acceptance criteria (AC#N)
- ▌ Vat Summary · wellapp-aiProduce a VAT / sales-tax summary for a period from a Well workspace's posted ledger. Use when the user asks for a VAT return, VAT summary, sales tax owed, output vs input VAT, or tax declaration figures for a period.
- ▌
- ▌
- ▌
- ▌
- ▌
- ▌
- ▌ Balance Sheet · wellapp-aiBuild a balance sheet (bilan) from a Well workspace. Use when the user asks for a balance sheet, bilan, assets/liabilities/equity, or financial position at a point in time.
- ▌
- ▌ Session Status · wellapp-aiGenerate breadcrumb headers/footers with takt time tracking and muda metrics
- ▌
- ▌
- ▌
- ▌ Reconciliation · wellapp-aiMatch bank transactions to invoices and surface unpaid / unmatched items in a Well workspace. Use when the user asks what's paid vs unpaid, to reconcile the bank, to find missing payments, or to match transactions to invoices.
- ▌ Autonomous Loop · wellapp-aiIterate until success or limit, composing existing skills with Jidoka integration
- ▌
- ▌ Problem Framing · wellapp-aiFrame problems using JTBD Job Stories, HMW questions, and persona validation
- ▌ Tech Divergence · wellapp-aiEvaluate technical options with scoring matrix, trigger Gate 4 for significant decisions
- ▌ Month End Close · wellapp-aiRun a month-end (or period) close checklist against a Well workspace — verify everything is reconciled and posted before the books are closed. Use when the user asks to close the month/period, run a close checklist, check if the books are ready to close, or what's left before closing.
- ▌
- ▌
- ▌
- ▌ Cash Flow Forecast · wellapp-aiForecast cash flow and runway for a Well workspace from booked invoices and collected bank transactions. Use when the user asks for a cash-flow forecast, runway, how long until they run out of cash, projected balance, or expected inflows/outflows.
- ▌ Compte De Resultat · wellapp-aiBuild a profit & loss statement (compte de résultat / income statement) from a Well workspace. Use when the user asks for a P&L, income statement, compte de résultat, revenue vs expenses, or net result over a period.
- ▌ Querying Well Data · wellapp-aiHow to query a Well workspace correctly — discover the schema first, then query the right root. Use whenever the user asks about their invoices, companies, contacts, bank transactions, accounts, or accounting ledger in Well, or before writing any well_query_records call.