XLSX creation, editing, and analysis
| Task |
Approach |
| Create or edit with formulas/formatting |
openpyxl — see gotchas below |
| Bulk data in or out |
pandas (read_excel, to_excel) |
| Quick look at a sheet |
markitdown file.xlsx — ## SheetName per sheet; reads .xlsm too. No cell coordinates, so don't plan edits from it |
| Read a model (formulas and values) |
two load_workbook passes — see gotchas |
openpyxl, pandas, and markitdown are preinstalled — do not run pip install first; write the script and import directly. Only if an import fails (or the markitdown command is missing): pip install the missing package.
Script paths below are relative to this skill's directory.
Requirements for every output
- Professional font (Arial, Times New Roman) throughout, unless the user says otherwise.
- Zero formula errors. Never ship while
formula_refresh.py reports errors_found. If you think an error predates you, prove it: load the original with data_only=True and look at that cell. An error you introduced looks exactly like one you inherited.
- Use formulas, never hardcoded results. Write
sheet['B10'] = '=SUM(B2:B9)', not the Python-computed total. The sheet must recalculate when its inputs change.
- Follow the user's spec literally. Exact tab names, exact column headers, and the formula they spelled out. A redesign that computes something else fails, however elegant.
- Document every assumption and hardcoded number where the reader will see it — a cell comment, or an adjacent cell at a table's end. Cite a real source when one exists (
Source: Company 10-K, FY2024, Page 45, Revenue Note, [SEC EDGAR URL]); when the number came from the user, say so plainly.
- A workbook you create for someone to fill in needs a short legend naming which cells to edit, and one example row of realistic values showing the expected format. Never add such a row to a file you were asked to edit.
- Editing an existing file: match its conventions exactly. They override every guideline here. Find its designated input cells first — a distinct font color, fill, or shading marks them — write only there, and leave every existing formula untouched.
Recalculate (mandatory whenever the file contains formulas)
openpyxl writes formulas as strings with no cached values. Until you recalculate, every
formula cell reads back as None to anything reading cached values — pandas,
load_workbook(data_only=True), and most previewers.
python scripts/formula_refresh.py output.xlsx [timeout_seconds] # default 30
LibreOffice computes every formula, the file is rewritten in place, and you get JSON:
status (success | errors_found), total_formulas, total_errors, and an
error_summary naming up to 100 cells per error type (locations_truncated says how many it
withheld — trust total_errors, not the length of the list). Fix what it names and run it
again. JSON with an error key instead of a status means nothing was recalculated, and
only that case exits non-zero — errors_found exits 0, so never treat a clean exit as a clean
workbook.
A green recalc proves your formulas evaluate, not that they are right. An off-by-one
range or a reference to the wrong row yields a clean, error-free file with wrong numbers.
Write 2–3 formulas first and check they pull the values you expect, before building out a grid.
A workbook that links to another file loses those links if you re-save it with openpyxl and
then recalculate. Such a formula reads ='[1]Returns Analysis'!$B$2 — the [1] is an index
into the workbook's external-reference list, naming a separate file on disk, not a sheet.
That file is rarely present here, so the cell's cached value is the only thing holding its
data. openpyxl strips that value on save; LibreOffice then has to resolve the reference for
real, fails, writes #NAME?, and deletes every link. formula_refresh.py refuses to run in that state
— copy those cells' values out of the original before you save over them (--force overrides,
and accepts the loss).
Choosing formulas that survive verification
LibreOffice implements fewer functions than Excel, and one it cannot evaluate becomes a
literal #NAME? baked into the file you deliver.
- Prefer Excel-2007-era functions —
SUMIFS, INDEX, MATCH, IFERROR, SUMPRODUCT — which need no prefix.
- Six post-2007 functions work, but only with an
_xlfn. prefix, because openpyxl writes your formula into the XML verbatim and Excel stores post-2007 names prefixed (its UI hides the prefix): _xlfn.TEXTJOIN, _xlfn.CONCAT, _xlfn.IFS, _xlfn.SWITCH, _xlfn.MAXIFS, _xlfn.MINIFS. Written bare, each yields #NAME?.
- Never use
XLOOKUP, XMATCH, SORT, FILTER, UNIQUE, or SEQUENCE. The runtime's LibreOffice cannot evaluate them under any prefix. Newer builds do evaluate them, but they are spilling array functions and an openpyxl-written file has no spill metadata, so only the top-left cell of the range gets a value — and formula_refresh.py reports total_errors: 0 on the truncated result. Use INDEX/MATCH for lookups, and sort, filter, and de-duplicate in Python before writing the cells.
- A formula LibreOffice could not parse is written back lowercased — a quick tell beside a
#NAME?.
openpyxl gotchas
- Reading a model takes two loads.
data_only=True yields cached values with the formulas gone; the default yields formula strings with no values. One pass cannot give you both.
data_only=True is destructive if you save. That workbook has no formulas left, so saving replaces every one with a literal — permanently.
data_only=True on a file openpyxl just wrote returns None everywhere — run formula_refresh.py first. (A formula whose result is "" also reads back as None.)
- Merged cells: write the top-left anchor only. Every other cell in the range is a
MergedCell whose .value is read-only.
.xlsm loses its macros unless you pass keep_vba=True to load_workbook.
- A sheet name containing a space must be quoted in a cross-sheet reference:
='Assumptions Inputs'!$B$5. Unquoted, it evaluates to #VALUE!.
Financial models
Unless the user says otherwise, or the existing file already does something else.
Color: blue text (0,0,255) for hardcoded inputs and scenario levers · black for formulas ·
green (0,128,0) for links to another sheet · red (255,0,0) for links to another file ·
yellow fill (255,255,0) for key assumptions and cells the user should fill in.
Numbers: currency $#,##0, with the unit named in the header (Revenue ($mm)) · zeros
render as -, including in percentages ($#,##0;($#,##0);-) · negatives in parentheses ·
percentages 0.0%, stored as fractions (0.15 renders 15.0%; storing 15 renders
1500.0%) · valuation multiples 0.0x · years as text ("2024", never 2,024).
Structure: every assumption in its own labeled cell, referenced by the formulas that use it
(=B5*(1+$B$6), never =B5*1.05) · formulas consistent across every projection period, since a
lone edited cell mid-row is the commonest silent error · guard denominators that can be zero.
Dependencies
openpyxl, pandas, markitdown (pip, preinstalled — install only if an import fails or the command is missing) · LibreOffice (soffice, auto-configured for sandboxed environments via scripts/ecmadoc/lo_runner.py)
1---2name: xlsx3version: 1.0.24description: "Use this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like \"the xlsx in my downloads\") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved."5description_zh: "当电子表格文件是主要输入或输出时使用此技能。包括:打开、读取、编辑或修复现有的 .xlsx、.xlsm、.csv 或 .tsv 文件(如添加列、计算公式、格式化、图表、清洗数据);从零或其他数据源创建新电子表格;在表格文件格式之间转换。当用户提及电子表格文件名或路径时触发——即使是随意提及(如\"下载文件夹里的 xlsx\")——并希望对其进行操作或生成电子表格。也适用于将混乱的表格数据文件(格式错误的行、错位的表头、垃圾数据)清理重组为规范的电子表格。交付物必须是电子表格文件。当主要交付物是 Word 文档、HTML 报告、独立 Python 脚本、数据库管道或 Google Sheets API 集成时,即使涉及表格数据也不要触发。"6license: Proprietary. LICENSE.txt has complete terms7metadata:8 source: https://skillmd.com/skills/ahang1598/xlsx9---1011# XLSX creation, editing, and analysis1213| Task | Approach |14|---|---|15| **Create** or **edit** with formulas/formatting | `openpyxl` — see gotchas below |16| **Bulk data** in or out | `pandas` (`read_excel`, `to_excel`) |17| **Quick look** at a sheet | `markitdown file.xlsx` — `## SheetName` per sheet; reads `.xlsm` too. No cell coordinates, so don't plan edits from it |18| **Read** a model (formulas *and* values) | two `load_workbook` passes — see gotchas |1920> `openpyxl`, `pandas`, and `markitdown` are preinstalled — do not run `pip install` first; write the script and import directly. Only if an import fails (or the `markitdown` command is missing): `pip install` the missing package.2122> Script paths below are relative to this skill's directory.2324## Requirements for every output2526- **Professional font** (Arial, Times New Roman) throughout, unless the user says otherwise.27- **Zero formula errors.** Never ship while `formula_refresh.py` reports `errors_found`. If you think an error predates you, prove it: load the *original* with `data_only=True` and look at that cell. An error you introduced looks exactly like one you inherited.28- **Use formulas, never hardcoded results.** Write `sheet['B10'] = '=SUM(B2:B9)'`, not the Python-computed total. The sheet must recalculate when its inputs change.29- **Follow the user's spec literally.** Exact tab names, exact column headers, and the formula they spelled out. A redesign that computes something else fails, however elegant.30- **Document every assumption and hardcoded number** where the reader will see it — a cell comment, or an adjacent cell at a table's end. Cite a real source when one exists (`Source: Company 10-K, FY2024, Page 45, Revenue Note, [SEC EDGAR URL]`); when the number came from the user, say so plainly.31- **A workbook *you create* for someone to fill in** needs a short legend naming which cells to edit, and one example row of realistic values showing the expected format. Never add such a row to a file you were asked to edit.32- **Editing an existing file: match its conventions exactly.** They override every guideline here. Find its designated input cells first — a distinct font color, fill, or shading marks them — write only there, and leave every existing formula untouched.3334## Recalculate (mandatory whenever the file contains formulas)3536openpyxl writes formulas as strings with **no cached values**. Until you recalculate, every37formula cell reads back as `None` to anything reading cached values — `pandas`,38`load_workbook(data_only=True)`, and most previewers.3940```bash41python scripts/formula_refresh.py output.xlsx [timeout_seconds] # default 3042```4344LibreOffice computes every formula, the file is **rewritten in place**, and you get JSON:45`status` (`success` | `errors_found`), `total_formulas`, `total_errors`, and an46`error_summary` naming up to 100 cells per error type (`locations_truncated` says how many it47withheld — trust `total_errors`, not the length of the list). Fix what it names and run it48again. **JSON with an `error` key instead of a `status` means nothing was recalculated**, and49only that case exits non-zero — `errors_found` exits 0, so never treat a clean exit as a clean50workbook.5152**A green recalc proves your formulas *evaluate*, not that they are *right*.** An off-by-one53range or a reference to the wrong row yields a clean, error-free file with wrong numbers.54Write 2–3 formulas first and check they pull the values you expect, before building out a grid.5556**A workbook that links to another file loses those links** if you re-save it with openpyxl and57then recalculate. Such a formula reads `='[1]Returns Analysis'!$B$2` — the `[1]` is an index58into the workbook's external-reference list, naming a *separate file on disk*, not a sheet.59That file is rarely present here, so the cell's cached value is the only thing holding its60data. openpyxl strips that value on save; LibreOffice then has to resolve the reference for61real, fails, writes `#NAME?`, and deletes every link. `formula_refresh.py` refuses to run in that state62— copy those cells' values out of the original before you save over them (`--force` overrides,63and accepts the loss).6465## Choosing formulas that survive verification6667LibreOffice implements fewer functions than Excel, and one it cannot evaluate becomes a68literal `#NAME?` baked into the file you deliver.6970- **Prefer Excel-2007-era functions** — `SUMIFS`, `INDEX`, `MATCH`, `IFERROR`, `SUMPRODUCT` — which need no prefix.71- **Six post-2007 functions work, but only with an `_xlfn.` prefix**, because openpyxl writes your formula into the XML verbatim and Excel stores post-2007 names prefixed (its UI hides the prefix): `_xlfn.TEXTJOIN`, `_xlfn.CONCAT`, `_xlfn.IFS`, `_xlfn.SWITCH`, `_xlfn.MAXIFS`, `_xlfn.MINIFS`. Written bare, each yields `#NAME?`.72- **Never use `XLOOKUP`, `XMATCH`, `SORT`, `FILTER`, `UNIQUE`, or `SEQUENCE`.** The runtime's LibreOffice cannot evaluate them under *any* prefix. Newer builds do evaluate them, but they are spilling array functions and an openpyxl-written file has no spill metadata, so only the top-left cell of the range gets a value — and `formula_refresh.py` reports `total_errors: 0` on the truncated result. Use `INDEX`/`MATCH` for lookups, and sort, filter, and de-duplicate in Python before writing the cells.73- A formula LibreOffice could not parse is written back **lowercased** — a quick tell beside a `#NAME?`.7475## openpyxl gotchas7677- **Reading a model takes two loads.** `data_only=True` yields cached values with the formulas gone; the default yields formula strings with no values. One pass cannot give you both.78- **`data_only=True` is destructive if you save.** That workbook has no formulas left, so saving replaces every one with a literal — permanently.79- **`data_only=True` on a file openpyxl just wrote returns `None` everywhere** — run `formula_refresh.py` first. (A formula whose result is `""` also reads back as `None`.)80- **Merged cells: write the top-left anchor only.** Every other cell in the range is a `MergedCell` whose `.value` is read-only.81- **`.xlsm` loses its macros unless you pass `keep_vba=True`** to `load_workbook`.82- **A sheet name containing a space must be quoted** in a cross-sheet reference: `='Assumptions Inputs'!$B$5`. Unquoted, it evaluates to `#VALUE!`.8384## Financial models8586Unless the user says otherwise, or the existing file already does something else.8788**Color:** blue text (`0,0,255`) for hardcoded inputs and scenario levers · black for formulas ·89green (`0,128,0`) for links to another sheet · red (`255,0,0`) for links to another file ·90yellow fill (`255,255,0`) for key assumptions and cells the user should fill in.9192**Numbers:** currency `$#,##0`, with the unit named in the header (`Revenue ($mm)`) · zeros93render as `-`, including in percentages (`$#,##0;($#,##0);-`) · negatives in parentheses ·94percentages `0.0%`, **stored as fractions** (`0.15` renders `15.0%`; storing `15` renders95`1500.0%`) · valuation multiples `0.0x` · years as text (`"2024"`, never `2,024`).9697**Structure:** every assumption in its own labeled cell, referenced by the formulas that use it98(`=B5*(1+$B$6)`, never `=B5*1.05`) · formulas consistent across every projection period, since a99lone edited cell mid-row is the commonest silent error · guard denominators that can be zero.100101## Dependencies102103`openpyxl`, `pandas`, `markitdown` (pip, preinstalled — install only if an import fails or the command is missing) · LibreOffice (`soffice`, auto-configured for sandboxed environments via `scripts/ecmadoc/lo_runner.py`)