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.
In this repository60 other files it gives its agents.
- animejsSkill
- sketch-animation-videoSkill
- sound-fx-for-videoSkill
- content_series_infographicSkill
- tech-article-seriesSkill
- agent-team-harnessSkill
- ai-agent-collaboration-standardSkill
- ci-cd-workflow-specSkill
- config-as-code-specSkill
- execution-ownership-migrationSkill
- feature-lane-release-workflowSkill
- generation-upgrade-acceptanceSkill
- gitops-canonical-resource-deliverySkill
- harness-workflowSkill
- infrastructure-as-code-specSkill
- issue-pr-traceability-standardSkill
- multi-environment-delivery-and-releaseSkill
- project-development-standardSkill
- store-and-startup-homepage-specSkill
- zero-trust-overlay-deliverySkill
- it-infra-continuous-pngSkill
- image-svg-pptx-proSkill
- autoglm-websearchSkill
- blogwatcherSkill
- Browser AutomationSkill
- docxSkill
- find-skillsSkill
- image-cogSkill
- image-resizerSkill
- pdfSkill
- pptxSkill
- Self-Improving Agent (With Self-Reflection)Skill
- skill-security-checkSkill
- skill-vetterSkill
- video-translatorSkill
- wan-image-video-gen-editSkill
- xlsxSkill
- backup-disaster-recovery-and-data-migrationSkill
- capacity-cost-and-resource-lifecycleSkill
- github-actions-operational-dispatchSkill
- incident-response-and-change-managementSkill
- network-dns-tls-edge-managementSkill
- observability-slo-and-alertingSkill
- secrets-identity-and-access-governanceSkill
- service-catalog-and-runbook-standardSkill
- system-db-three-role-securitySkill
- unified-observability-architectureSkill
- vault-eso-tls-certificate-governanceSkill
- ai-tech-news-videoSkill
- ai-ti-wo-shuo-explainerSkill
- it-infra-evolution-videoSkill
- it-infra-evolution-video-v2Skill
- product-intro-videoSkill
- swimlane-videoSkill
- video-understandingSkill
- ai-news-md-digestSkill
- article-to-image-seriesSkill
- evolutionary-social-copy-packSkill
- image-series-to-videoSkill
- research-to-slide-deckSkill
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
- Distinctive: line 10
Before generating, extending, repairing, or repainting chapter images, read ../../marketplace/pdf/editable-reconstruction.md only for its …
- Distinctive: line 12
Only when the user explicitly requests editable reconstruction of a scanned, flattened, or image-only PDF, apply the complete per-page …
- Distinctive: line 30
If the user specifies a particular content sequence or evolutionary path, ensure the exact sequence is preserved.
- Very specific: line 34
Create workflow.plan.md before writing final content.
- Distinctive: line 43
If the user gives an explicit chapter sequence, preserve it literally.
- Distinctive: line 54
Do not claim completion after this phase.
- Distinctive: line 58
Use the image-series skill path for one standalone PNG per chapter.
- Distinctive: line 60
If an image-generation tool is available, call it for each chapter before PDF assembly.
- Very specific: line 68
Every assets/images/*.png is a real non-empty PNG.
- Distinctive: line 69
Every chapter image is a generated or user-provided bitmap image, not a text placeholder, blank rectangle, SVG prompt card, or decorative …
- Distinctive: line 74
If any check fails, stop and report the missing image artifact.
- Very specific: line 78
Use the PDF creation path to assemble article.md plus image manifest into exports/final.pdf.
- Distinctive: line 87
Use a PDF library such as reportlab when available.
- Distinctive: line 89
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 …
- Very specific: line 92
After creating the PDF, verify at least one embedded image object exists and the image count is at least the chapter count.
- Distinctive: line 114
Before final response, run equivalent checks:
- Very specific: line 125
Only report success if exports/final.pdf exists, the expected source files are present, and the PDF contains embedded images.
≈ “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.
Files
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.mdarticle.mdassets/images/*.pngassets/images/manifest.mdprompts/image-prompts.mdseries.config.jsonexports/final.pdfDELIVERY.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/*.pngis 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.mdexists and references only relative paths inside the artifact scope.prompts/image-prompts.mdandseries.config.jsonexist.
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_countPhase 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 -40Also 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.
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
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.

