dsh-office-kit 0.4.1 → 0.4.3

package/assets/skills/office-spreadsheets/recipes/number-formats.md

@@ -1,9 +1,6 @@
 # Number formats
 
-A number format changes how a stored value is displayed, never the value. The
-cell keeps full precision; `0.0%` shows `6.4%` for `0.06398`. Never store a
-rounded number to make a column look tidy, and never store `"6.4%"` as text —
-it stops summing.
+A number format changes how a stored value is displayed, never the value. The cell keeps full precision; `0.0%` shows `6.4%` for `0.06398`. Never store a rounded number to make a column look tidy, and never store `"6.4%"` as text — it stops summing.
 
 ```python
 import sys
@@ -42,31 +39,18 @@ wb.save(sys.argv[2])
 | Date | `yyyy-mm-dd` | Sortable, unambiguous; store a real date, not text |
 | Text passthrough | `@` | For codes and account numbers with leading zeros |
 
-Do not use `0,0%` or `#.##0`. They are not locale-independent and render
-differently on an engine that reads `,` as a decimal separator.
+Do not use `0,0%` or `#.##0`. They are not locale-independent and render differently on an engine that reads `,` as a decimal separator.
 
 ## Signs, units, and scale
 
-- State the unit once, in the header or title (`Revenue (USD)`), and keep the
-  stored value in that unit. A column that stores thousands but is headed
-  "USD" is a defect waiting to be discovered.
-- If the presentation needs thousands (`$K`) while the data is in units,
-  format does not divide — either store thousands and say so, or divide with a
-  formula in a helper column. Never scale twice.
-- Percentages: store `0.064`, never `6.4`. A stored `6.4` formatted `0.0%`
-  reads `640.0%`.
+- State the unit once, in the header or title (`Revenue (USD)`), and keep the stored value in that unit. A column that stores thousands but is headed "USD" is a defect waiting to be discovered.
+- If the presentation needs thousands (`$K`) while the data is in units, format does not divide — either store thousands and say so, or divide with a formula in a helper column. Never scale twice.
+- Percentages: store `0.064`, never `6.4`. A stored `6.4` formatted `0.0%` reads `640.0%`.
 
 ## Widths and `###`
 
-`###` means the column is narrower than the formatted number. Widen that
-column (`ws.column_dimensions["B"].width = 14`) or shrink the font for the block.
-Never shorten the number, switch to text, or reduce decimals just to fit — and do
-not autofit every column in the sheet to fix one.
+`###` means the column is narrower than the formatted number. Widen that column (`ws.column_dimensions["B"].width = 14`) or shrink the font for the block. Never shorten the number, switch to text, or reduce decimals just to fit — and do not autofit every column in the sheet to fix one.
 
 ## Dates
 
-Write a real date (`datetime.date(2026, 1, 31)`) and set `yyyy-mm-dd`. Storing
-an ISO string sorts alphabetically and calculates as text: `EDATE`, `SUMIFS` on
-dates, and `YEAR()` all fail silently or with `#VALUE!`. A date typed as a number
-of days since 1899-12-30 is a serial — fine for formulas, unreadable for people,
-so format it.
+Write a real date (`datetime.date(2026, 1, 31)`) and set `yyyy-mm-dd`. An ISO string sorts alphabetically and calculates as text: `EDATE`, `SUMIFS` on dates, and `YEAR()` all fail silently or with `#VALUE!`. A date typed as a number of days since 1899-12-30 is a serial — fine for formulas, unreadable for people, so format it.

package/assets/skills/office-spreadsheets/recipes/sparklines.md

@@ -1,8 +1,6 @@
 # Sparklines and in-cell bars
 
-openpyxl writes no sparkline object (and neither does the helper CLI), so a
-"sparkline" here is one of two things: a formula that draws a bar inside the
-cell, or a tiny native chart. Pick by what the user needs to read.
+openpyxl writes no sparkline object (and neither does the helper CLI), so a "sparkline" here is one of two things: a formula that draws a bar inside the cell, or a tiny native chart. Pick by what the user needs to read.
 
 ```python
 import sys
@@ -21,23 +19,12 @@ ws.row_dimensions[4].height = 14
 wb.save(sys.argv[2])
 ```
 
