agentleFS
ai-workspace-labai-workspace-lab/xworkspace-core-skills/skills/workflows/content-pdf-with-images/SKILL.md

content-pdf-with-images

Skill8 starsChanged 5 months agoMITView on GitHub

图文 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.

The file

Show its rules and text

We split this skill into the rules it gives an agent

17 rules. About 0 are common, 12 are distinctive, and 5 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈12

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 5

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Before generating, extending, repairing, or repainting chapter images, read ../../marketplace/pdf/editable-reconstruction.md only for its …

    line 10
  2. Distinctive:

    Only when the user explicitly requests editable reconstruction of a scanned, flattened, or image-only PDF, apply the complete per-page …

    line 12
  3. Distinctive:

    If the user specifies a particular content sequence or evolutionary path, ensure the exact sequence is preserved.

    line 30
  4. Very specific:

    Create workflow.plan.md before writing final content.

    line 34
  5. Distinctive:

    If the user gives an explicit chapter sequence, preserve it literally.

    line 43
  6. Distinctive:

    Do not claim completion after this phase.

    line 54
  7. Distinctive:

    Use the image-series skill path for one standalone PNG per chapter.

    line 58
  8. Distinctive:

    If an image-generation tool is available, call it for each chapter before PDF assembly.

    line 60
  9. Very specific:

    Every assets/images/*.png is a real non-empty PNG.

    line 68
  10. Distinctive:

    Every chapter image is a generated or user-provided bitmap image, not a text placeholder, blank rectangle, SVG prompt card, or decorative …

    line 69
  11. Distinctive:

    If any check fails, stop and report the missing image artifact.

    line 74
  12. Very specific:

    Use the PDF creation path to assemble article.md plus image manifest into exports/final.pdf.

    line 78
  13. Distinctive:

    Use a PDF library such as reportlab when available.

    line 87
  14. Distinctive:

    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 …

    line 89
  15. Very specific:

    After creating the PDF, verify at least one embedded image object exists and the image count is at least the chapter count.

    line 92
  16. Distinctive:

    Before final response, run equivalent checks:

    line 114
  17. Very specific:

    Only report success if exports/final.pdf exists, the expected source files are present, and the PDF contains embedded images.

    line 125

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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 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:

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:

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.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.