xlsx

Overview of xlsx skill

What xlsx does

The xlsx skill is for tasks where a spreadsheet file is the main input or the required output. Use it when you need to read, create, repair, update, or convert .xlsx, .xlsm, .csv, or .tsv files and the end result should be a spreadsheet, not just an explanation or a script.

Best fit for this xlsx skill

This xlsx skill is best for people who need dependable spreadsheet work in an agent workflow: finance models, ops trackers, tabular cleanups, template updates, bulk formula fills, formatting fixes, chart-ready workbooks, and file conversion. It is especially relevant when a user mentions a real file path and expects a modified workbook back.

The real job-to-be-done

Most users do not need a generic “analyze this table” prompt. They need a workbook that opens correctly, preserves structure, keeps formatting sane, and avoids broken formulas. The xlsx skill is built around that practical outcome: produce spreadsheet files that are usable in Excel-style workflows, not merely describe what should be done.

What makes xlsx different

The strongest differentiator is its output discipline. The skill emphasizes professional spreadsheet deliverables, zero formula errors, and preserving existing templates when editing established files. The repo also includes helper scripts for unpacking and repacking Office files and recalculating formulas through LibreOffice, which is more concrete than a plain prompt-only spreadsheet workflow.

Key adoption caveats

This is not the right fit if your real deliverable is a Python ETL, database pipeline, Google Sheets integration, HTML report, or Word document. It is also not a general spreadsheet theory guide. The xlsx skill is narrowly useful when file fidelity and workbook output matter more than discussing data in the abstract.

Licensing and usage constraints

The repository skill materials are under Anthropic terms, with additional restrictions in LICENSE.txt. For directory users, the practical point is simple: treat this as an in-service skill resource, not a reusable open-source spreadsheet toolkit you can freely extract and redistribute.

How to Use xlsx skill

xlsx install context

The repository does not advertise a dedicated install command inside SKILL.md, but in the Anthropic skills workflow users commonly add it with:

npx skills add https://github.com/anthropics/skills --skill xlsx

After install, this xlsx skill should be invoked whenever the task centers on spreadsheet file creation or modification.

What inputs the xlsx skill needs

Give the skill the actual file context, not just a vague objective. Strong inputs include:

• file path or uploaded workbook
• sheet names
• target columns or ranges
• desired formulas
• formatting expectations
• whether existing templates must be preserved exactly
• required output format: .xlsx, .xlsm, .csv, or .tsv

If the workbook is messy, say what counts as the header row, which fields are authoritative, and what should happen to malformed rows.

Turn a rough goal into a usable xlsx prompt

Weak prompt:

• “Fix this spreadsheet.”

Better xlsx usage prompt:

• “Update forecast.xlsx. In sheet Q3 Plan, add a new column Gross Margin % after column H, fill formulas for all populated rows, preserve all existing formatting and formulas elsewhere, and ensure the workbook opens with no formula errors.”

That level of specificity matters because this skill is optimized for file output quality, not speculative interpretation.

Prompt pattern that improves output quality

A reliable prompt template for xlsx for Spreadsheet Workflows is:

1. identify the file
2. name the exact sheets involved
3. state the structural changes
4. define calculation rules
5. state preservation rules
6. define the required output file

Example:

• “Using sales_template.xlsm, update only the Monthly Summary and Raw Data sheets. Import the attached CSV into Raw Data, keep macros untouched, preserve all existing styles, refresh dependent formulas, and return a corrected .xlsm.”

Recommended workflow in practice

A practical xlsx usage workflow is:

1. inspect workbook structure and tabs
2. identify whether this is a clean build, template edit, or repair job
3. make targeted sheet-level changes
4. check formulas and references
5. recalculate if needed
6. return the workbook in the requested format

This sequence reduces the most common failure: making a valid-looking sheet that breaks downstream references or template conventions.

Read these repository files first

If you want to understand how the skill works before trusting it, start here:

• skills/xlsx/SKILL.md
• skills/xlsx/scripts/recalc.py
• skills/xlsx/scripts/office/unpack.py
• skills/xlsx/scripts/office/pack.py
• skills/xlsx/scripts/office/soffice.py
• skills/xlsx/scripts/office/validate.py

That file path is the fastest route to understanding actual behavior rather than just reading the high-level description.

Why the helper scripts matter

The included scripts show that xlsx is not only about table edits. The repo supports Office-file unpack/pack workflows and formula recalculation with LibreOffice. That matters when normal workbook edits leave cached formulas stale or when you need more controlled handling of OOXML package contents.

Recalculation and LibreOffice expectations

scripts/recalc.py uses LibreOffice to force formula recalculation and save the workbook. That is useful when the workbook must ship with computed values refreshed, especially after structural edits. In adoption terms, this means the xlsx skill is more convincing if your environment can run soffice.

Environment dependencies to know early

If you plan deeper xlsx automation around the bundled scripts, expect dependencies such as:

• Python environment for the helper scripts
• openpyxl
• LibreOffice / soffice
• in some environments, a compiler like gcc for the soffice shim path used by scripts/office/soffice.py

