xlsx — Skill for reading, editing, creating, and converting spreadsheet files (.xlsx, .xlsm, .csv, .tsv)

draft — generated, polish on first use.

Category: skills Where it works: Claude Code / Telegram (Hermes) / both Source: /Users/dexter/.hermes/skills/xlsx/SKILL.md

What it is

Skill that activates when a spreadsheet file is the primary input or output. Handles opening, reading, editing, formatting, cleaning, and creating .xlsx/.xlsm/.csv/.tsv files. Delivers a spreadsheet file as the final output.

How to trigger it

• Natural language phrases the operator would actually say (quote 3-6).
  • “open the xlsx in my downloads”
  • “clean this spreadsheet”
  • “add a column to the budget file”
  • “convert this csv to xlsx”
  • “fix the formulas in this workbook”
• Direct command/trigger if any: none (skill-based, context-triggered).
• Auto-fires? yes — when user references a spreadsheet file by name/path or requests tabular data transformation.

How to use it

Operator mentions or attaches a spreadsheet file and states the desired action (read, edit, clean, format, create). Skill processes the file per requirements (professional fonts, zero formula errors, color coding standards for financial models). Returns the modified or new .xlsx file.

Practical examples

1. you: “clean the messy data in Q3-report.xlsx” → result: standardized headers, removed junk rows, consistent formatting, zero formula errors, file returned.
2. you: “create a budget model from this csv” → result: new .xlsx with blue input cells, black formulas, yellow key assumptions, proper currency formatting.

Notes / limits

Requires the deliverable to be a spreadsheet file — does not trigger for Word/HTML/script outputs. Must follow financial model color standards (blue inputs, black formulas) unless existing template dictates otherwise. Verify doctrine for edge cases with malformed files or non-tabular deliverables.