-- `REPT` needs a repeat count that fits the column. A 9-character column shows
-  about 7 blocks at 9pt; anything longer spills into the neighbouring cell and
-  the bars look like one continuous smear. Scale to the column width, not to 22.
-- Keep the count formula-driven (`value / MAX(values) * width`), so a changed
-  number moves the bar.
-- The block character is text. Sorting the column sorts blocks, and a reader who
-  copies the cell gets `████`, not a number — never put these in the column the
-  numbers should be read from.
-- Guard blanks with `IF(cell="","",…)`, otherwise a blank reads as zero and every
-  missing month draws a minimum bar.
-- A native in-cell chart is not the same as a chart object: if the user needs a
-  hover tooltip, axis, or legend, build a real chart with `recipes/charts.md`
-  instead of stretching a formula.
+- `REPT` needs a repeat count that fits the column. A 9-character column shows about 7 blocks at 9pt; anything longer spills into the neighbouring cell and the bars look like one continuous smear. Scale to the column width, not to 22.
+- Keep the count formula-driven (`value / MAX(values) * width`), so a changed number moves the bar.
+- The block character is text. Sorting the column sorts blocks, and a reader who copies the cell gets `████`, not a number — never put these in the column the numbers should be read from.
+- Guard blanks with `IF(cell="","",…)`, otherwise a blank reads as zero and every missing month draws a minimum bar.
+- An in-cell native chart is not the same as a chart object: if the user needs a hover tooltip, axis, or legend, build a real chart with `recipes/charts.md` instead of stretching a formula.
 
 ## When a real chart is the right answer
 
-A sparkline is context for one number, in a dense table. If the sheet has space
-and the point is the trend itself, a small `LineChart` (height 4, width 9, no
-legend, no gridlines) reads better and stays editable. Two or three word-sized
-charts beat a wall of block characters.
+A sparkline is context for one number, in a dense table. If the sheet has space and the point is the trend itself, a small `LineChart` (height 4, width 9, no legend, no gridlines) reads better and stays editable. Two or three word-sized charts beat a wall of block characters.

package/assets/skills/office-spreadsheets/references/charts.md

@@ -1,8 +1,6 @@
 # Chart choice and audit
 
-A chart earns its place when it makes a comparison, a trend, a distribution, or a
-relationship easier to see than a table would. If the reader only needs the
-figures, a compact table or a KPI tile is better — and cheaper to check.
+A chart earns its place when it makes a comparison, a trend, a distribution, or a relationship easier to see than a table would. If the reader only needs the figures, a compact table or a KPI tile is better — and cheaper to check.
 
 | Question | Default | Notes |
 | --- | --- | --- |
@@ -16,48 +14,31 @@ figures, a compact table or a KPI tile is better — and cheaper to check.
 
 ## Honesty
 
-- Series must read from cells, not from typed arrays, and derived values must be
-  formulas. A chart of pasted numbers drifts the moment the table updates.
-- Include zero on bar, column, and area axes. Narrowing a line or scatter axis is
-  acceptable when the limits are stated; a truncated bar axis turns a 5% change
-  into a dramatic cliff.
+- Series must read from cells, not typed arrays, and derived values must be formulas. A chart of pasted numbers drifts the moment the table updates.
+- Include zero on bar, column, and area axes. Narrowing a line or scatter axis is acceptable when the limits are stated; a truncated bar axis turns a 5% change into a dramatic cliff.
 - No 3-D, no shadows, no gradients. They occlude data and date the workbook.
-- One period, one baseline, one unit across comparable charts. Disclose omitted
-  periods and missing values; do not let a blank read as zero.
-- Sort categories deliberately (by value, or by the natural order of time), and
-  keep the same order across charts that will be compared.
+- One period, one baseline, one unit across comparable charts. Disclose omitted periods and missing values; do not let a blank read as zero.
+- Sort categories deliberately (by value, or by the natural order of time), and keep the same order across charts that will be compared.
 
 ## Formatting rules that catch reviewers' eyes
 
-- Title states subject and unit: `Profit by category ($m)`, `Monthly revenue
-  (USD)`. No placeholder titles, no legend standing in for a title.
-- Units in the title or on the axis: `($K)`, `($M)`, `(USD thousands)`. Never
-  `($000)`.
-- Axis number formats are set on the chart. Source cell formats do not carry over,
-  and a `0.0%` column can still produce `0.06, 0.08` ticks.
-- Few series: direct labels. More series: legend above the plot area, consistent
-  colours per series across the workbook.
-- Single series: no legend, one colour. A reference or target line is neutral or
-  dashed so it does not read as another data series.
-- Selective data labels only — the last point, the maximum, the one the user asked
-  about. Ten labels on a twelve-point line is a table with extra steps.
+- Title states subject and unit: `Profit by category ($m)`, `Monthly revenue (USD)`. No placeholder titles, no legend standing in for a title.
+- Units in the title or on the axis: `($K)`, `($M)`, `(USD thousands)`. Never `($000)`.
+- Axis number formats are set on the chart. Source cell formats do not carry over, and a `0.0%` column can still produce `0.06, 0.08` ticks.
+- Few series: direct labels. More series: legend above the plot area, consistent colours per series across the workbook.
+- Single series: no legend, one colour. A reference or target line is neutral or dashed so it does not read as another data series.
+- Selective data labels only — the last point, the maximum, the one the user asked about. Ten labels on a twelve-point line is a table with extra steps.
 - Line strokes are set explicitly; a fill alone may not colour an exported line.
 
 ## Placement
 
