Codeck Export

This handles the final export step for the codeck presentation system: turning assembled HTML into PDF or PPTX files. It's designed as an internal publishing lane that gets called after deck assembly is done. The interesting part is the required QA loop. It won't just dump a file and call it done. Instead it generates thumbnails, converts outputs to images, and uses visual inspection to catch overlapping elements, text overflow, and rendering differences before signing off. If it spots source problems during QA, it writes threads instead of patching files directly. Use this when you need polished deliverables from codeck with actual quality control baked in.

skills.sh installs: 185
GitHub stars: 197
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add hiyeshu/codeck --skill codeck-export --agent claude-code

Installs into .claude/skills of the current project.

Files

codeck export — @export lane

Minimum conversation, maximum output. Export the deck to the user's format.

@export owns PDF/PPTX output and export QA.

Write boundaries:

May write final PDF/PPTX files in the user's project directory
May write export QA notes to $DECK_DIR/review.md or $DECK_DIR/MEMORY.md
May update $DECK_DIR/roles/export.md, $DECK_DIR/tasks/tasks.md, and $DECK_DIR/channel/YYYY-MM-DD.md
Must not edit deck.md, DESIGN.md, custom.css, slides.html, or speech.md
Export defects that require source changes become proposals in $DECK_DIR/threads/threads.md