Magnos

board-pack

Builds a one-page month-end summary for the board or the CFO from actuals and budget by month. The page has one paragraph, a KPI table, the lines that explain the gap to budget for the month and the year to date, what moved from the month before, and one next step. It writes board_pack_<mon>.md and a page spec that the page skill turns into an HTML page. Use for a board pack, a monthly management commentary, a CFO update, a one-page summary of the month, or /magnos:board-pack. Not for a full line-by-line variance; use variance.

close-review

Compares this month's trial balance with last month's account by account, flags the moves above materiality, explains each one from the general ledger's memo lines, and drafts a question for each account owner where the ledger gives no cause. Use for a month-end close review, flux analysis, "what moved this month", "which accounts need an explanation before sign-off", or when the person shares two trial balance exports (tb_sep.csv, tb_aug.csv) with or without a GL export. Not for actuals against budget; use variance.

figures

Lists every figure in the last answer as traced or not traced, with its source (a file, a script's output, the person's message, or a calculation and its formula), then fixes or removes each figure that is not traced. Use for /magnos:figures, "where does this number come from", "are these figures checked", "source these numbers", or before an answer goes to a CFO, board or client.

finance-plain

Writes or rewrites finance text in Finance plain, a controlled style based on ASD-STE100 Simplified Technical English. Finance plain puts the answer first, uses short active sentences, gives every figure its unit, period and comparison base, states direction in words, uses points for changes in rates, puts three or more figures in a table, and cuts hedging. Use when writing or editing variance commentary, close or month-end summaries, board pack or investor update text, CFO notes, budget narratives, emails about numbers, or any reply that reports figures, even if the person only says "tighten this" or "make it clearer". Not for computing figures; run an analysis skill first.

model-review

Audits an Excel model, budget or forecast workbook (.xlsx, .xlsm) without changing it. It maps every formula and lists hardcoded numbers inside formulas, cells that break their row's pattern, links to other files, totals that miss rows or columns, and error values, each with its sheet, cell and formula. Use before a workbook goes to a board, CFO, investor or lender, or for "check this model", "audit this spreadsheet", "is this budget right", or /magnos:model-review. Not for comparing actuals with the budget's figures; use variance.

page

Turns a computed finance result into one self-contained HTML page. The page can hold a title, a summary, figure tiles, a bridge, line and bar charts, tables and a switch between views. It uses inline CSS and SVG, makes no network requests, and reads well at phone width in light and dark mode. Use when the person wants a result as a web page, an HTML one-pager, something to open in a browser, email or share, a dashboard-style summary, or /magnos:page. Not for computing the figures; run variance, board-pack or another skill first.

profile

Profiles exported CSV or Excel files before any figure is computed from them. For each file it reports rows, columns and their types, the grain, the period and whether the last month is complete, entities, currencies, duplicate keys, empty values and total rows. Across files, it checks whether a join is one-to-many and how much it would double count. It also works out quota attainment by rep, with history and next-quarter pipeline coverage, from a deals export and a quota file. Use when the person shares exports (general ledger, trial balance, CRM deals, line items, subscriptions, quotas, invoices) and asks a question about them, asks what a file holds, wants to join files, asks about reps and quota, or runs /magnos:profile.

reconcile

Matches bank statement lines to the cash account in the ledger, groups what is left (checks not yet cleared, bank fees and payouts not booked, amount differences), ties the bank balance to the ledger balance, and drafts the journal for the fees in an Excel workbook. Use for a bank reconciliation, "bank rec", "why doesn't cash tie", outstanding checks, or when the person shares a bank export and a GL cash export (bank_sep.csv, gl_cash_sep.csv). Not for trial balance movements; use close-review.

saas-metrics

Works out ARR movement and retention for a period from a subscription export. It reports start and end ARR, new, expansion, contraction and churned ARR, net and gross revenue retention, logo churn and customer concentration. It shows each metric with its formula and writes a summary to metrics/, so next period's export gives the same numbers the same way. Use for ARR or MRR, an ARR bridge or waterfall, NRR, GRR, churn, the largest customers, or /magnos:saas-metrics, from a billing, CRM or ARR schedule export. Not for revenue against budget; use variance.

setup

Creates or updates the finance profile (.magnos/finance.md) that every Magnos skill reads. It scans the CSV and XLSX files in the working folder, proposes a fiscal year start, reporting currency, materiality thresholds and variance sign convention from them, asks four short questions and writes the answers. Use for /magnos:setup, a first session with Magnos, or when the person wants to change their fiscal year, currency, materiality or how variances are signed.

variance

Compares a P&L export of actuals with a budget or forecast export line by line, for one month or the year to date. It reads each line as revenue or cost so that favourable is always right, derives gross profit, operating expenses and EBITDA, and names the two or three lines that explain most of the gap. It can also draw the gap as a driver tree or a bridge. Use for budget vs actual, forecast vs actual, "why did we miss EBITDA", "how are we doing against plan", or /magnos:variance, with CSV, TSV or XLSX files in either wide (one column per month) or long layout. Not for the month-on-month movement of a trial balance; use close-review. Not for a board-ready page; use board-pack.

you-should-know

Decides, after an answer built on data, whether to add one closing note about something the person did not ask about but would want to know. "You should know" is for something in the data beyond the question, such as an underperformer, a concentration or a trend break. "Heads up" is for a result that may be wrong, such as a double count, a partial period, mixed currencies, a sign flip, duplicates or a total that does not tie. The default is no note. Use after any answer that read or computed data from trial balances, ledgers, budgets, bank statements, CRM, billing or subscription exports or spreadsheets, and when the person asks "anything else I should know?" or "what am I missing?".