-Charts sit next to the data they describe, aligned to a column edge, over empty
-cells, and never over the data, the controls, or a note. Size them to their
-content; a chart stretched across the page with two bars in it looks unfinished.
+Charts sit next to the data they describe, aligned to a column edge, over empty cells, and never over the data, the controls, or a note. Size them to their content; a chart stretched across the page with two bars looks unfinished.
 
 ## Verifying a chart
 
 1. Read the object back: type, anchor, series count, category source.
-2. Render and look at the image: are there categories, is anything clipped, is the
-   legend empty, do the bars reach the values in the table?
+2. Render and look at the image: are there categories, is anything clipped, is the legend empty, do the bars reach the values in the table?
 3. Compare the visual against the sheet's numbers at one or two points.
-4. Re-open in the app the user will use if the colours matter — an authoring
-   preview is not proof that a filled series exports as a visible line.
+4. Re-open in the app the user will use if the colours matter — an authoring preview is not proof that a filled series exports as a visible line.
 
-If the chart cannot be delivered as asked (the engine has no box plot, the data
-cannot be rearranged), say so and use the closest clear alternative. Never claim a
-requirement was met by a chart that does not show it.
+If the chart cannot be delivered as asked (the engine has no box plot, the data cannot be rearranged), say so and use the closest clear alternative. Never claim a requirement was met by a chart that does not show it.

package/assets/skills/office-spreadsheets/references/domain/financial-models.md

@@ -1,29 +1,15 @@
 # Financial models
 
-Applies to forecasts, budgets, cash-flow plans, and valuation work in any
-industry.
+Forecasts, budgets, cash-flow plans, and valuation work in any industry.
 
-- Periods run left to right with the scale in the header (Actual, Forecast,
-  Budget). Do not mix a monthly column with a quarterly total in the same row
-  without a labelled total column at the edge.
-- Drivers first, results second: volume × price, headcount × cost, days × rate.
-  A revenue row that jumps straight to a number cannot be reviewed.
-- Units are stated once and kept: thousands vs millions in the same block is the
-  classic reconciliation failure. Put the unit in the title, not in a footnote.
-- Three statements or none: if the workbook includes a balance sheet and a cash
-  flow, the balance sheet must balance and closing cash must equal the cash-flow
-  ending balance. Add those as checks, not as comments.
-- Working capital moves: receivables from revenue × DSO, payables from cost × DPO,
-  inventory from COGS × days. Hard-coded changes in working capital break when the
-  drivers move.
-- Scenarios: one selector, one set of case inputs per driver, and an explicit
-  `Case Selected:` on each output. A workbook with two switch cells reports two
-  answers.
-- Never hard-code a total that already exists as a sum, and never sum a column that
-  already contains a total (double counting is silent).
-- Sensitivity: one or two variables, closed-form or a small grid with the base case
-  marked. A native What-If Data Table is a different object with its own limits —
-  only build one when the user asks for it and the engine supports it.
+- Periods run left to right with the scale in the header (Actual, Forecast, Budget). Do not mix a monthly column with a quarterly total in the same row unless a labelled total column sits at the edge.
+- Drivers first, results second: volume × price, headcount × cost, days × rate. A revenue row that jumps straight to a number cannot be reviewed.
+- State units once and keep them: thousands and millions in the same block is the classic reconciliation failure. Put the unit in the title, not a footnote.
+- Three statements or none: if the workbook has a balance sheet and a cash flow, the balance sheet must balance and closing cash must equal the cash-flow ending balance. Make these checks, not comments.
+- Working capital moves: receivables from revenue × DSO, payables from cost × DPO, inventory from COGS × days. Hard-coded working-capital changes break when drivers move.
+- Scenarios: one selector, one set of case inputs per driver, and an explicit `Case Selected:` on each output. Two switch cells report two answers.
+- Never hard-code a total that exists as a sum, and never sum a column that already holds a total — double counting is silent.
+- Sensitivity: one or two variables, closed-form or a small grid with the base case marked. A native What-If Data Table is a different object with its own limits; build one only when the user asks and the engine supports it.
 
 ## Checks a finance reader looks for first
 
@@ -36,5 +22,4 @@ industry.
 | Case consistency | Every tab shows the same selected case |
 | No hard-coded totals | Total cells are formulas |
 
-Put them on a check tab, terminal and read-only, and make a failing check visually
-obvious without painting passing checks green.
+Put them on a check tab, terminal and read-only. Make a failing check visually obvious without painting passing checks green.

package/assets/skills/office-spreadsheets/references/domain/healthcare.md

@@ -1,22 +1,11 @@
 # Healthcare operations
 
-Workbooks here usually track volume, capacity, cost, and quality — not patients.
-Treat patient-level data as sensitive: do not paste identifiers into a workbook
-unless the user asks for it, do not copy rows from files you were shown into new
-sheets, and prefer aggregates.
+Workbooks here usually track volume, capacity, cost, and quality — not patients. Treat patient-level data as sensitive: do not paste identifiers into a workbook unless the user asks, do not copy rows from files you were shown into new sheets, and prefer aggregates.
 
