office-document-review

Office Document Review

Use this skill when the user wants you to inspect a OneDrive/SharePoint-style folder tree, locate a subfolder by name/date, and proofread all documents in it for spelling and grammar.

This is a workflow skill, not a single-app skill: it covers local file-system browsing, document text extraction, and batch proofreading notes.

Triggers

• "go to the OneDrive folder"
• "look in folder X and then folder Y"
• "proofread all those documents"
• "check for spelling/grammar errors in the docs"
• "review the files in this folder"

Core workflow

1. Resolve the real path first

• Prefer a filesystem path over guessing from the user’s wording.
• Folder names in casual speech may not match the actual on-disk name exactly.
• If the exact folder cannot be found, list the visible folder names and state what is missing before asking for clarification.

1. Search the tree recursively

• Use the live file tree to locate the target folder and confirm the actual path.
• When the user gives a date-like folder name, search for variant spellings and punctuation (6-2-26, 6.2.26, 6_2_26, 6-2-2026) before assuming it does not exist.

1. Inventory the documents

• Identify all files in the target folder.
• Group by extension and prioritize editable office docs (.docx, .doc, .odt, .rtf, .txt) before PDFs or spreadsheets.

1. Extract readable text

• For Word/Office files, extract the text in a way that preserves headings and paragraphs as much as possible.
• If the file-reading tool rejects .docx as binary, do not classify the document as unreadable and do not repeat the same call across the batch. A DOCX is a ZIP package: validate it with Python zipfile, then use python-docx when available or extract word/document.xml and convert paragraph/table XML to bounded text. Record package validity, paragraph/table counts, and extraction method. Use native Word or PDF rendering separately when layout—not just text—is under review.
• When validating generated fixtures, compare extracted text against the fixture specification or authoritative .txt source before opening Word. A valid ZIP alone does not prove the fixture contains the intended content.
• For scanned or image-based files, use OCR or an extraction tool first.
• If a file is not meaningfully text-reviewable after at least one appropriate format-specific fallback, say so explicitly instead of pretending to proofread it.