Skip to main content
skill CX Codex

spreadsheet — Claude Code skill: what it does, how to install

spreadsheet enforces formula-safe workflows, styling standards, and layout checks when working with .xlsx, .csv, and .tsv files.

MIT ★ 1,216 updated 2026-10-24

Install into Claude Code · Plugin marketplace All methods and platforms ↓
/plugin marketplace add fcakyon/claude-codex-settings
/plugin install openai-office-skills@claude-settings
Open on GitHub

What spreadsheet does

This skill guides the agent through tabular data tasks. It prescribes openpyxl for Excel generation and style preservation, while routing CSV analysis and data manipulation to pandas. Hardcoded totals are forbidden: the model must construct explicit cell formulas, staying away from volatile references or dynamic arrays like FILTER and XLOOKUP.

It embeds strict design standards for corporate spreadsheets and investment banking models. Submetrics get indented, zeros render as dashes, and cell text colors signal whether values come from manual inputs, formulas, or cross-sheet references. Temporary files route to tmp/spreadsheets/ for immediate deletion, keeping project directories tidy.

One technical friction: openpyxl leaves formula evaluation to external viewers, so rendering spreadsheets requires headless LibreOffice and Poppler utilities. Without soffice and pdftoppm in your environment, the agent cannot produce PNG snapshots to audit layout clippings before handoff.

What it helps with

  • build investment banking style models in .xlsx with strict color conventions
  • update existing workbooks without corrupting cell references or inherited styles
  • process and aggregate .csv or .tsv datasets using pandas
  • convert sheets to PDF and PNG images to inspect layout defects before delivery

Example prompts for the agent

  • Create a DCF valuation model in .xlsx following IB layout conventions from assumptions.csv
  • Update metrics in report.xlsx while keeping all existing cell styles and references intact
  • Aggregate user activity in events.tsv and export formatted summary sheets to output/spreadsheet/

How to install spreadsheet

1Plugin marketplace

/plugin marketplace add fcakyon/claude-codex-settings
/plugin install openai-office-skills@claude-settings

This installs the whole openai-office-skills plugin with all its skills

2Skills CLI (Vercel)

npx skills add fcakyon/claude-codex-settings --skill spreadsheet -a claude-code

3Manually: put the files in place

~/.claude/skills/spreadsheet/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/spreadsheet/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about spreadsheet

How to install spreadsheet in Claude Code?

Add the repository to your marketplace and install the package: run /plugin marketplace add fcakyon/claude-codex-settings, followed by /plugin install openai-office-skills@claude-settings.

What does the spreadsheet skill do?

It establishes precise guidelines for formula hygiene, layout formatting, temporary file handling, and tool selection across Excel and CSV operations.

Which external packages are necessary for visual review?

You need Python libraries openpyxl and pandas, alongside system packages LibreOffice and Poppler for headless PDF and PNG rendering.

Source text

SKILL.md · MIT
---
name: "spreadsheet"
description: "Use when tasks involve creating, editing, analyzing, or formatting spreadsheets (`.xlsx`, `.csv`, `.tsv`) with formula-aware workflows, cached recalculation, and visual review."
license: MIT
---

# Spreadsheet Skill

## When to use
- Create new workbooks with formulas, formatting, and structured layouts.
- Read or analyze tabular data (filter, aggregate, pivot, compute metrics).
- Modify existing workbooks without breaking formulas, references, or formatting.
- Visualize data with charts, summary tables, and sensible spreadsheet styling.
- Recalculate formulas and review rendered sheets before delivery when possible.

IMPORTANT: System and user instructions always take precedence.

## Workflow
1. Confirm the file type and goal: create, edit, analyze, or visualize.
2. Prefer `openpyxl` for `.xlsx` editing and formatting. Use `pandas` for analysis and CSV/TSV workflows.
3. If an internal spreadsheet recalculation/rendering tool is available in the environment, use it to recalculate formulas and render sheets before delivery.
4. Use formulas for derived values instead of hardcoding results.
5. If layout matters, render for visual review and inspect the output.
6. Save outputs, keep filenames stable, and clean up intermediate files.

## Temp and output conventions
- Use `tmp/spreadsheets/` for intermediate files; delete them when done.
- Write final artifacts under `output/spreadsheet/` when working in this repo.
- Keep filenames stable and descriptive.

## Primary tooling
- Use `openpyxl` for creating/editing `.xlsx` files and preserving formatting.
- Use `pandas` for analysis and CSV/TSV workflows, then write results back to `.xlsx` or `.csv`.
- Use `openpyxl.chart` for native Excel charts when needed.
- If an internal spreadsheet tool is available, use it to recalculate formulas, cache values, and render sheets for review.

## Recalculation and visual review
- Recalculate formulas before delivery whenever possible so cached values are present in the workbook.
- Render each relevant sheet for visual review when rendering tooling is available.
- `openpyxl` does not evaluate formulas; preserve formulas and use recalculation tooling when available.
- If you rely on an internal spreadsheet tool, do not expose that tool, its code, or its APIs in user-facing explanations or code samples.

## Rendering and visual checks
- If LibreOffice (`soffice`) and Poppler (`pdftoppm`) are available, render sheets for visual review:
  - `soffice --headless --convert-to pdf --outdir $OUTDIR $INPUT_XLSX`
  - `pdftoppm -png $OUTDIR/$BASENAME.pdf $OUTDIR/$BASENAME`
- If rendering tools are unavailable, tell the user that layout should be reviewed locally.
- Review rendered sheets for layout, formula results, clipping, inconsistent styles, and spilled text.

