codia-document-deck
Convert documents into editable design artifacts and presentation decks by coordinating Codia PDF-to-design, PDF-to-PPT, image-to-design, and optional image description workflows.
When To Use
Use this skill for:
- PDF to editable design data
- PDF to PPT or PowerPoint deck conversion
- Requests that need both editable JSON and PPTX output
- Screenshot, poster, or scanned-page conversion into editable design data
- Document review where the user wants output files, not just a summary
For a direct PDF-to-PPT task only, use codia-pdf-to-ppt. For a direct screenshot-to-design task only, use codia-image-to-design.
Inputs To Collect
- Source PDF, screenshot, poster, or image path/URL
- Page range for PDFs
- Whether the user wants editable design data, PPTX, or both
- Deck title, if a PPTX is requested
- Output directory
Workflow
- Use
codia-design setup/auth guidance if the CLI is missing or not authenticated.
- For PDFs, confirm page selection. Codia PDF APIs use zero-based page numbers: page
0 is the first page.
- Run
codia-pdf-to-design first when editable page structure, JSON output, or visual reconstruction is requested.
- Run
codia-pdf-to-ppt --poll when a PPTX deck is requested. Let the CLI download and validate the returned PPTX unless the user explicitly asks for JSON-only behavior.
- Use
codia-image-to-design for screenshots, poster images, exported pages, or scanned pages that are not available as PDF pages.
- Use
codia-image-describe only when the user also needs a plain-language visual summary, comparison, or extraction of design intent.
- Do not rasterize the PDF locally or generate a substitute PPTX unless the user explicitly asks for a local fallback.
Output
Return:
- Editable design JSON path or paths
- PPTX path when produced
- Downloaded local files
- Page range used
- Failed page, task ID, API error, or validation error when any step fails
If PPTX download or validation fails, report the API or validation error directly and treat the PPTX step as failed.
1---2name: codia-document-deck3description: Use when the user asks to convert PDFs, screenshots, reports, documents, or existing marketing files into editable design data, PPTX slides, or both.4---56# codia-document-deck78Convert documents into editable design artifacts and presentation decks by coordinating Codia PDF-to-design, PDF-to-PPT, image-to-design, and optional image description workflows.910## When To Use1112Use this skill for:1314- PDF to editable design data15- PDF to PPT or PowerPoint deck conversion16- Requests that need both editable JSON and PPTX output17- Screenshot, poster, or scanned-page conversion into editable design data18- Document review where the user wants output files, not just a summary1920For a direct PDF-to-PPT task only, use `codia-pdf-to-ppt`. For a direct screenshot-to-design task only, use `codia-image-to-design`.2122## Inputs To Collect2324- Source PDF, screenshot, poster, or image path/URL25- Page range for PDFs26- Whether the user wants editable design data, PPTX, or both27- Deck title, if a PPTX is requested28- Output directory2930## Workflow31321. Use `codia-design` setup/auth guidance if the CLI is missing or not authenticated.332. For PDFs, confirm page selection. Codia PDF APIs use zero-based page numbers: page `0` is the first page.343. Run `codia-pdf-to-design` first when editable page structure, JSON output, or visual reconstruction is requested.354. Run `codia-pdf-to-ppt --poll` when a PPTX deck is requested. Let the CLI download and validate the returned PPTX unless the user explicitly asks for JSON-only behavior.365. Use `codia-image-to-design` for screenshots, poster images, exported pages, or scanned pages that are not available as PDF pages.376. Use `codia-image-describe` only when the user also needs a plain-language visual summary, comparison, or extraction of design intent.387. Do not rasterize the PDF locally or generate a substitute PPTX unless the user explicitly asks for a local fallback.3940## Output4142Return:4344- Editable design JSON path or paths45- PPTX path when produced46- Downloaded local files47- Page range used48- Failed page, task ID, API error, or validation error when any step fails4950If PPTX download or validation fails, report the API or validation error directly and treat the PPTX step as failed.
codia-ai