Xlsx
Build and analyze Excel (.xlsx) workbooks — formulas, multiple sheets, and tabular exports — from an agent instead of CSV paste.
Get the complete skill folder, including its scripts and reference files.
·
Turn a PDF table into a usable Excel sheet
Extract six invoice lines, keep their source references, and reconcile the result before using it. (2 sample files)
Turn a sales spreadsheet into a monthly report
Check two months of figures, build a formula-backed summary, and write an editable one-page review. (3 sample files)
When to use this skill
Use the Excel skill when the deliverable is a workbook: budget, tracker, model, or a sheet other people will filter in Excel or Google Sheets.
When not to use it
Use PDF for a snapshot report nobody should edit. Use a database or script when the sheet would exceed what Excel can honestly hold.
How to install
Where will you use it?
Install the publisher’s plugin
This installs a bundle that can include other skills. Choose this method or the manual alternative below; you only need one installation.
Run these commands in Claude Code:
Claude Code CLI/plugin marketplace add anthropics/skills /plugin install document-skills@anthropic-agent-skills
- Ask Claude Code to use Xlsx on a small task and confirm that it loads. Check the setup requirements in the publisher’s guide if it cannot run.
Alternative: install the folder manually
Use these steps if you choose the manual folder method. If you installed the plugin above, skip this alternative.
- Claude Code personal install: place the skill and its bundled files at ~/.claude/skills/xlsx/SKILL.md. For a shared project, commit the folder at .claude/skills/xlsx/ instead.
- Current Claude Code detects SKILL.md changes in watched directories during the session. If you just created a top-level skills directory, run /reload-skills. Check that the skill is listed before testing its trigger.
- For Claude chat or Cowork in the Desktop app, manage uploaded skills in Customize > Skills; copying files into a local Claude Code folder is not a Desktop install. Other agents may use different install locations.
What supports this recommendation?
67/100 provisional content score. This measures documentation, practical detail and source signals. It is not a measured task success rate or a security certification.
- Documentation
- 67/100
- Practical detail
- 50/100
- Source evidence
- 70/100
- Source signals
- 94/100
Model compatibility evidence
- claudeuntested
No model-specific signal or recorded compatibility test was found.
- chatgptuntested
No model-specific signal or recorded compatibility test was found.
- geminiuntested
No model-specific signal or recorded compatibility test was found.
- copilotuntested
No model-specific signal or recorded compatibility test was found.
- llamauntested
No model-specific signal or recorded compatibility test was found.
- perplexityuntested
No model-specific signal or recorded compatibility test was found.
- mistraluntested
No model-specific signal or recorded compatibility test was found.
- grokuntested
No model-specific signal or recorded compatibility test was found.
Inferred compatibility is based on content signals. Check the app, its available tools and setup requirements before running a skill.
Try one small task
Best first exercise: build a workbook with formulas and compare its totals with known inputs.
See actual outputs and execution limits →What you need
- A file-capable agent with Python and the spreadsheet packages required by the upstream guide.
- A spreadsheet calculation engine for formula recalculation; upstream uses LibreOffice through its bundled script.
- Download monthly-sales.xlsx or the matching CSV from the monthly report workflow.
Get the sample input and full checklist
Summarize two months of sales while keeping the underlying rows intact.
Use the XLSX skill on monthly-sales.xlsx. Create sales-summary.xlsx with Raw data and Summary sheets. Preserve all six input rows. Calculate revenue, cost, gross profit and gross margin for January and February 2026 using formulas. Define gross profit as revenue minus cost, and gross margin as gross profit divided by revenue. Recalculate, check for formula errors, and report the totals. Keep currency as USD.
Expected result
A specification to check against, not output from an AI run.
A workbook with January revenue 12,000 and gross profit 6,000; February revenue 15,000 and gross profit 7,200.
- All six source records remain available for audit.
- Summary cells contain formulas and have recalculated values without spreadsheet errors.
- Gross margins are 50% for January and 48% for February; a 25% revenue increase is not a 25% margin increase.
Where this exercise stops
- A formula that evaluates without errors can still reference the wrong cells; check the known totals.
- Macros and external workbook links are outside this starter exercise.
Recorded example runs
These files came from actual execution in a Codex session. They were produced and checked within the same session; this is scoped evidence, not independent review or a measured success rate.
PDF invoice extracted and reconciled in Excel
Executed · Automated Codex exercise
Codex agent in this session; Python 3.12.3, openpyxl 3.1.5, LibreOffice 24.2.7.2 420(Build:2); aarch64. PDF extraction: pdfplumber 0.11.10.
The agent read the pinned upstream instructions and applicable helpers, then authored and executed the committed scripts locally. This is not a native Claude skill-loader test or an independent benchmark.
Download the actual outputs
Recorded checks and observations
- Passed: All six extracted rows match the CSV answer key; leading-zero IDs are preserved.
- Passed: The recalculated subtotal is USD 1,250.00 with a USD 0.00 reconciliation difference.
- Passed: Nine formulas recalculate without errors. Changing a quantity in a copy updates the subtotal to USD 1,295.00.
Scope, limitations and pinned sources
- The agent read the pinned upstream instructions and used their prescribed tools. Native Claude skill loading and general cross-agent compatibility were not tested.
- One small synthetic input per workflow; results are not a success rate or a broad model-compatibility claim.
- The Codex agent that produced the outputs also ran and interpreted the checks; no independent human review occurred.
- PDF extraction used selectable text and regular table borders. OCR, merged cells, and multi-page PDFs were not tested.
- Spreadsheet recalculation used LibreOffice 24.2.7.2; Microsoft Excel was not run.
- This session already knew the published acceptance criteria. The CSV answer key was read by verification after PDF extraction, but this is not a blind or held-out evaluation.
Sales workbook summarized in an editable monthly report
Executed · Automated Codex exercise
Codex agent in this session; Python 3.12.3, openpyxl 3.1.5, LibreOffice 24.2.7.2 420(Build:2); aarch64. Report generation: docx 9.8.1, Node v24.13.0.
The agent read the pinned upstream instructions and applicable helpers, then authored and executed the committed scripts locally. This is not a native Claude skill-loader test or an independent benchmark.
Download the actual outputs
Recorded checks and observations
- Passed: All six input rows are preserved and the summary retains formulas.
- Passed: Recalculated January/February revenue is USD 12,000 / 15,000; gross margin is 50% / 48%.
- Passed: The DOCX contains an editable five-row table and the expected figures; all XML parts parse.
- Passed: The report renders to one page with expected text. The creating agent inspected the image and observed no clipping or overlap.
Scope, limitations and pinned sources
- The agent read the pinned upstream instructions and used their prescribed tools. Native Claude skill loading and general cross-agent compatibility were not tested.
- One small synthetic input per workflow; results are not a success rate or a broad model-compatibility claim.
- The Codex agent that produced the outputs also ran and interpreted the checks; no independent human review occurred.
- Spreadsheet recalculation used LibreOffice 24.2.7.2; Microsoft Excel was not run.
- DOCX structure and one-page LibreOffice rendering were checked; Microsoft Word and Google Docs rendering were not tested.
- The temporary LibreOffice render emitted Java-launch and liblangtag registry warnings. Conversion returned 0 and the produced PDF was inspected; unsupported language/layout cases remain untested.
- This session already knew the published acceptance criteria. The CSV answer key was read by verification after PDF extraction, but this is not a blind or held-out evaluation.
Source and evidence
The upstream instructions informed this guide. The exercise and acceptance checks are an OpxSkills test recipe. Where a run is recorded, its actual outputs, environment and limits appear separately above. A recorded example does not establish general model compatibility or a success rate.
Source reviewed · Upstream revision 8a1541c4a3ff
What this skill does
XLSX output keeps formulas and sheet structure. That is the difference between figures in a chat transcript and a workbook a finance partner can use.
Intended uses
- Turn a CSV export into a formatted workbook
- Build a simple budget with formulas
- Reconcile two sheets the agent is given in-session
Implementation notes
- Name the sheets. Default Sheet1 files are hard to review.
- Say which columns are inputs vs formulas.
Try it, then tell us how it went
A copied prompt does not tell us whether the task worked. Report your result after checking the output. We collect your tool and outcome, never your files or prompt.