This does not block normal skill usage, but it does affect whether you can reproduce the repo’s validation and recalculation workflow locally.

Template-preserving edits need explicit instructions

One of the most important xlsx guide points from the skill is to preserve existing templates exactly when updating them. If you are editing a finance model, board-report workbook, or regulated template, explicitly say:

• do not restyle the workbook
• keep fonts, widths, number formats, and sheet order
• change only specified cells, columns, or tabs

Without that constraint, a generic spreadsheet edit may technically solve the data task while still failing the business task.

Where xlsx is strongest

The xlsx skill is strongest when the work is concrete and bounded:

• add formulas
• clean imported rows
• convert CSV/TSV into a usable workbook
• update existing sheets without breaking layout
• produce polished spreadsheet deliverables with low tolerance for formula errors

It is less compelling for exploratory data analysis where a notebook, SQL workflow, or BI tool is the real destination.

xlsx skill FAQ

Is xlsx better than an ordinary spreadsheet prompt?

Usually yes, when the output must be a real workbook. Ordinary prompts often optimize for explanation. The xlsx skill is framed around spreadsheet deliverables, preservation of workbook structure, and practical file-editing constraints.

Is the xlsx skill beginner-friendly?

Yes, if your task is concrete. Beginners can use xlsx successfully when they provide the file, specify the desired changes, and avoid underdefined requests like “make this more professional.” The skill performs best when the workbook job is explicit.

When should I not use xlsx?

Do not use xlsx when the final deliverable is primarily:

• a script
• a database workflow
• a web report
• a Google Sheets API integration
• a narrative analysis with no spreadsheet file needed

In those cases, the xlsx skill adds less value than a code, analytics, or reporting-oriented skill.

Does xlsx handle broken formulas and workbook repair?

That is one of the main reasons to choose it. The skill explicitly prioritizes zero formula errors, and the repo includes recalculation support. Still, the quality of repair depends on how clearly you describe the intended workbook logic.

Can xlsx work with CSV and TSV too?

Yes. The xlsx skill covers .csv and .tsv when the goal is to clean, restructure, or convert tabular data into a proper spreadsheet output.

Is xlsx suitable for macro-enabled files?

Potentially, yes, especially for limited updates to .xlsm files. But macro-enabled workbooks are higher risk. Be explicit about preserving macros and avoiding unrelated edits, because the safest use case is targeted modification rather than deep VBA refactoring.

How to Improve xlsx skill

Give business rules, not just edit instructions

The fastest way to improve xlsx results is to explain the workbook logic. Instead of “fill formulas down,” say “calculate Net Revenue = Gross Revenue - Discounts - Refunds for every non-empty row in Transactions.” This helps the skill catch structural mismatches and formula edge cases.

Name the non-negotiables up front

For strong xlsx usage, specify what must not change:

• sheet names
• formulas outside target ranges
• macros
• formatting
• hidden tabs
• named ranges
• column order

These constraints matter more than broad style requests because spreadsheet tasks often fail through unintended collateral edits.

Reduce ambiguity around messy data

If your source data is inconsistent, tell the xlsx skill how to normalize it:

• which row is the true header
• whether blank rows should be dropped
• how to handle duplicate IDs
• whether dates are MM/DD/YYYY or DD/MM/YYYY
• what values count as null

This is often the difference between a usable workbook and a superficially cleaned one.

Ask for verification, not just output

A better xlsx guide prompt asks for checks such as:

• confirm no formula errors remain
• verify sheet references after column insertion
• preserve existing styles in untouched areas
• ensure totals still reconcile

Those checks align with the skill’s strongest value: trustworthy spreadsheet output.

Use iteration after the first workbook pass

After the first result, review:

• formulas in a few representative rows
• formatting at boundaries
• totals and rollups
• external-looking references
• hidden assumptions in cleaned data

Then issue a narrow second prompt. Iterative xlsx work usually improves faster when you correct one workbook behavior at a time instead of restating the whole task.

Watch for common failure modes

The most likely xlsx failure modes are:

• broken references after inserting columns
• formulas copied into the wrong row span
• accidental restyling of an existing template
• text-number or date parsing mistakes
• stale calculated values if recalculation is skipped

These are exactly the issues to mention in your prompt if the workbook is business-critical.

Improve results with sample rows and target examples

If you can, provide:

• 3 to 10 representative rows
• one example of a correct final formula
• one example of desired formatting
• one example of a bad row and how it should be fixed

For xlsx for Spreadsheet Workflows, examples beat abstract instructions because they anchor both structure and expected output.

Use the repo scripts when fidelity matters most

If you are evaluating the xlsx skill seriously, inspect and use the helper scripts rather than relying only on a skim of SKILL.md. unpack.py, pack.py, and recalc.py reveal the repo’s practical stance on OOXML handling, validation, and recalculation. That gives you a better install decision than a generic feature summary.

Know the ceiling of the xlsx skill

The xlsx skill improves spreadsheet-output reliability, but it does not remove the need for domain review in complex finance, audit, or regulatory models. If one incorrect formula could create material risk, use xlsx as an accelerator and still review the workbook logic carefully.