convert-excel-to-md
Converts Excel (.xlsx) workbooks into Markdown so their contents can be accurately analyzed, summarized, searched, or extracted from. Use this skill whenever the user shares, references, or asks about a .xlsx file — even if they don''t say "convert" or "markdown" explicitly.
Install / Use
npx skills add github/awesome-copilot --skill convert-excel-to-mdInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
Data & AnalyticsSupported Platforms
Our assessment of convert-excel-to-md
convert-excel-to-md scores 91/100 on our quality scale, 65th of 279 Data & Analytics skills we index (top 24%).
Its SKILL.md is 6.6 KB long, split into 6 sections with 5 code examples: a thorough specification that gives an agent plenty to work with.
With 39,348 GitHub stars, it is one of the more widely adopted skills in the catalogue.
Maintenance, license and trust
- The repository was last updated 3 days ago, so convert-excel-to-md is actively maintained.
- It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
- Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
convert-excel-to-md compared with similar skills
All 4 of these similar skills score higher than convert-excel-to-md; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| convert-excel-to-md (this skill)by github | 91 | 39.3k | 3d ago | SKILL.md |
| algorithmic-artby anthropics | 100 | 177.9k | 5d ago | SKILL.md |
| pptxby anthropics | 100 | 177.9k | 5d ago | SKILL.md |
| designby nextlevelbuilder | 100 | 130.2k | 6d ago | SKILL.md |
| ui-ux-pro-maxby nextlevelbuilder | 100 | 130.2k | 6d ago | SKILL.md |
Frequently asked questions
- How do I install convert-excel-to-md?
- Run
npx skills add github/awesome-copilot --skill convert-excel-to-md. The install tabs above show the steps for each supported agent. - Which AI agents does convert-excel-to-md work with?
- It is written for Zed, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is convert-excel-to-md safe to use?
- It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is convert-excel-to-md still maintained?
- The repository was last updated 3 days ago, so convert-excel-to-md is actively maintained.
Skill content
View source on GitHubname: convert-excel-to-md description: 'Converts Excel (.xlsx) workbooks into Markdown so their contents can be accurately analyzed, summarized, searched, or extracted from. Use this skill whenever the user shares, references, or asks about a .xlsx file — even if they don''t say "convert" or "markdown" explicitly. This includes requests to "read", "summarize", "review", "extract data from", "compare", "chart", or "analyze" a spreadsheet, workbook, budget, data export, or tracker. Always run the bundled conversion script to produce Markdown first; do not attempt to parse .xlsx content directly or write ad-hoc extraction code. Also use this skill for batch requests involving a whole folder of Excel workbooks. IMPORTANT: When the user references a folder or set of documents containing multiple file types (.pdf, .docx, .xlsx), invoke ALL three sibling skills — convert-pdf-to-md, convert-word-to-md, and convert-excel-to-md — so no file type is silently skipped.'
Convert Excel to Markdown
When to use this skill
Trigger this skill any time there is a .xlsx file that needs to be
understood or processed — for example, a user attaches a spreadsheet and
asks questions about it, wants a summary of the data, wants specific rows or
values pulled out, or wants multiple workbooks in a folder processed
together. Excel's native .xlsx format is a zipped XML bundle that is not
reliably readable as plain text, so always convert it to Markdown first
using the script in this skill rather than trying to open or parse the file
directly.
This skill only supports .xlsx. If asked to convert a legacy .xls file,
tell the user it isn't supported and ask them to re-save it as .xlsx
(Excel: File > Save As > Excel Workbook (.xlsx)) first.
Mixed file types: When the user references a folder or set of documents
containing multiple supported file types (.pdf, .docx, .xlsx), this
skill handles only .xlsx files. The agent MUST also invoke the sibling
skills in parallel:
convert-pdf-to-mdfor any.pdffilesconvert-word-to-mdfor any.docxfiles
Never process a folder and silently skip a supported file type. All three skills must be invoked together when mixed types are present.
Setup (once per environment)
Before the first conversion in a given environment, follow
references/setup.md step by step to ensure Python,
pip, and the markitdown package are installed. Do this proactively rather
than guessing whether the environment is ready — the script itself will
also fail with a clear pointer back to that file if markitdown turns out
to be missing, so it's safe to just try the conversion first if you're
reasonably confident setup was already done.
Usage
The conversion script lives at scripts/convert_excel_to_md.py.
Output structure: MarkItDown's XLSX converter renders each sheet as its
own ## <SheetName> Markdown table — it has no support for embedded images
at all. This script separately extracts real embedded images (raster
pictures, not charts) and maps them to the sheet they belong to, writing a
self-contained folder per document:
<name>/
img/
sheet001_<sheetname>_img001.<ext>
sheet002_<sheetname>_img001.<ext>
...
<name>.md (each sheet's images appear right after its table,
under a "#### Images in this sheet" heading)
This is per-sheet placement, not exact cell position — the finest
granularity MarkItDown's stable output anchors (the ## <SheetName>
headings) allow. If a workbook has no embedded images, no img/ folder or
image sections are created. Native Excel charts are not extracted as
images (only actual embedded pictures are — charts would need to be
rendered by Excel/LibreOffice, which this lightweight skill does not do).
Single file:
python scripts\convert_excel_to_md.py "C:\path\to\workbook.xlsx"
This creates a workbook\ folder next to the source file (containing
workbook.md and, if present, workbook\img\). To control the destination
folder explicitly:
python scripts\convert_excel_to_md.py "C:\path\to\workbook.xlsx" -o "C:\path\to\output_folder"
A folder of workbooks (batch mode):
python scripts\convert_excel_to_md.py "C:\path\to\folder"
Add --recursive to also include subfolders:
python scripts\convert_excel_to_md.py "C:\path\to\folder" --recursive
Each .xlsx found gets its own <name>\ output folder next to it by
default. Pass -o "C:\path\to\output_parent" to collect all the generated
<name>\ folders under a separate parent directory instead (subfolder
structure is preserved when combined with --recursive).
After conversion, read the resulting .md file(s) to perform the actual
analysis the user asked for — the script's job is only to produce accurate
Markdown (and images), not to interpret the content.
Deciding where output goes
Default — always output next to the source file. The <name>/ folder
is created in the same directory as the source .xlsx. This is the required
default for every case. Do NOT override it unless the user explicitly asks
for a different location.
Only use -o when the user explicitly provides an output path (e.g.,
"save the output to C:\output", "put the results in D:\work"). Do NOT
pass -o based on the agent's current working directory, the session state
folder, or any implied location.
If the source file path cannot be fully resolved — for example, the
user provides only a filename with no directory, or the path is ambiguous —
use ask_user to confirm the full absolute path before running the
conversion. Never guess or assume the directory.
Troubleshooting
| Symptom | Likely cause | Fix |
|---|---|---|
| ModuleNotFoundError: No module named 'markitdown' / exit code 2 | MarkItDown not installed | Follow references/setup.md |
| ERROR: Unsupported file type '.xls' / exit code 3 | Legacy .xls, not .xlsx | Ask the user to re-save as .xlsx |
| ERROR: Input path not found / exit code 3 | Wrong path, or file moved | Confirm the correct path with the user |
| FAILED <file> -> ... in batch output | That specific file is corrupt, password-protected, or otherwise unreadable | Report which file(s) failed; other files in the batch still succeed |
| NOTE: skipped N non-.xlsx file(s) | Folder contains non-Excel files | Expected — those files are intentionally ignored |
| A sheet's charts don't appear as images | Charts are chart objects, not embedded pictures — this skill only extracts real embedded raster images | Expected; mention this limitation if the user specifically needs chart images |
Related Skills
algorithmic-art
177.9kCreating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems.
pptx
177.9kUse this skill any time a .pptx or .potx file is involved in any way — as input, output, or both. This includes: creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text from any .pptx or .potx file (even if the extracted content will be used elsewhere, like in an em…
design
130.2kComprehensive design skill: brand identity, design tokens, UI styling, logo generation (55 styles, Gemini, Atlas Cloud, or MuAPI AI), corporate identity program (50 deliverables, CIP mockups), HTML presentations (Chart.js), banner design (22 styles, social/ads/web/print), icon design (15 styles, SVG…
ui-ux-pro-max
130.2kUI/UX design intelligence for web, mobile, and desktop. This skill should be used when designing, building, reviewing, or fixing interfaces, including pages, components, design systems, accessibility, interaction, responsive layout, typography, color, charts, and stack-specific UI implementation.
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