-- Name the denominator in every rate: per patient day, per discharge, per 1,000
-  members, per available bed. A percentage without its base is not a metric.
-- Volume and capacity are different columns. Utilization is
-  `used ÷ available`, and both sides need the same period and unit (bed-days, not
-  beds).
-- Payer mix, service line, and site of care are separate dimensions. One table with
-  a column per dimension beats four tables that must be read together.
-- Quality and safety metrics keep their own definitions; do not average a rate
-  across sites without stating whether it is volume-weighted.
-- Claims and remittance data arrive with gaps. Show missing as blank or `n.a.`,
-  never as zero, and state the coverage period.
-- Do not invent clinical thresholds, targets, or compliance claims. Use the
-  targets the source file provides, and cite the sheet and cell.
-- Money and counts follow the finance conventions: units stated once, totals as
-  formulas, checks that detail rows reconcile to the summary.
+- Name the denominator in every rate: per patient day, per discharge, per 1,000 members, per available bed. A percentage without its base is not a metric.
+- Volume and capacity are different columns. Utilization is `used ÷ available`, and both sides need the same period and unit (bed-days, not beds).
+- Payer mix, service line, and site of care are separate dimensions. One table with a column per dimension beats four tables that must be read together.
+- Quality and safety metrics keep their own definitions; do not average a rate across sites without stating whether it is volume-weighted.
+- Claims and remittance data arrive with gaps. Show missing as blank or `n.a.`, never as zero, and state the coverage period.
+- Do not invent clinical thresholds, targets, or compliance claims. Use the targets the source file provides, and cite the sheet and cell.
+- Money and counts follow the finance conventions: units stated once, totals as formulas, checks that detail rows reconcile to the summary.

package/assets/skills/office-spreadsheets/references/domain/marketing.md

@@ -1,28 +1,14 @@
 # Marketing and advertising
 
-Campaign work is a funnel plus a spend table, and both are easy to make look
-better than they are.
+Campaign work is a funnel plus a spend table, and both are easy to make look better than they are.
 
-- One row per campaign, channel, or creative — with that grain named in the header.
-  Mixing a channel total into a campaign table double counts.
-- The funnel reads spend → impressions → clicks → conversions → revenue, in that
-  order, with rates derived by formula: `CTR = clicks / impressions`,
-  `CVR = conversions / clicks`, `CPA = spend / conversions`,
-  `ROAS = revenue / spend`.
-- Never compute a ratio from cells that are not the same period and the same
-  population. A monthly CTR built from a quarterly spend and a weekly click count
-  is a number nobody can defend.
-- Attribution is a claim: say which model the numbers use (last click, platform
-  reported, blended) and keep it constant across the table. Do not add platform
-  conversions together and call it incremental revenue.
-- Missing spend or reach for a period is blank, not zero — a zero-spend month
-  shows an infinite CPA and a fake collapse in the trend.
-- Benchmarks and targets belong in a labelled row or column with their source, not
-  in a note the reader has to find.
+- One row per campaign, channel, or creative, with that grain named in the header. Mixing a channel total into a campaign table double counts.
+- The funnel reads spend → impressions → clicks → conversions → revenue in that order, with rates derived by formula: `CTR = clicks / impressions`, `CVR = conversions / clicks`, `CPA = spend / conversions`, `ROAS = revenue / spend`.
+- Never compute a ratio from cells that are not the same period and the same population. A monthly CTR built from a quarterly spend and a weekly click count is a number nobody can defend.
+- Attribution is a claim: say which model the numbers use (last click, platform reported, blended) and keep it constant across the table. Do not add platform conversions together and call it incremental revenue.
+- Missing spend or reach for a period is blank, not zero — a zero-spend month shows an infinite CPA and a fake collapse in the trend.
+- Benchmarks and targets belong in a labelled row or column with their source, not in a note the reader has to find.
 
 ## Charts for marketing
 
-Spend and return on the same chart only when both are in the same unit; otherwise
-two aligned charts. Sort channel bars by spend or by return — not alphabetically —
-and keep the same order across charts. A conversion trend belongs on a line chart
-with the campaign launch dates marked, not on a pie.
+Put spend and return on one chart only when both use the same unit; otherwise two aligned charts. Sort channel bars by spend or by return, not alphabetically, and keep the same order across charts. A conversion trend belongs on a line chart with the campaign launch dates marked, not on a pie.

package/assets/skills/office-spreadsheets/references/domain/research.md

@@ -1,22 +1,11 @@
 # Scientific and research data
 
-The spreadsheet is usually a working copy of measurements, not the record of
-truth. Keep it that way: never edit raw measurements in place, and never let a
-formatted view replace the values behind it.
+The spreadsheet is usually a working copy of measurements, not the record of truth. Keep it that way: never edit raw measurements in place, and never let a formatted view replace the values behind it.
 
