Excel Spreadsheet Workflows
Tech Stack Target / Version: Excel desktop or openpyxl-based spreadsheet automation with current OOXML-compatible workflows.
Use this skill when the deliverable is an .xlsx workbook or when spreadsheet structure matters.
- Leverage native parallel subagent dispatch and 200k+ context windows where available.
Current MCP Reality
Excel MCP tooling is host-dependent. In GitHub Copilot, Excel actions may appear as grouped Office tools. In Codex or Claude, those tools may be absent entirely. Treat the included Python script as the reliable fallback.
Activation Conditions
Use symptom -> action triggers: when one matches, apply this skill and verify with the protocol below.
- Creating or updating workbooks
- Converting CSV data into structured Excel output
- Applying formulas, formatting, charts, or pivots
- Producing spreadsheet deliverables when layout matters
Practical Workflow
- Confirm whether the client exposes spreadsheet MCP tools.
- If yes, inspect the actual tool names before assuming a wrapper exists.
- If no, use the local converter or author the workbook with
openpyxl.
- Validate formulas and chart ranges before claiming the workbook is ready.
MCP Fallback – Native Automation
When MCP is unavailable, use native automation: openpyxl for .xlsx, CSV export for flat data, and manual formula inspection for high-risk calculations. Preserve formulas, number formats, sheet names, hidden sheets, and workbook metadata, then reopen or parse the workbook before claiming success.
Cross-Client Portability
This skill is written to stay usable across GitHub Copilot, Claude Code, and Codex.
- GitHub Copilot: keep the folder in a Copilot-visible skill path or wrap the
workflow in project instructions when folder discovery is unavailable.
- Claude Code: keep the folder in a local skills directory or a compatible plugin source.
- Codex: install or sync the folder into
$CODEX_HOME/skills/excel-sheet and restart Codex after major changes.
MCP Availability And Fallback
Preferred MCP Server: Excel MCP
- Fallback prompt: "Use the Excel Spreadsheet Workflows skill without MCP. Follow the documented local or manual fallback, show the selected tool surface, and report the verification evidence."
- Use
scripts/csv-to-xlsx.py, openpyxl, or desktop Excel when the spreadsheet MCP surface is missing.
- Re-open the generated workbook locally to verify formulas, ranges, and frozen panes.
- Do not claim an MCP operation was used when the active host does not expose it.
Anti-Patterns
- Treating source content as already clean: Formatting automation will happily preserve broken or inconsistent input.
- Skipping an open-file verification pass: Documents and spreadsheets often fail in the destination app, not in the script output.
- Automating irreversible edits without checkpoints: A small mapping mistake can affect an entire workbook or document.
Verification Protocol
Before claiming "skill applied successfully":
- Pass/fail: The Excel Sheet artifact type, target format, and required output fidelity are stated before editing.
- Pass/fail: MCP availability is checked and the native automation fallback path is named when MCP is absent.
- Pass/fail: The produced file or formula is opened, parsed, rendered, or otherwise validated locally.
- Pressure-test scenario: Apply the workflow to a file with formatting, metadata, or conversion edge cases and verify nothing important is lost.
- Success metric: Zero unverified document claims; the artifact itself is the evidence.
Workbook Checklist
References & Resources
Documentation
Scripts
Examples
Related Skills
- documentation-authoring: Use it when the workflow also needs drafting structured technical or product documents.
- notion-docs: Use it when the workflow also needs Notion page and database publishing workflows.
- pdf: Use it when the workflow also needs PDF extraction, generation, and layout-aware review.
- word-document: Use it when the workflow also needs Word document authoring and formatting workflows.
1---2name: excel-sheet3description: Excel (.xlsx) manipulation via MCP server. Use for creating workbooks, formatting cells, writing formulas, building charts, pivot tables, data analysis, or any task involving Excel spreadsheets.4---5# Excel Spreadsheet Workflows
6
7> Tech Stack Target / Version: Excel desktop or `openpyxl`-based spreadsheet automation with current OOXML-compatible workflows.
8
9Use this skill when the deliverable is an `.xlsx` workbook or when spreadsheet structure matters.
10
11- Leverage native parallel subagent dispatch and 200k+ context windows where available.
12
13
14## Current MCP Reality
15
16Excel MCP tooling is host-dependent. In GitHub Copilot, Excel actions may appear as grouped Office tools. In Codex or Claude, those tools may be absent entirely. Treat the included Python script as the reliable fallback.
17
18## Activation Conditions
19
20Use symptom -> action triggers: when one matches, apply this skill and verify with the protocol below.
21
22- Creating or updating workbooks
23- Converting CSV data into structured Excel output
24- Applying formulas, formatting, charts, or pivots
25- Producing spreadsheet deliverables when layout matters
26
27## Practical Workflow
28
291. Confirm whether the client exposes spreadsheet MCP tools.
302. If yes, inspect the actual tool names before assuming a wrapper exists.
313. If no, use the local converter or author the workbook with `openpyxl`.
324. Validate formulas and chart ranges before claiming the workbook is ready.
33
34## MCP Fallback – Native Automation
35
36When MCP is unavailable, use native automation: `openpyxl` for `.xlsx`, CSV export for flat data, and manual formula inspection for high-risk calculations. Preserve formulas, number formats, sheet names, hidden sheets, and workbook metadata, then reopen or parse the workbook before claiming success.
37
38<!-- MCP:START -->
39
40<!-- PORTABILITY:START -->
41## Cross-Client Portability
42
43This skill is written to stay usable across GitHub Copilot, Claude Code, and Codex.
44
45- GitHub Copilot: keep the folder in a Copilot-visible skill path or wrap the
46 workflow in project instructions when folder discovery is unavailable.
47- Claude Code: keep the folder in a local skills directory or a compatible plugin source.
48- Codex: install or sync the folder into
49 `$CODEX_HOME/skills/excel-sheet` and restart Codex after major changes.
50
51<!-- PORTABILITY:END -->
52
53## MCP Availability And Fallback
54
55Preferred MCP Server: Excel MCP
56
57- Fallback prompt: "Use the Excel Spreadsheet Workflows skill without MCP. Follow the documented local or manual fallback, show the selected tool surface, and report the verification evidence."
58- Use `scripts/csv-to-xlsx.py`, `openpyxl`, or desktop Excel when the spreadsheet MCP surface is missing.
59- Re-open the generated workbook locally to verify formulas, ranges, and frozen panes.
60- Do not claim an MCP operation was used when the active host does not expose it.
61
62<!-- MCP:END -->
63
64## Anti-Patterns
65
66- Treating source content as already clean: Formatting automation will happily preserve broken or inconsistent input.
67- Skipping an open-file verification pass: Documents and spreadsheets often fail in the destination app, not in the script output.
68- Automating irreversible edits without checkpoints: A small mapping mistake can affect an entire workbook or document.
69
70## Verification Protocol
71
72Before claiming "skill applied successfully":
73
741. Pass/fail: The Excel Sheet artifact type, target format, and required output fidelity are stated before editing.
752. Pass/fail: MCP availability is checked and the native automation fallback path is named when MCP is absent.
763. Pass/fail: The produced file or formula is opened, parsed, rendered, or otherwise validated locally.
774. Pressure-test scenario: Apply the workflow to a file with formatting, metadata, or conversion edge cases and verify nothing important is lost.
785. Success metric: Zero unverified document claims; the artifact itself is the evidence.
79
80## Workbook Checklist
81
82- [ ] Sheets are named clearly
83- [ ] Headers are formatted consistently
84- [ ] Formulas are used instead of hardcoded derived values
85- [ ] Charts reference the correct ranges
86- [ ] Frozen panes or filters are applied where useful
87
88## References & Resources
89
90### Documentation
91- [Excel Formulas Reference](./references/excel-formulas-reference.md) - Formula patterns, lookup guidance, and Power Query notes
92
93### Scripts
94- [CSV to XLSX Converter](./scripts/csv-to-xlsx.py) - Local fallback for generating formatted Excel workbooks from CSV input
95
96### Examples
97- [Excel Workbook Examples](./examples/excel-workbook-examples.md) - Example workbook structures and automation patterns
98
99## Related Skills
100
101- [documentation-authoring](../documentation-authoring/SKILL.md): Use it when the workflow also needs drafting structured technical or product documents.
102- [notion-docs](../notion-docs/SKILL.md): Use it when the workflow also needs Notion page and database publishing workflows.
103- [pdf](../pdf/SKILL.md): Use it when the workflow also needs PDF extraction, generation, and layout-aware review.
104- [word-document](../word-document/SKILL.md): Use it when the workflow also needs Word document authoring and formatting workflows.
practicalswan