Skip to main content

content-pdf-with-images

图文 PDF 工作流:将主题或文章拆成章节,为每章生成配图,并汇总排版为真实 PDF。Workflow skill for turning a topic or article request into a chaptered PDF with one image per chapter; use for illustrated PDF reports, chapter images, and final PDFs assembled from text plus generated images.

跳到安装

来源信息

仓库
ai-workspace-lab/xworkspace-core-skills
最近来源活动
2026年7月1日 07:19
检测到的 SKILL.md 语言
英语
星标
7
分支
0

安装方式

默认使用会先检查来源的 Prompt;你也可以切换为直接命令,或下载本地副本。

检查来源文件

决定是否安装前,请先阅读 SKILL.md,以及 SkillsMP 当前展示的配套文件。

正在显示 SKILL.md

SKILL.md
来源说明 · 只读预览
name
content-pdf-with-images
description
图文 PDF 工作流:将主题或文章拆成章节,为每章生成配图,并汇总排版为真实 PDF。Workflow skill for turning a topic or article request into a chaptered PDF with one image per chapter; use for illustrated PDF reports, chapter images, and final PDFs assembled from text plus generated images.
# Content PDF With Images Workflow This is an orchestration skill. It does not replace planning, image, or PDF skills. It forces a staged handoff so the final artifact is a real PDF with real image inputs, not a placeholder file. Before generating, extending, repairing, or repainting chapter images, read [../../marketplace/pdf/editable-reconstruction.md](../../marketplace/pdf/editable-reconstruction.md) only for its provider order. Generate the chapter image that best fits the intended composition; do not force a text-free background or separate PDF text layer for ordinary illustrations. Only when the user explicitly requests editable reconstruction of a scanned, flattened, or image-only PDF, apply the complete per-page contract from that reference: one text-free full-page PNG plus native selectable PDF text objects. Hard rule: image prompts are not images. A PDF that contains only chapter text and image prompts is incomplete and must not be reported as delivered. ## Output Contract Final deliverables must stay inside the current XWorkmate/OpenClaw task artifact scope: - `workflow.plan.md` - `article.md` - `assets/images/*.png` - `assets/images/manifest.md` - `prompts/image-prompts.md` - `series.config.json` - `exports/final.pdf` - `DELIVERY.md` If the user specifies a particular content sequence or evolutionary path, ensure the exact sequence is preserved. Do not hardcode a fixed number of chapters unless requested. ## Phase 1: Plan Create `workflow.plan.md` before writing final content. It must include: - topic and audience - chapter list - target word or character count - one image concept per chapter - downstream skill sequence - final acceptance checklist If the user gives an explicit chapter sequence, preserve it literally. ## Phase 2: Article Write `article.md` with: - title - one section per planned chapter - concise intro and closing summary - total length matching the user request Do not claim completion after this phase. ## Phase 3: Images Use the image-series skill path for one standalone PNG per chapter. If an image-generation tool is available, call it for each chapter before PDF assembly. If no image-generation tool is available, stop after `article.md` and `prompts/image-prompts.md`, then report that the PDF cannot be completed because the required image artifacts are missing. Required checks before continuing: - PNG count equals chapter count. - Every `assets/images/*.png` is a real non-empty PNG. - Every chapter image is a generated or user-provided bitmap image, not a text placeholder, blank rectangle, SVG prompt card, or decorative filler. - `assets/images/manifest.md` exists and references only relative paths inside the artifact scope. - `prompts/image-prompts.md` and `series.config.json` exist. If any check fails, stop and report the missing image artifact. Do not generate a placeholder PDF. ## Phase 4: PDF Use the PDF creation path to assemble `article.md` plus image manifest into `exports/final.pdf`. The PDF must contain: - title page - chapter text - matching chapter image near each section - closing summary Use a PDF library such as reportlab when available. The file must be large enough to plausibly contain text and images; a tiny one-page placeholder PDF is a failure. Do not use a Markdown-to-PDF command by itself unless the Markdown contains real image links and the generated PDF is verified to contain embedded image objects. After creating the PDF, verify at least one embedded image object exists and the image count is at least the chapter count. With `pypdf`, use an equivalent check: ```python from pypdf import PdfReader reader = PdfReader("exports/final.pdf") image_count = 0 for page in reader.pages: resources = page.get("/Resources", {}) xobjects = resources.get("/XObject", {}) if hasattr(xobjects, "get_object"): xobjects = xobjects.get_object() for obj in xobjects.values(): target = obj.get_object() if target.get("/Subtype") == "/Image": image_count += 1 assert image_count >= EXPECTED_CHAPTER_COUNT, image_count ``` ## Phase 5: Delivery Check Before final response, run equivalent checks: ```bash find . -maxdepth 4 -type f | sort file exports/final.pdf pdfinfo exports/final.pdf pdftotext exports/final.pdf - | head -40 ``` Also run an embedded-image check equivalent to the `pypdf` snippet in Phase 4. Only report success if `exports/final.pdf` exists, the expected source files are present, and the PDF contains embedded images. If the PDF has no embedded image objects, report it as incomplete and keep the missing-image issue visible.
在 GitHub 查看