-- Raw data on its own sheet, untouched, in columns whose headers carry the unit
-  (`time (s)`, `temp (C)`, `conc (mg/L)`). Derived columns live on a build sheet
-  and reference the raw cells.
-- One row per observation, one column per variable. Do not encode a variable in a
-  colour, a note, or a header font.
-- Replicates are separate rows with a replicate id and a group id; the mean and
-  standard deviation are formulas over those rows, never typed.
-- Keep the precision the instrument gives you and let the format hide extra
-  decimals. Rounding stored values destroys the ability to recompute a mean.
-- Uncertainty, detection limits, and excluded points are stated in labelled cells.
-  An excluded point stays in the data with a reason column — deleting it hides the
-  decision.
-- Smoothing, binning, and unit conversion are formulas with visible inputs, or they
-  do not exist. A trend line drawn over noisy points is not an analysis.
-- Distribution, trend, and relationship: choose the chart by the question, and
-  check that the axis ranges and bins are stated (`references/charts.md`).
+- Raw data on its own sheet, untouched, in columns whose headers carry the unit (`time (s)`, `temp (C)`, `conc (mg/L)`). Derived columns live on a build sheet and reference the raw cells.
+- One row per observation, one column per variable. Do not encode a variable in a colour, a note, or a header font.
+- Replicates are separate rows with a replicate id and a group id; mean and standard deviation are formulas over those rows, never typed.
+- Keep the precision the instrument gives you and let the format hide extra decimals. Rounding stored values destroys the ability to recompute a mean.
+- State uncertainty, detection limits, and excluded points in labelled cells. An excluded point stays in the data with a reason column — deleting it hides the decision.
+- Smoothing, binning, and unit conversion are formulas with visible inputs, or they do not exist. A trend line drawn over noisy points is not an analysis.
+- Distribution, trend, and relationship: choose the chart by the question, and check that axis ranges and bins are stated (`references/charts.md`).

package/assets/skills/office-spreadsheets/references/formula-patterns.md

@@ -1,7 +1,6 @@
 # Formula patterns
 
-Spreadsheet formulas are read by people who did not write them and recalculated
-by engines that disagree at the edges. Prefer the direct, boring form.
+People who did not write a formula have to read it, and engines that disagree at the edges recalculate it. Prefer the direct, boring form.
 
 ## Anchoring
 
@@ -12,67 +11,38 @@ by engines that disagree at the edges. Prefer the direct, boring form.
 | `$A8` | right only | A column of item labels |
 | `$B$3` | never | One rate, a case selector, a fixed constant |
 
-`=SUMIFS(Amount,Month,C$4,Item,$A8)` reads the period from the header and the item
-from the label. `=C8*$B$3` multiplies by one fixed rate; `=C8*C$3` multiplies by
-the rate in that column. Getting this backwards is the most common silent error in
-a copied model — check one filled row and one filled column by hand.
+`=SUMIFS(Amount,Month,C$4,Item,$A8)` reads the period from the header and the item from the label. `=C8*$B$3` multiplies by one fixed rate; `=C8*C$3` multiplies by the rate in that column. Getting this backwards is the most common silent error in a copied model — check one filled row and one filled column by hand.
 
 ## Aggregation
 
-- `SUM` for a column, `SUMIFS` for filtered totals, `COUNTIFS` for counts,
-  `AVERAGEIFS` for averages.
-- Use `SUMIFS`/`COUNTIFS` even with one criterion; they read the same and extend
-  cleanly.
-- `SUMPRODUCT(qty_range, rate_range)` for paired multiplication; it does not
-  collapse to a single cell the way array arithmetic would.
-- `PRODUCT` for multiplied factors, but it skips blanks: a missing input silently
-  removes a factor. Check the inputs before trusting the result.
-- `INDEX`/`MATCH`, `VLOOKUP(...,FALSE)`, or `XLOOKUP` — all fine. Keep the exact
-  match flag explicit. A matched key is not a filled value: check the returned
-  cell for blank as well as for the key existing.
-- Long category lists belong in a mapping table with a lookup, not in a nested
-  `IF` chain.
+- `SUM` for a column, `SUMIFS` for filtered totals, `COUNTIFS` for counts, `AVERAGEIFS` for averages.
+- Use `SUMIFS`/`COUNTIFS` even with one criterion; they read the same and extend cleanly.
+- `SUMPRODUCT(qty_range, rate_range)` for paired multiplication; it does not collapse to a single cell the way array arithmetic would.
+- `PRODUCT` for multiplied factors, but it skips blanks: a missing input silently removes a factor. Check the inputs before trusting the result.
+- `INDEX`/`MATCH`, `VLOOKUP(...,FALSE)`, or `XLOOKUP` — all fine. Keep the exact-match flag explicit. A matched key is not a filled value: check the returned cell for blank as well as for the key existing.
+- Long category lists belong in a mapping table with a lookup, not in a nested `IF` chain.
 
 ## Dates and periods
 
