agentleFS
kiku-jwkiku-jw/codex-skills/spreadsheet-xlsx-edit/SKILL.md

spreadsheet-xlsx-edit

Skill0 starsChanged 4 months agoMITView on GitHub

Create or edit `.xlsx` workbooks while preserving formulas, references, formatting, and layout. Use when workbook integrity matters more than raw data analysis.

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Do not use when: the job is mainly aggregation, joins, filtering, or analysis over CSV/TSV/tabular data.

    line 10
  2. Distinctive:

    If formula evaluation or visual rendering cannot be fully verified in this environment, that caveat is stated clearly.

    line 25

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Spreadsheet XLSX Edit

Metadata

  • Trigger when: the task is to create or edit .xlsx files without breaking formulas, styles, sheet structure, or references.
  • Do not use when: the job is mainly aggregation, joins, filtering, or analysis over CSV/TSV/tabular data.

Skill Purpose

Make targeted .xlsx changes with openpyxl while preserving workbook integrity instead of flattening the file into disposable data.

Instructions

  1. Inspect the workbook first: target sheets, named ranges, formulas, styles, and the exact cells or structures that need to change. Use openpyxl and consult ~/.codex/skills/spreadsheet/references/examples/openpyxl only when you need a concrete pattern.
  2. Apply the minimal workbook change that satisfies the task while preserving formulas, references, merged cells, widths, formatting, and sheet structure. Save the result under a stable descriptive path such as output/spreadsheet/.
  3. Validate formulas, references, number/date formats, and visible layout. If layout matters and soffice plus pdftoppm are available, render for visual review; otherwise state that local eyeballing is still needed.

Non-Negotiable Acceptance Criteria

  • Existing formatting is preserved unless the user explicitly asked for redesign.
  • Derived cells remain formulas when formulas are the correct source of truth.
  • Structural workbook changes are intentional and explicit; no silent sheet damage or broken refs.
  • If formula evaluation or visual rendering cannot be fully verified in this environment, that caveat is stated clearly.

Output

  • The final workbook path.
  • Any render artifact path used for visual validation.
  • A short note on formulas, style preservation, and remaining validation caveats.
  • Next skill options (only if needed): $spreadsheet-tabular-analysis — use when the task turns into aggregation, joins, or reshaping rather than workbook-preserving edits.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.