Anthropic XLSX
Create and edit spreadsheets, including formulas, multiple sheets and charts.
npx skills add anthropics/skills --skill xlsxClaude skills for spreadsheets: build tables, update formulas and charts, and recalculate workbooks before sharing.
Create and edit spreadsheets, including formulas, multiple sheets and charts.
npx skills add anthropics/skills --skill xlsxCreate, edit, and validate XLSX files in a workflow that also supports PDF, DOCX, XLSX, and PPTX.
A spreadsheet is not a table. It is formulas, cross-sheet references, number formats and charts that all have to stay consistent after an agent touches the file. A Claude XLSX skill earns its place by writing formulas instead of frozen values, and by leaving you a workbook you can recalculate and audit.
The failure mode that costs the most time is a column of plausible numbers with no formulas behind it. Next month the input changes and the total does not. Ask for the formula and the cell range explicitly, then change one input and watch whether the dependent cells move. If they do not, the agent wrote values instead of formulas.
Cross-sheet references are where an automated edit most often goes wrong: a formula that pointed at 'Q3 Inputs' ends up pointing at the active sheet, and the error is invisible until someone reads the number. Name the sheets in your request and re-check any total that pulls from another sheet. Totals built from several sheets deserve a second look against the source.
Charts can survive an edit while pointing at a stale range, so open each chart and confirm the source range matches the new rows. Number formats are the quiet one: a percentage written as 0.185 shows 0.185 until the cell format changes, and a currency column can silently drop its symbol. Check one currency column, one percentage column and every chart's data range.
CSV carries values, not formulas, styles or multiple sheets, which is exactly what an import into another system wants. It is the wrong output when a person has to recalculate anything later. If a workflow needs both, ask for the workbook first and export a CSV from the finished file, then check that the export has no hidden columns and no extra header rows.
Use the dedicated XLSX skill for working formulas, charts and workbook edits. A cross-format skill can help when a workbook and a separate report need to share the same numbers. Either way, ask for formulas, not values, and name the sheets you expect the agent to touch.
Recalculate the file, change one input and inspect a dependent total. Confirm any CSV export only includes the data intended for that file, and open each chart to check its source range still covers the new rows.
Start with Anthropic XLSX and ask for formulas rather than results. After the edit, change one input cell and check that the dependent totals move; if they stay frozen, the agent wrote values instead of formulas.
It can edit an existing workbook when you give it the file and say which range to change, but formulas, charts and formats are the parts most likely to shift. Keep the original, then compare formulas and chart ranges against your copy before sharing.
Choose XLSX for formulas, styles and multiple sheets. Choose CSV for exchanging plain tabular data. A CSV keeps values only, so anything that has to be recalculated later should stay in XLSX.
Recalculate first, then check one currency column, one percentage column and every chart's source range. Test one cross-sheet total against the source sheet; that is where a broken reference usually hides.
Ask for the workbook first and export the CSV from the finished file, rather than running two separate edits. Then scan the export for hidden columns, extra header rows and values that should have been blank.