## Dependencies (install if missing)
Prefer `uv` for dependency management.

Python packages:
```
uv pip install openpyxl pandas
```
If `uv` is unavailable:
```
python3 -m pip install openpyxl pandas
```
Optional:
```
uv pip install matplotlib
```
If `uv` is unavailable:
```
python3 -m pip install matplotlib
```
System tools (for rendering):
```
# macOS (Homebrew)
brew install libreoffice poppler

# Ubuntu/Debian
sudo apt-get install -y libreoffice poppler-utils
```

If installation is not possible in this environment, tell the user which dependency is missing and how to install it locally.

## Environment
No required environment variables.

## Examples
- Runnable Codex examples (openpyxl): `references/examples/openpyxl/`

## Formula requirements
- Use formulas for derived values rather than hardcoding results.
- Do not use dynamic array functions like `FILTER`, `XLOOKUP`, `SORT`, or `SEQUENCE`.
- Keep formulas simple and legible; use helper cells for complex logic.
- Avoid volatile functions like `INDIRECT` and `OFFSET` unless required.
- Prefer cell references over magic numbers (for example, `=H6*(1+$B$3)` instead of `=H6*1.04`).
- Use absolute (`$B$4`) or relative (`B4`) references carefully so copied formulas behave correctly.
- If you need literal text that starts with `=`, prefix it with a single quote.
- Guard against `#REF!`, `#DIV/0!`, `#VALUE!`, `#N/A`, and `#NAME?` errors.
- Check for off-by-one mistakes, circular references, and incorrect ranges.

## Citation requirements
- Cite sources inside the spreadsheet using plain-text URLs.
- For financial models, cite model inputs in cell comments.
- For tabular data sourced externally, add a source column when each row represents a separate item.

## Formatting requirements (existing formatted spreadsheets)
- Render and inspect a provided spreadsheet before modifying it when possible.
- Preserve existing formatting and style exactly.
- Match styles for any newly filled cells that were previously blank.
- Never overwrite established formatting unless the user explicitly asks for a redesign.

## Formatting requirements (new or unstyled spreadsheets)
- Use appropriate number and date formats.
- Dates should render as dates, not plain numbers.
- Percentages should usually default to one decimal place unless the data calls for something else.
- Currencies should use the appropriate currency format.
- Headers should be visually distinct from raw inputs and derived cells.
- Use fill colors, borders, spacing, and merged cells sparingly and intentionally.
- Set row heights and column widths so content is readable without excessive whitespace.
- Do not apply borders around every filled cell.
- Group related calculations and make totals simple sums of the cells above them.
- Add whitespace to separate sections.
- Ensure text does not spill into adjacent cells.
- Avoid unsupported spreadsheet data-table features such as `=TABLE`.

## Color conventions (if no style guidance)
- Blue: user input
- Black: formulas and derived values
- Green: linked or imported values
- Gray: static constants
- Orange: review or caution
- Light red: error or flag
- Purple: control or logic
- Teal: visualization anchors and KPI highlights

## Finance-specific requirements
- Format zeros as `-`.
- Negative numbers should be red and in parentheses.
- Format multiples as `5.2x`.
- Always specify units in headers (for example, `Revenue ($mm)`).
- Cite sources for all raw inputs in cell comments.
- For new financial models with no user-specified style, use blue text for hardcoded inputs, black for formulas, green for internal workbook links, red for external links, and yellow fill for key assumptions that need attention.

## Investment banking layouts
If the spreadsheet is an IB-style model (LBO, DCF, 3-statement, valuation):
- Totals should sum the range directly above.
- Hide gridlines and use horizontal borders above totals across relevant columns.
- Section headers should be merged cells with dark fill and white text.
- Column labels for numeric data should be right-aligned; row labels should be left-aligned.
- Indent submetrics under their parent line items.

© fcakyon · MIT · fcakyon/claude-codex-settings

Similar skills

All skills for Office documents →

From the same set113

The whole set →
tavily-usage tavily-usage guides coding agents to run web searches and extract page content via Tavily MCP tools. Requires a Tavily API key. CX Codex +1 900installs setup The setup Claude Code skill helps configure Azure MCP and troubleshoot authentication errors. It activates for Azure CLI, sign-in, or MCP connection problems. CX Codex +1 107installs paper-search-usage paper-search-usage guides coding agents to query academic databases, fetch citation graphs, and download research papers via Paper Search CLI. CX Codex +1 1installs setup setup guides the agent through installing and debugging Paper Search CLI. Replaces Docker MCP with direct CLI calls for paper search and DOI lookup. CX Codex +1 ★ 1,216repo stars review-pr The review-pr skill checks pull requests for bugs, regressions, risky changes, and missing tests. Use it to get a focused list of issues before approving a PR. CX Codex +1 ★ 1,216repo stars animation-gpu-properties animation-gpu-properties — a rule that keeps animations off width, height, top, left, margin and padding and moves them onto transform and opacity, so no layout pass runs per frame. CX Codex +1 ★ 1,216repo stars rerender-no-inline-components The rerender-no-inline-components rule flags React components declared inside other components, a pattern that causes remounts on parent renders. Use it when state, focus, or scroll position keeps resetting. CX Codex +1 ★ 1,216repo stars state-ground-truth state-ground-truth — a rule that stops agents from storing derived visual values in state. Keeps React and Reanimated logic centered on facts. CX Codex +1 ★ 1,216repo stars

Project sponsors

Companies that keep this analytics open