/pdf-package

Package an exported PDF as a SUBMISSION PACKAGE — explainer videos attached INSIDE the file (pikepdf EmbeddedFiles) plus a click-to-stream poster page. The PDF itself comes from the portal's built-in Export → PDF; this skill covers the packaging on top. Use when a proposal/brochure/report must ship as one self-contained file (client submissions, RFP responses, board packs).

• Instructions: You are packaging an already-exported PDF as a **submission package**: one file that carries its explainer videos *inside* it. This is the validated pipeline behind `PartnerRe/content/ESL-Submission-Package.pdf` (proposal + 2 process videos, 4.7 MB, byte-exact verified). 🚨 **This skill does NOT produce the PDF.** The portal has a built-in document export — use it (phase 1), then come back here to package the result. Hand-rolling a print pipeline duplicates a maintained feature and drifts from it. # 0. Know the playback truth-table (decide the shape FIRST) | Technique | Plays where | Verdict | |---|---|---| | Inline RichMedia video annotation | Adobe Acrobat/Reader ONLY; blank in Preview, browsers, mobile; mail gateways distrust it | ❌ never use | | **File attachments (EmbeddedFiles)** | Every Acrobat + most desktop viewers show the paperclip/attachments pane; user opens the mp4 from there | ✅ "ships as part of the PDF" | | **Poster frame hyperlinked to the streaming URL** | Every viewer, print included | ✅ always add — the universal path | The package therefore combines **both ✅ rows**: a "See it run" page (posters + links) AND the mp4s attached inside. If the deliverable has **no videos**, you do not need this skill at all — phase 1 is the whole job. # 1. Produce the PDF with the built-in export **Mesh-first**: author the document on the mesh — a top node consolidating sections via `@@Path/Sub/$Content` embeds (content-only, no headers/comments), e.g. `PartnerRe/EslProposal`. Fix content on the mesh, then export, so the page and the PDF never diverge. See **[/multipart-doc](/Publish/Skill/multipart-doc)** for the document shape. Then export it — two equivalent routes: - **UI**: the node menu's 📦 **Export** group → **📄 PDF**. The dialog offers title, corporate identity, cover page, table of contents, page-break rules, header/footer, and "include child nodes as chapters" (which is what pulls the `@@` sections in). - **Script**: run the built-in template w…
• Auto mount: yes
• Launches sub thread: no