xlsx-edit
Skill0 starsChanged 47 days agoMITView on GitHub
Make small, hash-bound changes to existing literal XLSX cells while preserving unrelated archive members, pictures and formula expressions. Use for local quantity or text corrections without rebuilding an existing workbook.
In this repository8 other files it gives its agents.
- freight-estimatorSkill
- invoice-builderSkill
- landed-costSkill
- multi-quoteSkill
- quote-auditSkill
- supplier-rfqSkill
- translate-rfqSkill
- whatsapp-rfqSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 0 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 9
Run python scripts/edit_xlsx.py inspect SOURCE.xlsx --cell "Sheet Name" E6.
- Very specific: line 11
Run python scripts/edit_xlsx.py apply SOURCE.xlsx PATCH.json --output NEW.xlsx.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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.
Files
Bounded spreadsheet edits
- Inspect the source and choose existing, nonformula cells. Structural changes (rows, merges, sheet names, drawings) require a different spreadsheet editor and its own preservation check.
- Run
python scripts/edit_xlsx.py inspect SOURCE.xlsx --cell "Sheet Name" E6. Repeat--cell SHEET CELLfor more cells. This returns the source SHA-256 and current expected values. - Make a JSON patch with exactly
source_sha256and a nonemptychangeslist. Each change is{sheet,cell,expected,value}. Keep the reportedexpectedunchanged; add the intendedvalue(string, number, boolean or null). A whole-cell text replacement intentionally replaces any existing rich-text runs in that cell. - Run
python scripts/edit_xlsx.py apply SOURCE.xlsx PATCH.json --output NEW.xlsx. Output must be a new, different filename. Source hash, expected values, duplicate cells and unsupported cells are checked before publication. - Inspect the edited values and images. All formula expressions are retained, but every worksheet formula cache is cleared and workbook recalculation is requested, because changing an input can invalidate distant totals. Open with a spreadsheet application, recalculate and save before using formula results or running quote-audit. Never treat an empty cache as a zero total.
Only XLSX cell values are supported, without external dependencies. Signed/encrypted/duplicate-entry files and packages over 512 MiB unpacked are rejected. Unrelated ZIP-member contents are verified byte-for-byte; ZIP compression bytes may differ. A preserved image can still contain private information. The output filesystem must support hard links. There is no claim that arbitrary structural changes, macros or protected workbooks are supported.
Repository demo: generate examples/multi-quote.json, then use examples/make_demo_edit.py to create the quantity-change patch.
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
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.