-- Use the date the source gives; `TODAY()` only when the workbook should track
-  today, and label it when it does.
+- Use the date the source gives; `TODAY()` only when the workbook should track today, and label it when it does.
 - Store real dates with a date number format. Text dates do not calculate.
-- Derive period filters from one header row so a new month is a copy, not an edit:
-  `=SUMIFS(Amount,Date,">="&C$4,Date,"<"&EDATE(C$4,1),Item,$A8)`.
-- Week starting on the first business day (Monday unless the business says
-  otherwise); say which in the header.
-- Time scales run left to right coarse to fine: Annual, Quarterly, Monthly,
-  Weekly — with narrow unfilled spacer columns, not merged headers over hidden
-  helpers.
+- Derive period filters from one header row so a new month is a copy, not an edit: `=SUMIFS(Amount,Date,">="&C$4,Date,"<"&EDATE(C$4,1),Item,$A8)`.
+- Week starting on the first business day (Monday unless the business says otherwise); say which in the header.
+- Time scales run left to right coarse to fine: Annual, Quarterly, Monthly, Weekly — with narrow unfilled spacer columns, not merged headers over hidden helpers.
 
 ## Missing data
 
-- A real zero is zero. A missing value is blank, or honestly `n.a.`/`N/A` where
-  the reader expects text. Never substitute one for the other to make a chart look
-  complete.
-- `IFERROR` only around a failure you understand, never wrapped around a whole
-  block to hide it. `IFERROR(x,0)` turns a broken reference into a plausible zero.
-- Guards must not swallow the failure they guard against: `=IF(C8=0,"n.a.",B8/C8)`
-  is a clear answer, `=IFERROR(B8/C8,0)` is a lie.
-- Missing keys in a lookup should show as missing (`=IFNA(...,"not found")`), not
-  as zero.
+- A real zero is zero. A missing value is blank, or honestly `n.a.`/`N/A` where the reader expects text. Never substitute one for the other to make a chart look complete.
+- `IFERROR` only around a failure you understand, never around a whole block to hide it. `IFERROR(x,0)` turns a broken reference into a plausible zero.
+- Guards must not swallow the failure they guard against: `=IF(C8=0,"n.a.",B8/C8)` is a clear answer, `=IFERROR(B8/C8,0)` is a lie.
+- Missing keys in a lookup should show as missing (`=IFNA(...,"not found")`), not as zero.
 
 ## Things not to write
 
-- `LET`, dynamic arrays/spills, `MAP`, `REDUCE`, `LAMBDA`: the engines that read
-  these files implement them unevenly, and openpyxl stores text without
-  validating it.
-- `INDIRECT` for everything. It breaks traceability and does not update when a
-  sheet is renamed. Keep it only where the existing file already relies on it.
-- Volatile functions (`TODAY`, `NOW`, `RAND`, `OFFSET`) in a calculation grid:
-  every keystroke recalculates them, and the value changes when the file is
-  reopened.
+- `LET`, dynamic arrays/spills, `MAP`, `REDUCE`, `LAMBDA`: the engines that read these files implement them unevenly, and openpyxl stores text without validating it.
+- `INDIRECT` for everything. It breaks traceability and does not update when a sheet is renamed. Keep it only where the existing file already relies on it.
+- Volatile functions (`TODAY`, `NOW`, `RAND`, `OFFSET`) in a calculation grid: every keystroke recalculates them, and the value changes when the file is reopened.
 
 ## Circular references
 
-Avoid unintended cycles; Excel flags them for a reason. If a cycle is deliberate
-(interest on average balance, iterative allocation), document it in the sheet,
-confirm iteration is enabled, and verify the result converges to the expected
-number. A model that only "works" because the last recalc happened to stop at
-iteration 100 is not verified.
+Avoid unintended cycles; Excel flags them for a reason. If a cycle is deliberate (interest on average balance, iterative allocation), document it in the sheet, confirm iteration is enabled, and verify the result converges to the expected number. A model that only "works" because the last recalc happened to stop at iteration 100 is not verified.

package/assets/skills/office-spreadsheets/references/style-guidelines.md

@@ -1,69 +1,44 @@
 # Style guidelines
 
-Precedence: the user's request, then the workbook or template being edited, then a
-domain convention, then these defaults. Defaults apply to new sheets, or to
-restyling the user asked for — never to a sheet you were not asked to touch.
+Precedence: the user's request, then the workbook or template being edited, then a domain convention, then these defaults. Defaults apply to new sheets, or to restyling the user asked for — never to a sheet you were not asked to touch.
 
 ## Page furniture
 
-- One blank row at the top, then a short unfilled title, left aligned, in a size
-  clearly larger than the body. No full-width filled banner.
+- One blank row at the top, then a short unfilled title, left aligned, in a size clearly larger than the body. No full-width filled banner.
 - A thin rule under the title separates it from the table; nothing else.
