pptx-posters
Converts HTML/CSS content into formatted research posters for presentation.
Install
mkdir -p .claude/skills/pptx-posters && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/2634" && unzip -o skill.zip -d .claude/skills/pptx-posters && rm skill.zipInstalls to .claude/skills/pptx-posters
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Create research posters using HTML/CSS that can be exported to PDF or PPTX. Use this skill ONLY when the user explicitly requests PowerPoint/PPTX poster format. For standard research posters, use latex-posters instead. This skill provides modern web-based poster design with responsive layouts and easy visual integration.Key capabilities
- →Create HTML/CSS research posters
- →Export poster content to PDF or PPTX
- →Integrate AI-generated visual elements
- →Apply responsive poster layouts
How it works
The skill uses a structured HTML/CSS template to build posters that can be exported to PDF or PPTX. It mandates the generation of simplified, high-contrast visual elements using AI before assembly to ensure readability.
Inputs & outputs
When to use pptx-posters
- →Create academic conference posters
- →Export HTML content to PowerPoint
- →Format research findings for display
About this skill
PPTX posters
Scope
Use this skill only when the requested source/deliverable is an editable PowerPoint poster. Do not route an unspecified poster request here merely because PowerPoint is available.
Version 2.0 generates a real one-slide .pptx from strict local JSON. It does not use
HTML conversion, external templates, schematic/image-generation services, API keys,
environment files, network requests, or mandatory figure styles.
Hard gates
Stop instead of guessing when any gate is unmet:
- The author has not supplied exact poster content and source records.
- Any claim, number, citation, author, affiliation, funding statement, figure, license, or QR target is unresolved.
- Current conference and printer requirements are not confirmed.
- Author approval is not bound to the current manifest content hash.
- An asset is remote, outside the manifest directory, unhashed, or unapproved.
- An input is
.pptm, contains macros/external relationships/OLE/embedded files, or is an untrusted template. - The requested workflow needs PowerPoint to be opened or executed automatically.
- A script reports a package, layout, DPI, contrast, or output-plan blocker.
Never fabricate missing material or leave a plausible placeholder. Drafts fail closed.
Install exact generation dependencies
From the skill directory:
uv venv
uv pip install "python-pptx==1.0.2" "Pillow==12.3.0" "lxml==6.1.1"
Generation requires exactly:
python-pptx==1.0.2
Pillow==12.3.0
lxml==6.1.1
All CLIs use lazy optional imports, so python -B scripts/<tool>.py --help works
without these packages. Use -B to avoid bytecode artifacts.
Establish requirements before layout
Record these separately:
- physical trim width/height and orientation;
- bleed on each edge;
- safe margin inside trim;
- PowerPoint canvas width/height;
- uniform physical-artboard/canvas print scale;
- conference maximum dimensions and delivery format;
- printer trim, bleed, margin, scaling, color-mode, and proof requirements;
- final-output font and raster-DPI thresholds, each labeled as a heuristic or tied to an exact source.
- required font faces, workstation availability, embedding permission, and the substitution/proof workflow.
There is no universal poster size. Microsoft currently limits each custom PowerPoint dimension to 1–56 inches and uses one size for all slides. If the physical artboard is larger, use a proportional canvas only when the printer confirms scaling.
Read references/poster_layout_design.md.
Build the manifest
Copy assets/poster_manifest_template.json into the project. The template is
deliberately invalid until every replacement token, false confirmation, and draft
approval is resolved.
Follow references/manifest_spec.md and references/poster_content_guide.md.
The manifest requires:
- exact source IDs for document metadata, every element, and every asset;
author_verified: trueon every source;author_approved: trueon every element and asset;- local PNG/JPEG paths and lowercase SHA-256 hashes;
- exact provenance and license/permission for every optional image;
- approved alt text and, when needed, a source-bound native long description;
- explicit reading order and design rectangles;
- visible exact fallback URL/text for every local QR image;
- confirmed conference/printer rules;
- declared sRGB contrast pairs and redundant data encoding;
- approval bound to canonical manifest content.
To obtain the content hash after all non-approval fields pass:
python -B scripts/validate_manifest.py poster.json \
--print-content-hash
Give that exact manifest and hash to the author. Then set approval.status to
approved, record approver and offset-aware timestamp, and copy the hash. Any
non-approval edit invalidates approval.
Validate the approved manifest and local assets:
python -B scripts/validate_manifest.py poster.json
Audit assets and palette before generation
python -B scripts/inventory_images.py poster.json \
--output poster.assets.json
python -B scripts/check_palette.py poster.json \
--output poster.palette.json
python -B scripts/plan_export.py poster.json \
--output poster.export-plan.json
Effective DPI is pixels divided by final placed inches, not image metadata DPI. The inventory fully decodes bounded images and blocks EXIF/XMP/comments and embedded text/application metadata; strip those offline, then rehash and reapprove the asset. Contrast uses WCAG 2.2 sRGB mathematics; applying those values to a physical poster is a design target, not a standalone conformance claim. Keep color-redundant labels, markers, shapes, patterns, or line styles.
If the printer requires CMYK, the plan blocks print-readiness until a printer-approved conversion/profile and proof exist. Do not claim that a native PowerPoint PDF is CMYK-compliant.
Read references/poster_design_principles.md.
Generate the PPTX
Use a new output path:
python -B scripts/generate_poster.py poster.json \
--output poster.pptx \
--report poster.generation.json
Generation:
- creates a new blank presentation; it never loads a user template;
- sets the approved canvas before adding content;
- uses one native title placeholder, native text boxes, and local pictures;
- preserves image aspect ratio with
containfitting; - disables text auto-shrink;
- adds elements in approved reading order;
- writes approved picture alt descriptions and explicit text language to PresentationML;
- does not embed fonts, audio, video, OLE, ActiveX, links, or other media;
- removes default printer-settings binary data and normalizes package timestamps;
- inspects the package before and after the alt-text patch;
- refuses overlaps, out-of-bounds shapes, low final font size/DPI, unsafe packages, and existing destinations.
It renders exact manifest text. It does not compose, summarize, research, or correct scientific content.
Run final technical audits
python -B scripts/inspect_pptx.py poster.pptx \
--output poster.package.json
python -B scripts/check_layout.py poster.pptx \
--manifest poster.json \
--output poster.layout.json
The package inspector reads bounded ZIP metadata and selected XML only. It never extracts members or opens/executes the presentation. It rejects:
- every non-
.pptxextension, including.pptm; - packages outside the bounded one-slide generator profile;
- macro/VBA, ActiveX, custom UI, OLE, embedded, executable, and binary parts;
- every external relationship, including remote linked images and hyperlinks;
- unsafe/duplicate ZIP paths, symlinks, encryption, oversized expansion, and excessive compression ratios;
- malformed or entity-bearing inspected XML;
- missing internal relationship targets.
Read references/pptx_security.md.
Manual PowerPoint and accessibility gate
Automation cannot certify accessibility, text rendering, or scientific accuracy. In a fully patched PowerPoint:
- Open only the generated and technically clean file.
- Run Review > Check Accessibility.
- Inspect the Reading Order pane and object names.
- Review every alt text and native long description.
- Test keyboard and screen-reader navigation.
- Confirm fonts are installed/licensed; check embedding choices, substitution, glyphs, equations, overflow, contrast, and all edges.
- Verify that color is never the only encoding.
- Test every QR code and its visible fallback URL/text.
- Obtain author sign-off on all content and citations.
Microsoft's 18 pt slide recommendation is not a universal poster minimum. Evaluate font size at final physical output using the manifest's labeled basis and proofs.
Export and print
Use the approved export plan. When PDF is required, export from the reviewed PowerPoint using Standard/high print quality rather than Minimum size.
Independently verify the PDF:
- page/artboard dimensions, orientation, trim, and bleed;
- one-page output if required;
- fonts, clipping, glyphs, equations, and image resampling;
- tags, reading order, alt text, language, and links;
- RGB/CMYK conversion and physical color proof;
- conference naming, file-size, and upload rules.
Print a reduced-scale proof and obtain the printer's required proof. Re-run all checks after any change.
Use assets/poster_quality_checklist.md for release sign-off.
Bundled CLIs
validate_manifest.py— strict content/provenance/approval validator.generate_poster.py— exact-pinned local PPTX generator.inspect_pptx.py— non-executing ZIP/XML security inspector.check_layout.py— bounds, overlap, reading-order, and final-font checker.inventory_images.py— asset hash/metadata/effective-DPI manifest.check_palette.py— WCAG contrast and heuristic palette report.plan_export.py— dimensions, scale, fonts, color, media, export, and print preflight.
References
references/manifest_spec.mdreferences/poster_content_guide.mdreferences/poster_design_principles.mdreferences/poster_layout_design.mdreferences/pptx_security.mdreferences/security_validation.mdreferences/source_ledger.md
When not to use it
- →Standard research posters without PPTX requirement
- →LaTeX-based poster creation
Prerequisites
Limitations
- →Strict limit of 5-6 sections per poster
- →Requires explicit user request for PPTX format
- →Mandatory font size and white space constraints for visuals
How it compares
It provides a web-based design workflow specifically for PowerPoint-compatible posters, whereas standard academic posters typically use LaTeX.
Compared to similar skills
pptx-posters side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| pptx-posters (this skill) | 9 | 2mo | Review | Intermediate |
| pitch-deck | 16 | 9mo | Review | Beginner |
| infographic-creator | 1 | 3mo | No flags | Intermediate |
| html-ppt-zhangzara-editorial-tri-tone | 0 | 2mo | No flags | Beginner |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by K-Dense-AI
View all by K-Dense-AI →You might also like
pitch-deck
ailabs-393
Generate professional PowerPoint pitch decks for startups and businesses. Use this skill when users request help creating investor pitch decks, sales presentations, or business pitch presentations. The skill follows standard 10-slide pitch deck structure and includes best practices for content and design.
infographic-creator
antvis
基于给定文字内容创建精美信息图。当用户请求创建信息图时使用。
html-ppt-zhangzara-editorial-tri-tone
skeletorflet
|
create-an-asset
anthropics
Generate tailored sales assets (landing pages, decks, one-pagers, workflow demos) from your deal context. Describe your prospect, audience, and goal — get a polished, branded asset ready to share with customers.
xpager
mishahanin
Produce a 31C OnePager (xPager) using the locked corporate template. Three-page branded document - dark full-bleed cover with ODUN.ONE wordmark, capability page, and proof/contact page. Renders to PDF + HTML. Trigger when the user says "xPager", "x-pager", "onepager", "one-pager", "1-pager", "produc
pptx
Wizarck
>