Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →onewave-ai/design-export-repair
Fixes broken decks/PDFs exported from Claude's "Design" feature (or similar AI deck generators) — cut-off or clipped text, wrong/substituted fonts, and corrupted .pptx package structure that shows up only once you export to PDF, not while looking at it in the app.
Passed 3 of 9 test cases with the skill, and 2 of 9 without it.
and 5 more in the full report
6 fixed2 passed either way10 still failing4 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 6 test cases the skill fixed. Same model, same prompt, with and without the skill.
If an exported ZIP archive contains a PPTX presentation, an `index.html` file, and a PDF file, which file does `unpack.py` select first for the primary repair workflow?
| Checked | Without skill | With skill |
|---|---|---|
| Prioritizes PPTX file extraction over other formats. | Missed | Passed |
The instructions your model reads when the skill loads.
Fixes AI-generated deck/PDF exports (built for Claude Design's export
path, but the checks are generic OOXML/PDF hygiene, not Claude-specific)
that look fine in the app but come apart once exported — text missing
its last few characters, fonts that don't match the original design, or
a .pptx that some converters choke on even though PowerPoint opens it
fine.
Four defect classes were found and fixed against a real broken export;
references/defect-classes.md has the full story for each, including how
they were confirmed and what the fix trades off. Skim it before extending
this skill to a case it doesn't already handle — in particular, defect #4
there is a good example of why "the shape geometry looks right" is not
the same claim as "the rendered PDF looks right," and it's worth reading
before assuming a new complaint is a geometry problem.
This is written for the person running Claude Code, not just for Claude — skim it once so you know what to actually do. There are two different ways a Design project reaches Claude Code, and they behave differently.
Path A — plain Export (this is the one that matches "my deck/PDF looks
broken"): In Claude Design, use Export and pick PDF, PPTX, or HTML. Save
the file, then bring it to whichever Claude Code you're using — attach it
in the chat if your setup allows that, or save it to disk and give Claude
the path. Then tell Claude to use this skill: plain language like "this
deck looks broken when I export it to PDF, can you fix it" is enough on
its own (the skill's description is written to match that phrasing), or
name it directly (design-export-repair) if you want to be explicit.
Path B — the "Send to Claude Code" button. This is a related but different feature from plain Export — it's aimed at continuing design/ prototype work in code, not at fixing a deck export, but you may end up here anyway. It offers two options, and they behave differently:
test cases passed, vs 2 / 9 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.