-- Notes sit in ordinary cells to the right of the data, at least one blank column
-  away from the last header fill, with wrap off.
+- Notes sit in ordinary cells to the right of the data, at least one blank column away from the last header fill, with wrap off.
 - No footer blocks, no "Prepared by" furniture, no date stamps nobody asked for.
-- Gridlines off on new sheets. Do not change gridlines on a sheet you are editing
-  for another reason.
+- Gridlines off on new sheets. Do not change gridlines on a sheet you are editing for another reason.
 
 ## Structure
 
-- Freeze the header row of any table that scrolls, plus the identifying column(s)
-  when horizontal scrolling hides them. Freeze the smallest useful area and never
-  move content to make freezing convenient.
-- Header row: bold, centred horizontally and vertically, dark fill with white text
-  or a light grey band, thin white separators between header cells.
-- Section bands: one continuous fill with a single outline around the block; no
-  internal borders inside the band, no full-cell grid.
-- Spacer columns are genuinely empty (no values, no borders), not narrow columns
-  of spaces.
-- Keep working titles, headers, and input areas unmerged. Center Across Selection
-  gives the look of a merge without breaking sorting, filtering, and references.
+- Freeze the header row of any table that scrolls, plus the identifying column(s) when horizontal scrolling hides them. Freeze the smallest useful area and never move content to make freezing convenient.
+- Header row: bold, centred horizontally and vertically, dark fill with white text or a light grey band, thin white separators between header cells.
+- Section bands: one continuous fill with a single outline around the block; no internal borders inside the band, no full-cell grid.
+- Spacer columns are genuinely empty (no values, no borders), not narrow columns of spaces.
+- Keep working titles, headers, and input areas unmerged. Center Across Selection gives the look of a merge without breaking sorting, filtering, and references.
 
 ## Numbers, inputs, calcs
 
 - Typed values with explicit number formats — see `recipes/number-formats.md`.
-- Left-align text, right-align numbers, centre headers, middle-align vertically;
-  top-align long wrapped descriptions.
-- Distinguish inputs from calculations consistently: inputs get a light fill or a
-  colour cue the sheet already uses, calculations stay white. Yellow/amber marks an
-  input that still needs updating; keep that cue separate from calculated warnings.
-- When cases exist, show `Case Selected:` plus the linked value near the top of
-  each output and build tab, in a restrained dashed outline, and highlight the
-  active row in the driver table.
+- Left-align text, right-align numbers, centre headers, middle-align vertically; top-align long wrapped descriptions.
+- Distinguish inputs from calculations consistently: inputs get a light fill or a colour cue the sheet already uses, calculations stay white. Yellow/amber marks an input that still needs updating; keep that cue separate from calculated warnings.
+- When cases exist, show `Case Selected:` plus the linked value near the top of each output and build tab, in a restrained dashed outline, and highlight the active row in the driver table.
 - Technical helper rows above a model are italic and grouped/collapsed.
 
 ## Conditional formatting as a cue
 
-- Bound the rule to the data, and use it for status, risk, variance, and
-  exceptions — not decoration.
-- Critical errors: light red fill, bold dark red text. Valid checks stay neutral;
-  no static green "PASS" paint over a range.
-- Reuse the sheet's existing rule style before inventing a new colour. Two similar
-  reds in one workbook look like two different severities.
+- Bound the rule to the data, and use it for status, risk, variance, and exceptions — not decoration.
+- Critical errors: light red fill, bold dark red text. Valid checks stay neutral; no static green "PASS" paint over a range.
+- Reuse the sheet's existing rule style before inventing a new colour. Two similar reds in one workbook look like two different severities.
 
 ## Typography
 
 - One family across the workbook: Helvetica Neue, Helvetica, Arial, then Aptos.
-- Two sizes at most (three counting the title). Largest size no more than six
-  points above body. A 10pt body with an 11pt header and a 14pt title is enough.
-- Bold for headers and totals, italic for short context notes — never both on
-  the same line, never on every row.
-- Tighten row heights after content fits; do not shrink the font to win an
-  argument with a column width.
+- Two sizes at most (three counting the title). Largest size no more than six points above body. A 10pt body with an 11pt header and a 14pt title is enough.
+- Bold for headers and totals, italic for short context notes — never both on the same line, never on every row.
+- Tighten row heights after content fits; do not shrink the font to win an argument with a column width.
 
 ## Tab colours
 
-Use colours only to help navigation: a darker brand tone on output tabs, one
-level lighter on assumptions, a distinct muted tone on a ReadMe, a divider tab
-coloured while its children stay plain. Financial Actuals tabs are traditionally
-light tan. Never recolour tabs during an unrelated edit.
+Use colour only to help navigation: a darker brand tone on output tabs, one level lighter on assumptions, a distinct muted tone on a ReadMe, a divider tab coloured while its children stay plain. Financial Actuals tabs are traditionally light tan. Never recolour tabs during an unrelated edit.

