Skip to content
Back to skills

Local Mcp Pdf To Sheet

ASecurity

Use when the user wants to pull data out of one or more PDFs (invoices, bank/credit-card statements, receipts, reports, tables) and put it into a spreadsheet. pdf_read is one of the most-used tools; this codifies the read-PDF → structure → write-Excel workflow. Powered by LMCP on macOS and Windows.

  • 66 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added October 9, 2026
ai-agentsgo

Works with

  • mcp

Security analysis

A100/100

Scanned October 9, 2026

npx -y skills add colibird-ai/local-mcp-releases --skill local-mcp-pdf-to-sheet --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Local Mcp Pdf To Sheet?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Local Mcp Pdf To Sheet
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/colibird-ai-local-mcp-pdf-to-sheet/badge)](https://www.skillsdirectory.com/skills/colibird-ai-local-mcp-pdf-to-sheet)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: local-mcp-pdf-to-sheet
description: Use when the user wants to pull data out of one or more PDFs (invoices, bank/credit-card statements, receipts, reports, tables) and put it into a spreadsheet. pdf_read is one of the most-used tools; this codifies the read-PDF → structure → write-Excel workflow. Powered by LMCP on macOS and Windows.
---

# PDF → spreadsheet

Reading PDFs and turning them into structured data is one of the highest-volume things LMCP
users do. This skill codifies the end-to-end flow: read the PDF(s) on the user's computer (macOS or
Windows), extract the rows, and build an Excel sheet. The tools execute on the device; the extracted
text goes to the user's AI provider as part of the conversation.

## The flow
1. **Read the PDF(s)** — `pdf_read(path=...)`, one call per file. (Find the files first with
   `file_search`, or `finder_search` on macOS, if the user only describes them, e.g. "my March invoices".)
2. **Extract the structured rows** from the text — identify the columns the user wants (e.g. for
   statements: Date, Description, Amount; for invoices: Vendor, Invoice #, Date, Total). Normalize
   dates and numbers. If several PDFs, combine into one consistent table.
3. **Write the spreadsheet** — prefer one call:
   `excel_create(path="<out>.xlsx", headers=["Date","Description","Amount"], rows=[[...],[...]], confirm=true)`.
   `headers` is required; `rows` is the full data. For edits to an existing sheet use
   `excel_write_cell(path, cell="B2", value, confirm=true)`; to read one back use `excel_read(path)`.

## Good practice
- Confirm the **columns** with the user before building the sheet ("I'll pull Date, Description,
  Amount — want a Category column too?").
- Build the whole table in memory, then write it in a single `excel_create` (one row per record) —
  don't write cell-by-cell unless editing an existing file.
- Watch totals: if the PDF has a stated total, add a check row or verify your sum matches.
- Keep money as numbers (not "$1,234.50" strings) so the sheet can compute.
- Write the output next to the source or to a path the user names; `excel_create`/`excel_write_cell`
  are preview/confirm-gated (pass `confirm: true` once the user approves the columns).
- Multi-PDF: keep a `Source` column so each row traces back to its file.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.