working-with-documents

Stars11

Forks3

UpdatedJuly 4, 2026 at 08:43

Use when reading, extracting from, or generating real-world document files — PDFs, spreadsheets (CSV/Excel/Sheets), and slide decks — with available tools; preserve the source and verify the output.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Source

imzodev

imzodev/openaidy

View GitHub Repository View Creator Repositories

Download

Related occupationsSOC

Based on SOC occupation classification

Office Clerks, GeneralOffice and Administrative Support Occupations·SOC 43-9061

File Explorer

2 files

SKILL.md

readonly

name	Working with Documents
description	Use when reading, extracting from, or generating real-world document files — PDFs, spreadsheets (CSV/Excel/Sheets), and slide decks — with available tools; preserve the source and verify the output.
version	1.0.0

Working with Documents

Documents are where real data lives: an invoice PDF, a budget spreadsheet, a deck to update. The job is extracting exactly what's there and producing files that open cleanly — with no silent data loss.

Reading and extracting

Confirm you have a tool that can actually parse the format — PDF text, spreadsheet cells, slide contents. A scanned PDF needs OCR, not a text parser; say so if that's the case.
Pull structure, not just text: tables as rows and columns, not a flattened blob. Preserve headers and units.
Quote figures exactly as they appear, and note the page, sheet, or cell so the user can check.
Never fill gaps with invented numbers. If a value is unreadable, mark it unreadable.

Generating and editing

Work on a copy. Don't overwrite the user's original unless they ask.
Match the format's conventions: real formulas in spreadsheets rather than pre-computed constants, consistent number and date formatting, sensible column widths.
For an edit, change only what was requested and keep the rest intact — other sheets, other pages, existing styles.
After writing, verify: reopen or re-parse the output and confirm the key values and structure survived.

Handling tabular data

Keep types honest — a number stays a number, a date stays a date. Don't turn IDs into rounded decimals.
Watch encoding and delimiters on CSV: commas inside values, quoting, and UTF-8.

See references/formats-and-tools.md.

Anti-patterns

Overwriting the source file in place with no backup.
Reporting numbers you couldn't actually read from the document.
Flattening a table into prose and losing the columns.
Writing constants where the spreadsheet should hold formulas.

More from this repository

same repository

addon-ui-components-cookbook

imzodev/openaidy

Use when writing or reviewing OpenAidy addon UI code (app/index.html, app/index.js) that calls sdk.ui.* — covers component mounting semantics and composed usage patterns beyond the one-line reference in addon_create's tool description.

2026-07-2011

data-and-apis

imzodev/openaidy

Use when calling external REST APIs or querying databases on the user's behalf through available tools or MCP servers — read-only by default, parametrized queries, and confirmation before any write.

2026-07-0411

scheduling

imzodev/openaidy

Use when working with calendars — checking availability, finding meeting times, and creating or updating events through an available calendar integration — with careful timezone handling and confirmation before inviting others.

2026-07-0411

sending-messages

imzodev/openaidy

Use when posting to chat or email on the user's behalf — Slack, Discord, Telegram, or mail — through an available integration. Get the recipient and content right, and confirm before anything goes out.

2026-07-0411

browser-automation

imzodev/openaidy

Use when a task needs a real browser — navigating sites, filling and submitting forms, clicking through flows, extracting page data, or taking screenshots — driving whatever browser tool or MCP server is available.

2026-07-0411

web-research

imzodev/openaidy

Use when you need current or external facts — searching the web, reading multiple sources, cross-checking claims, and synthesizing an answer with citations instead of guessing from memory.

2026-07-0411

name	Working with Documents
description	Use when reading, extracting from, or generating real-world document files — PDFs, spreadsheets (CSV/Excel/Sheets), and slide decks — with available tools; preserve the source and verify the output.
version	1.0.0

Working with Documents

Reading and extracting

Confirm you have a tool that can actually parse the format — PDF text, spreadsheet cells, slide contents. A scanned PDF needs OCR, not a text parser; say so if that's the case.
Pull structure, not just text: tables as rows and columns, not a flattened blob. Preserve headers and units.
Quote figures exactly as they appear, and note the page, sheet, or cell so the user can check.
Never fill gaps with invented numbers. If a value is unreadable, mark it unreadable.

Generating and editing

Work on a copy. Don't overwrite the user's original unless they ask.
Match the format's conventions: real formulas in spreadsheets rather than pre-computed constants, consistent number and date formatting, sensible column widths.
For an edit, change only what was requested and keep the rest intact — other sheets, other pages, existing styles.
After writing, verify: reopen or re-parse the output and confirm the key values and structure survived.

Handling tabular data

Keep types honest — a number stays a number, a date stays a date. Don't turn IDs into rounded decimals.
Watch encoding and delimiters on CSV: commas inside values, quoting, and UTF-8.

See references/formats-and-tools.md.

Anti-patterns

Overwriting the source file in place with no backup.
Reporting numbers you couldn't actually read from the document.
Flattening a table into prose and losing the columns.
Writing constants where the spreadsheet should hold formulas.