package/assets/skills/office-spreadsheets/references/workbook-structure.md

@@ -1,9 +1,6 @@
 # Workbook structure
 
-Tab roles describe what a sheet *does*, not what tabs a workbook must have. A
-simple workbook can carry several roles as labelled blocks on one sheet; a large
-one separates them because the readers, the refresh cadence, or the audit trail
-differ.
+Tab roles describe what a sheet *does*, not what tabs a workbook must have. A simple workbook can carry several roles as labelled blocks on one sheet; a large one separates them because the readers, the refresh cadence, or the audit trail differ.
 
 | Role | Holds | Feeds |
 | --- | --- | --- |
@@ -16,45 +13,25 @@ differ.
 
 Rules that keep a workbook readable a year later:
 
-- Inputs flow forward: source → build → output. A source tab never reads a
-  downstream result back in; when it seems to, the value belongs on a build tab.
-- Builds show the steps: quantity × rate, capacity used ÷ capacity available,
-  opening + movements = closing. One dense formula that jumps from input to final
-  number cannot be reviewed and will be wrong the first time an input changes.
-- Outputs consolidate and roll up. They do not repeat a calculation that already
-  exists on a build tab; they reference it.
-- Checks are terminal. Nothing depends on a check tab, and a passing check stays
-  neutral — a wall of green PASS fills trains the reader to ignore the one red
-  cell that matters.
-- Combine roles when the workbook is small. Three assumption cells do not need a
-  Settings tab; a short labelled block beside the calculation is easier to audit.
-- Add a tab when the reader differs, the data grain differs, the refresh
-  boundary differs, or the user asks. Not because a template had one.
+- Inputs flow forward: source → build → output. A source tab never reads a downstream result back in; when it seems to, the value belongs on a build tab.
+- Builds show the steps: quantity × rate, capacity used ÷ capacity available, opening + movements = closing. One dense formula that jumps from input to final number cannot be reviewed and will be wrong the first time an input changes.
+- Outputs consolidate and roll up. They reference the calculation on the build tab; they do not repeat it.
+- Checks are terminal. Nothing depends on a check tab, and a passing check stays neutral — a wall of green PASS fills trains the reader to ignore the one red cell that matters.
+- Combine roles when the workbook is small. Three assumption cells do not need a Settings tab; a short labelled block beside the calculation is easier to audit.
+- Add a tab when the reader differs, the data grain differs, the refresh boundary differs, or the user asks. Not because a template had one.
 
 ## Physical order
 
-For multi-tab workbooks, left to right: outputs, the assumption control panel
-(usually just after the primary output so a reader sees the switch), builds,
-then inputs and sources, with a divider tab such as `Internal >>` guarding the
-tail. The reader gets the answer first; the machinery lives to the right.
+For multi-tab workbooks, left to right: outputs, the assumption control panel (usually just after the primary output so a reader sees the switch), builds, then inputs and sources, with a divider tab such as `Internal >>` guarding the tail. The reader gets the answer first; the machinery lives to the right.
 
-Separate schedules when inputs, grain, or owners differ (revenue vs cost bases,
-monthly vs weekly). A single mega-sheet that mixes both grains is where
-double-counting starts.
+Separate schedules when inputs, grain, or owners differ (revenue vs cost bases, monthly vs weekly). A single mega-sheet that mixes both grains is where double-counting starts.
 
 ## Names
 
-Short, descriptive, and about the content: `Pipeline`, `Revenue build`,
-`Monthly forecast`. Not `Sheet3`, not `Data2`, not a sentence. A forecast review
-tab is `Forecast review`, `Forecast variance`, or `Sensitivity`; never `Movement`,
-which says nothing about what moved.
+Short, descriptive, and about the content: `Pipeline`, `Revenue build`, `Monthly forecast`. Not `Sheet3`, not `Data2`, not a sentence. A forecast review tab is `Forecast review`, `Forecast variance`, or `Sensitivity`; never `Movement`, which says nothing about what moved.
 
-Divider tabs are labels, not data: `Inputs >>` with its children uncoloured reads
-as a section marker; a coloured tab on every sheet reads as noise.
+Divider tabs are labels, not data: `Inputs >>` with its children uncoloured reads as a section marker; a coloured tab on every sheet reads as noise.
 
 ## The case selector
 
-When a workbook has cases, there is exactly one editable selector, on the cover
-or assumptions tab, with its current value shown as `Case Selected:` near the top
-of every output and build tab. Two selectors, or a selector plus hard-coded
-per-tab values, is how a model ends up reporting two different cases.
+When a workbook has cases, there is exactly one editable selector, on the cover or assumptions tab, with its current value shown as `Case Selected:` near the top of every output and build tab. Two selectors, or a selector plus hard-coded per-tab values, is how a model ends up reporting two different cases.