Skip to content
cccskills
FreePublished on GitHub

convert-excel-to-md

Convert Excel workbooks into Markdown tables organized by sheet, preparing their contents for reading, summarizing, searching, or extracting data. The bundled script also extracts embedded pictures and processes folders of workbooks, including subfolders when requested.

OriginalShow the original 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.

Works withExcelWord
See how to install

Good for

  • Preparing an Excel budget for summarization
  • Converting workbooks before searching or extracting values
  • Batch converting Excel files across folders
  • Saving embedded pictures alongside each sheet's table

Files included (4)

  • SKILL.md6.6 KB
  • references/setup.md2.7 KB
  • scripts/convert_excel_to_md.py13.8 KB
  • scripts/requirements.txt24 B

SKILL.md (original)

Review the instructions the agent will receive before you install.

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-md for any .pdf files
  • convert-word-to-md for any .docx files

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

SymptomLikely causeFix
ModuleNotFoundError: No module named 'markitdown' / exit code 2MarkItDown not installedFollow references/setup.md
ERROR: Unsupported file type '.xls' / exit code 3Legacy .xls, not .xlsxAsk the user to re-save as .xlsx
ERROR: Input path not found / exit code 3Wrong path, or file movedConfirm the correct path with the user
FAILED <file> -> ... in batch outputThat specific file is corrupt, password-protected, or otherwise unreadableReport which file(s) failed; other files in the batch still succeed
NOTE: skipped N non-.xlsx file(s)Folder contains non-Excel filesExpected — those files are intentionally ignored
A sheet's charts don't appear as imagesCharts are chart objects, not embedded pictures — this skill only extracts real embedded raster imagesExpected; mention this limitation if the user specifically needs chart images

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Map an existing codebase into seven documents covering its technology, structure, architecture, conventions, integrations, tests, and concerns. Link findings to file evidence, mark unknowns, and highlight differences between stated plans and the actual implementation.

  • Get oriented in an unfamiliar codebase
  • Prepare documentation for a project handover
  • Compare documented architecture with implementation
github/awesome-copilot40.2KUpdated Oct 17, 2026

Assess a repository’s readiness for AI agents with AgentRC and generate a standalone HTML dashboard. Review scores across nine areas, see prioritized improvements, and optionally apply scoring policies tailored to an organization.

  • Assessing a repository’s readiness for AI agents
  • Prioritizing improvements from assessment results
  • Reviewing scores under an organization’s own policy
github/awesome-copilot40.2KUpdated Oct 17, 2026

Generate coding agent instruction files from a project's actual code using AgentRC. Capture detected languages, frameworks, and conventions in one shared file or split rules by topic and project area, with a preview before writing.

  • Create project instructions for VS Code Copilot
  • Refresh agent rules after project changes
  • Split monorepo instructions by project area
github/awesome-copilot40.2KUpdated Oct 17, 2026

Customize AgentRC readiness assessments to match team or organization standards. Choose or create policies that adjust check importance, disable irrelevant checks, set pass thresholds, and define requirements for automated checks in CI workflows.

  • Set shared readiness standards across an organization
  • Focus assessments on AI tooling
  • Adjust the importance of individual checks
github/awesome-copilot40.2KUpdated Oct 17, 2026

Analyze supplied ad performance data to identify wasted spend, strong campaigns, and next tests. Compare channels, assess whether test differences are meaningful, and produce budget reallocation recommendations with a prioritized action plan.

  • Identify ads and keywords to pause
  • Find campaigns and audiences worth scaling
  • Assess whether A/B test results are meaningful
github/awesome-copilot40.2KUpdated Oct 17, 2026

Turn code files into learning resources by adding comments that explain syntax, programming concepts, and design choices. Adjust explanation depth and repetition to the reader’s knowledge while preserving file structure, encoding, and syntax.

  • Add beginner-friendly explanations to existing code
  • Document the reasoning behind syntax and design choices
  • Adjust comment depth for readers with different experience
github/awesome-copilot40.2KUpdated Oct 17, 2026

See all skills by github

Report a problem with this skill