De-AI Office

Clean up the OOXML-internal artifacts that scripted editing tools (python-docx, python-pptx, openpyxl, LibreOffice) leave behind in Office files.

What this is and is not

This skill does not change document content. The words, images, layout, and structure the user authored stay intact. The skill touches only the XML-internal metadata that identifies which software last wrote the file, not who wrote the content.

Legitimate reasons to run this:

• You drafted a document in the user's voice, and used python-docx or openpyxl to append it to their existing file because no copy of Word was available on the machine.
• The user ran a mail-merge, accessibility-remediation, or batch-template script and wants the output to open cleanly in Word without "Document created by python-docx" showing up in metadata panes.
• The file is going into a workflow (e.g., a plagiarism-checker upload, an LMS submission) where script-generator strings trip false-positive automated flags.
• The file was edited on Linux via LibreOffice and needs to look like a Word export for a client who will inspect properties.

Authorship is the user's responsibility, not this skill's. This skill will not make AI-authored content look human-authored; for that, use the humanize skill, which works on the text itself. Metadata cleanup is file hygiene, not content provenance.

Tooling location