This skill deepens the option-comparison-table in the existing operation manual into a standalone entry point, adding real ID binding, width checks, and PPTX read-back; it does not count as a new standalone scenario.
- From the input, confirm the proposal names, comparison dimensions, units, period, and source date. Write "to be verified" for unknown values; do not fill in zeros or invent scores. Align with the criteria already given by the user first, then decide whether a recommendation conclusion is needed.
- Read methods, IDs, and parameters and step-by-step template. Example numbers are only for structural verification; replace them cell by cell with actual facts during production.
- For an existing document, check the target page first; preserve other pages. Only for a new task, execute
file.new. Carry content in a native table; do not pass off screenshots or multiple text boxes as an editable table. - After creation, query the real table ID; write content cell by cell, then configure the header, row bands, and column widths. All widths are in pt; changing one column may change the total width, so you must check the sum of column widths and the right boundary.
- Add speaker notes to this page explaining the data sources and assumptions; the body expresses the comparison results, and the notes supplement the methodology. When there is no common standard, keep the comparison objective and do not automatically declare a winner.
- Save as
.deckcraftand.pptx, reopen to check the table, notes, and text. Then modify one cell in the copy and export it to confirm it is still a native editable table. Check the actual full-page rendering for overflow, alignment, and font size.
When an embedded editor is needed, hand off to the deckcraft-editor skill. Standalone installation:npx skills add full-aigc-skills/deckcraft-skills --skill deckcraft-editor. This skill is provided as a pre-release with DeckCraft development; real materials and other hosts still need separate acceptance.
The example is limited to 4 rows and 3 columns. If content is too long, simplify it first or split it across pages by dimension, repeating the header on continuation pages; the current process has not verified automatic pagination, screen-reader header semantics, external PowerPoint layout, or host screen synchronization, and file generation does not substitute for these checks.