# Office Export QA

> Final export, compatibility, render, metadata, accessibility, and quality-assurance workflow for Office files including DOCX, XLSX, PPTX, PDF, Word, Excel, PowerPoint, and Google Workspace-targeted artifacts. Use when users ask to check, verify, package, export, clean, inspect, anonymize, or prepare Office deliverables for sharing, submission, printing, presentation, or GitHub examples.

- Skill: `xiangdong-415/office-export-qa` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add xiangdong-415/office-export-qa`
- Raw SKILL.md: https://api.skillmd.com/api/skills/xiangdong-415/office-export-qa/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Web & Frontend
- Author: Xiangdong-415 (https://skillmd.com/u/xiangdong-415)
- Updated: 2026-09-22
- Page: https://skillmd.com/skills/xiangdong-415/office-export-qa

---


# Office Export QA

## Purpose

Use this skill before handing off Office files. It helps Codex verify that Word, Excel, and PowerPoint artifacts are clean, compatible, and ready to share.

## Workflow

1. Identify deliverables.
   - `.docx`, `.xlsx`, `.pptx`, PDF, images, Google Docs, Google Sheets, or Google Slides.
   - Determine whether editability or visual fidelity matters more.

2. Run structural checks.
   - DOCX: headings, lists, tables, comments, tracked changes, fields, metadata.
   - XLSX: formulas, named ranges, charts, hidden sheets, calculation errors, external links.
   - PPTX: slide count, media files, charts, fonts, speaker notes, template consistency.

3. Run visual checks when possible.
   - Render pages, sheets, or slides to preview images or PDF.
   - Inspect all final outputs, not only the first page or first slide.

4. Check privacy and sharing safety.
   - Remove personal metadata when requested.
   - Check comments, hidden sheets, speaker notes, tracked changes, and embedded files.
   - Confirm no private paths, tokens, or internal scratch notes are visible.

5. Package final files.
   - Keep final deliverables separate from scratch files.
   - Use descriptive filenames.
   - Provide absolute links or paths to final artifacts.

## Quality Checklist

- File opens in the intended Office app or compatible viewer.
- No visible clipping, overlap, unreadable labels, or missing assets.
- Formulas/charts/fields point to valid data.
- Metadata and hidden content are handled according to the user's intent.
- Final output format matches the user's request.
- Any unverified item is disclosed clearly.