domains / families / documents / xlsx
Comprehensive spreadsheet creation, editing, and analysis with support for formulas, formatting, data analysis, and visualization. When Claude needs to work with spreadsheets (.xlsx, .xlsm, .csv, .tsv, etc) for: (1) Creating new spreadsheets with formulas and formatting, (2) Reading or analyzing data, (3) Modify existing spreadsheets while preserving formulas, (4) Data analysis and visualization in spreadsheets, or (5) Recalculating formulas 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, .xltx, .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.
The anthropics/skills copy is the upstream, most complete procedure: it defines the tool-selection table, the mandatory recalc.py contract (JSON status, exit-code semantics, external-link loss, and the _xlfn. prefix rules), and the 'follow the user's spec literally' constraint. The other three copies (zLanqing, foryourhealth111-pixel, Prat011) reproduce the financial-modeling requirements (color coding, number formatting, formula construction rules) and the pandas/openpyxl workflow, but they omit the recalc.py JSON contract and the formula-compatibility rules, and they add material steps the upstream copy lacks (e.g., foryourhealth111-pixel's scientific-schematics section). Crowning one copy would hide either the recalculation contract or the financial-modeling conventions, so the copies must be combined.