Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →yuezhiai/openkb-deck-editorial
Use when the user asks the openkb chat to make a deck / slide presentation / PPT / slides / 演示稿 / 幻灯片 from their compiled KB content. Generates a polished single-file HTML deck in the Editorial Monocle visual direction (warm cream background, serif type, brick-red accent) — designed to be opened in a browser, full-screened, and shared. Does NOT apply to generating skills (that's `openkb skill new`), long-form research reports, or interactive prototypes.
Passed 10 of 17 test cases with the skill, and 4 of 17 without it.
and 9 more in the full report
9 fixed5 passed either way10 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 9 test cases the skill fixed. Same model, same prompt, with and without the skill.
In our HTML deck for `output/decks/kernel-bypass/index.html`, every slide has a top header row with a left label. For chapter slides we put "CHAPTER 01", "CHAPTER 02", etc. What exact text string must be placed in the top-left label position for the cover and closing slides?
| Checked | Without skill | With skill |
|---|---|---|
| Uses `OPENKB` as the top-left header label on cover and closing slides. | Missed | Passed |
The instructions your model reads when the skill loads.
You are designing a presentation, not writing a research report. Each slide carries one idea. Visual structure carries the narrative.
The user typed something like "make a deck about X" inside openkb chat.
You have wiki-read tools in your normal tool set, plus a write_file
tool that can write under output/**, plus a shell tool you can use to
read this SKILL.md and any files in skills/openkb-deck-editorial/ if
needed.
Pick a kebab-case slug for the deck (e.g. transformers-pitch) and
write the output to output/decks/<slug>/index.html.
Exactly one file: output/decks/<slug>/index.html.
It must be self-contained: no external <link rel="stylesheet">,
no external <script src="…">, no remote <img>. All CSS goes in a
single inline <style> in <head>. Helper JS for keyboard navigation
goes in a single inline <script> at end of <body>.
The body is a sequence of <section class="slide" data-type="...">
blocks. Each data-type must be one of the 7 values listed in §
"Slide grammar" below. The deck supports keyboard navigation: ← / →
move between slides, F toggles fullscreen, P triggers print.
Use this fixed design system. Do not improvise nearby colors, do not introduce gradients, do not bring in emojis. This is the only non-monochrome palette in the entire deck.
:root {
test cases passed, vs 4 / 17 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.