视觉画布设计
canvas-design
基于设计原则创作静态视觉作品,用于海报与品牌图形。
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.
独立 GitHub 快照 · 自动分类 · 以原作者文档为准
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 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.
Final deliverables must stay inside the current XWorkmate/OpenClaw task artifact scope:
workflow.plan.mdarticle.mdassets/images/*.pngassets/images/manifest.mdprompts/image-prompts.mdseries.config.jsonexports/final.pdfDELIVERY.mdIf 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.
Create workflow.plan.md before writing final content. It must include:
If the user gives an explicit chapter sequence, preserve it literally.
Write article.md with:
Do not claim completion after this phase.
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:
assets/images/*.png is a real non-empty PNG.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.
Use the PDF creation path to assemble article.md plus image manifest into exports/final.pdf.
The PDF must contain:
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:
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
Before final response, run equivalent checks:
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.