CyberPPT Turns Your Reports Into Consulting-Style Decks

The user gives you a set of documents, research reports, or business data and wants a consulting-firm-style PPT (industry research, brand strategy, e-commerce analysis, executive briefings, board materials, client proposals, project reviews). You follow the three-stage process of CyberPPT (MIT license). First, organize the material into a traceable evidence table and an SCR storyline (situation, complication, resolution). Next, use image generation to make a visual blueprint for each page. Finally, use PptxGenJS to rebuild the blueprint as a PPTX where text, numbers, and charts are all editable, then render each page and check it against the blueprint. Every stage needs user confirmation. Do not skip any stage.

For a beginner walkthrough, see the tutorial Turn Source Material into a Consulting-Style PPT with CyberPPT.

Triggers

The user says things like "turn these materials into a PPT," "make a consulting-style report," "industry analysis PPT," "board materials," or "client proposal." Or the user uploads a DOCX, PDF, TXT, or XLSX file and asks for a presentation.

Not a good fit: text-light, image-heavy talks, personal opinion sharing, and story-driven decks. For these requests, first tell the user that this skill makes high-density, consulting-style decks.

Hard Rules

1. The SKILL.md and references/ in the repo are the source of truth. Before each stage starts, read the matching reference file. Do not enter a stage without reading it. This page is only a summary.
2. Facts come only from the user's material. Every number and judgment must trace back to a source file. Every recommendation must too. When evidence is missing, flag the gap. Do not fill it in or make it up. Text and numbers produced by image generation are not evidence, and neither is a logo.
3. Three stages, two confirmations, no skipping. Get the outline confirmed in stage one before you work on style and blueprints. Get all blueprints confirmed before you build the PPTX.
4. Stage three is built and checked one page at a time. Do not rebuild every page at once, or you will only get a skeleton. Render each page as an image, compare it side by side with its blueprint, and move to the next page only after the user confirms.
5. Key information must be editable. Titles, body text, key numbers, charts, tables, footers, and SO WHAT conclusions are rebuilt with native text and shapes. Do not tile blueprint screenshots as backgrounds.
6. Build the final PPTX only with PptxGenJS. Do not use python-pptx, HTML-to-PPT, or screenshot-to-PPT.
7. Shrinking the font to fit too much content is a failure. Re-lay out the page instead.

Install

First, check:

ls ~/.codex/skills/cyber-ppt/SKILL.md 2>/dev/null && echo "installed" || echo "not installed"

If it is not installed, tell the user where it will be installed. After they agree:

git clone https://github.com/crazyykhllc-bit/CyberPPT.git ~/.codex/skills/cyber-ppt

Windows (PowerShell):

git clone https://github.com/crazyykhllc-bit/CyberPPT.git "$env:USERPROFILE\.codex\skills\cyber-ppt"

The directory name must be cyber-ppt, and the root must contain SKILL.md. Update with git pull.

Runtime requirements:

• The author designed it for Codex. Stage two needs Codex's image generation (ImageGen) to produce the blueprints.
• Stage three needs Node.js and PptxGenJS. The validation script needs Python 3.
• Rendering for comparison needs PowerPoint to export each page as PNG. The repo only provides a Windows PowerShell export script. On other systems, confirm with the user how to export first.

Workflow

Stage	What you do	What the user confirms
1. Source analysis	Read all the material and build an evidence table: facts, numbers, judgments, items to verify, and contradictions. Draft 2 to 3 storylines and narrow them to one SCR. Produce a page-by-page outline that notes the information density, chart plan, and SO WHAT for each page	Page count, storyline, page-by-page outline
2. Style and blueprints	Send the 8 built-in style samples (assets/palette-samples/) directly to the user to choose from. Once a style is locked, generate one 16:9 blueprint per page. Blueprint text uses the user's language	Which style to use, and the blueprints for all pages
3. Rebuild the PPTX	Rebuild each page from its blueprint with PptxGenJS. Pick icons from assets/icons/ first. Export a render of each page, compare it side by side with the blueprint, and run validation	The render of each page

Validation command (do not drop any arguments in stage three):

python scripts/validate_pptx.py deck.pptx --manifest slide_manifest.json --visual-qa visual_qa_gate.json --strict --json-out report.json

In --strict mode, any errors mean rework. Do not just explain them. Passing validation does not mean the slides look right. You still have to check the rendered images.

The 8 Built-in Styles

No.	Style
01	Classic deep-red consulting
02	Cool gray with burgundy
03	Warm ivory with dark wine
04	Ivory with deep blue
05	Light gray-white with dark green
06	Paper beige with bronze-brown
07	Clean light gray with black and gold
08	Cool gray-white with deep purple

Choose only from these 8. Do not invent a new style. Once a style is chosen, the whole blueprint set keeps it.

Common Questions

• The user says "use only the material I gave you": This only limits where facts and numbers come from. You still make the style samples and blueprints.
• Unusual charts like curve charts and Sankey diagrams are the hardest to rebuild: Trace them precisely with SVG paths or custom shapes, following the repo's curve-tracing rules. Do not approximate them with default curves or rectangles.
• Wrong icon: Swap in a closer match from the icon library. Do not hand-draw complex icons.
• User wants 100% fidelity: The author's advice is that AI gets you about 90 percent of the way. Let the user fix small issues like line breaks and font sizes in PowerPoint. Chasing perfection uses a lot of tokens.

Output Format

1. Stage one: a summary of the evidence table, a comparison of 2 to 3 storylines, the chosen SCR, and the page-by-page outline.
2. Stage two: the 8 style sample images (sent directly), and the full page-by-page blueprints after a style is chosen.
3. Stage three, for each page: a render of the single page, a side-by-side image of the blueprint and the render, the validation result, and which content on this page is editable.
4. Delivery: the PPTX path, slide_manifest.json, visual_qa_gate.json, and the strict validation result.

In One Sentence

Get the evidence and storyline straight first, then pick a style and make the blueprints, and finally rebuild each page as an editable PPTX. Get the user's approval at every step.