Choose the Right Skill for PDF, Slides, and Sheets
Choose PDF, PowerPoint, Word, or spreadsheet skills by the required deliverable, then plan dependencies and checks for useful, editable output.
Source reviewed · SkillDex editorial
Choose a document skill by the file you need at the end and the constraints that must survive the work. “Make a report” might mean an editable Word document, a fixed-layout PDF, a slide deck for a meeting, or a workbook that recalculates when inputs change. Those are different deliverables even when they begin with the same source material.
This guide connects the PDF, PPTX, XLSX, and DOCX entries to practical selection and review steps. It is based on their upstream instructions, not on an independent cross-platform runtime test. The sample briefs below are examples you can adapt; they are not completed customer projects or benchmark results.
Start with the deliverable contract
Before installing a skill, write down the required file type, audience, input files, editable areas, and acceptance checks. Include the intended application if formatting or feature compatibility matters. A workbook that must open in Excel and a workbook intended for another spreadsheet application may need different verification.
State what should remain unchanged. For an existing presentation, that might be theme colors, slide masters, and speaker notes. For a workbook, it might be formulas outside a named input range. For a contract draft, it might be tracked changes and heading structure.
Specify a new output filename so the evaluation preserves the original. Keep the source files alongside a short task note. This makes it easier to compare the result and repeat the task when a dependency or skill changes.
Use the PDF skill for PDF operations
The upstream PDF instructions cover reading and extracting content, page operations, creation, forms, and OCR-related workflows. They describe different tools for different operations, including pypdf, pdfplumber, ReportLab, and command-line utilities.
Your first decision is whether the PDF contains selectable text or scanned page images. A page can look like text to a person while containing no text layer for an extraction library. For scanned material, plan an OCR step and review the recognized text against the image.
An example brief is: “Extract the line-item table from this three-page sample PDF into CSV. Preserve the row order and currency values. Flag ambiguous cells instead of guessing.” That brief makes correctness observable. You can compare row counts, headers, and selected values against the source.
For page merging or splitting, check page count and order. For newly created PDFs, inspect rendered pages for clipping, missing glyphs, margins, and pagination. Extracted text alone cannot prove that the visual layout is correct. Conversely, a visually correct preview cannot prove that all requested text is searchable or selectable.
Use the PPTX skill when slides must remain editable
The PPTX instructions distinguish creating a new deck, editing an existing package, and reading slide content. They reference presentation-specific scripts and rendering or validation tools. The exact prerequisites depend on the selected path, so inspect the current dependency section before starting.
A useful example brief is: “Update slides four through six in this template with the supplied results. Keep the existing layouts and theme. Preserve speaker notes, and return a new PPTX plus a preview of the changed slides.” This is clearer than asking the agent to “improve” a deck without defining whether redesign is allowed.
Review the slide sequence, titles, charts, footnotes, and any remaining template placeholders. Inspect every changed slide at a readable size. When a chart changes, compare its displayed values to the underlying source instead of accepting the visual alone.
A rendered slide is a preview, not the editable file. Open the final presentation in the intended application when practical and check for repair prompts or missing assets. If the skill uses an alternative renderer, note that its output may not exactly match PowerPoint’s font substitution and layout behavior.
Use the XLSX skill for calculations and structured workbooks
The upstream XLSX instructions emphasize formulas, workbook structure, recalculation, and error checks. They identify Python tools for reading or editing tabular data and a recalculation workflow. Installing the instructions alone does not establish that those dependencies exist on your machine.
An example brief is: “Add a monthly summary to a copy of this workbook. Read transactions from the existing table, use formulas for totals, and leave all original worksheets unchanged. Confirm the totals for three selected months against the input rows.”
Separate formula storage from calculated values. A file can contain a formula without a refreshed cached result. Recalculation is necessary for many downstream previews and readers, but it is not proof that the formula references the correct cells.
Check units, date handling, percentage formats, blank cells, and representative edge cases. Inspect formula ranges around the first and last rows because boundary errors can produce plausible totals. If the workbook contains macros, shapes, external references, or features the editing library cannot preserve, choose the workflow deliberately and record any limitations.
Use DOCX for structured prose that users will edit
The DOCX instructions address Word documents and templates, with separate approaches to creating, editing, and reading files. They describe package-level considerations and document-specific tooling. Use this route when editable prose, styles, tables, comments, or tracked changes are part of the deliverable.
An example brief is: “Revise the supplied policy document using the marked changes. Preserve heading levels and numbering, retain comments, and return a new DOCX with a PDF preview for visual review.” Identify whether revisions should be accepted, tracked, or merely proposed before work begins.
Check heading hierarchy, table widths, page breaks, headers, footers, and numbering. Render the document to inspect pagination, but also review the editable file: text can look correct in a PDF while losing its useful style structure in Word.
If the user only needs a final PDF, a Word intermediate may still be appropriate for editing, but do not add one automatically. Choose the simplest workflow that preserves the required structure and output.
Combine skills at explicit handoff points
Some tasks legitimately need more than one skill. For example, extract a table from a PDF, check the extracted data, create a workbook, and then summarize the verified results in slides. Treat each transition as a checkpoint rather than asking one long instruction to hide all intermediate decisions.
At the first handoff, confirm that the extracted rows match the source. At the second, verify formulas and units. Before the slide stage, decide which calculated values are approved for presentation. Keep the source of each figure traceable so a later correction can be made consistently.
Do not assume that two skills use identical file conventions or tool versions. Specify the intermediate format, filenames, and whether the next stage may modify the previous output. This reduces accidental overwrites and makes failures easier to locate.
Review the result at three levels
First, check completion: the requested files exist, open, and have the expected pages, slides, sheets, or sections. Second, check meaning: facts, formulas, labels, and source references match the task. Third, check presentation: layout, typography, contrast, pagination, and readability are suitable for the audience.
Record which checks were actually performed and which remain outstanding. If no rendering tool is available, say that visual review is pending rather than implying it passed. If only a sample of formulas was compared, state the sample and the scope.
For a first evaluation, a small completed task with a clear review record is more informative than a large generated deliverable nobody has inspected. Use the result to decide whether to keep the skill, add a missing dependency, narrow the task, or choose another workflow.