Hl presentation
Skill HorizenLabs/hl-claude-marketplace/skills/hl-presentation
Create on-brand Horizen Labs PowerPoint/slide-deck presentations. Use this skill whenever the user wants to build, edit, or extend a Horizen Labs slide deck, pitch deck, or PowerPoint presentation — including when they mention .pptx files, PowerPoint, Google Slides, or slide decks in a Horizen Labs context. Builds from the real on-brand template at assets/hl-presentation-template.pptx (theme: HL 2026 Theme) rather than inventing a look from scratch, and shares its brand tokens (navy/teal/lavender, IBM Plex Sans/Mono + Roboto) with the horizenlabs-design-system skill.From its SKILL.md
npx -y skills add HorizenLabs/hl-claude-marketplace --skill hl-presentationAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
5.8 KB, as published. Nobody here has run it
HL Presentation
Builds on-brand Horizen Labs slide decks from the real template at assets/hl-presentation-template.pptx, rather than inventing a visual language from scratch. Always load the pptx skill alongside this one — it owns the actual .pptx mechanics (scripts, gotchas, QA); this skill only supplies the Horizen Labs brand and layout specifics on top of it.
Relationship to horizenlabs-design-system
The presentation template's theme (literally named HL 2026 Theme) and the web design system's tokens are the same brand, confirmed to match almost exactly: navy #041742, teal #4CDFDD/#00C0BD, lavender #BBC0FF, magenta #F251EA, IBM Plex Sans (headings) + Roboto (body) + IBM Plex Mono (labels/mono). [[horizenlabs-design-system]]'s tokens.md is still the canonical source for exact hex values — references/brand.md in this skill only documents how those tokens show up on slides specifically (logo placement, canvas size, gradient motifs, one known status-color discrepancy) and should not be treated as a second source of truth that could drift from it.
Reference Pointers
| File | Contents |
|---|---|
references/brand.md | Colors, fonts, logo usage/placement, canvas dimensions, gradient/motif patterns — cross-referenced against the web tokens |
references/layouts.md | The template's 20-layout catalog (deduplicated to 12 families), what each is for, which example slide demonstrates it |
assets/hl-presentation-template.pptx | The real on-brand template — source of truth for layouts |
assets/logo-full.png | Full "HORIZEN LABS" wordmark + shield lockup (title slide use) |
assets/logo-mark.png | Shield-only mark (recurring small corner placement, every slide) |
Workflow
Default to editing the template, not generating from scratch. The template already has 20 real, on-brand layouts (see references/layouts.md) — treat a fresh pptxgenjs build as a fallback for content the template genuinely has no layout for (e.g. a native chart slide), not the default path.
- Pick layouts. Read
references/layouts.mdfor the family that fits each piece of content. Confirm visually with the pptx skill'sscripts/thumbnail.py assets/hl-presentation-template.pptx hl-template-thumbsbefore committing to one. - Duplicate. Unzip the template, use
scripts/add_slide.pyto duplicate the chosen example slide (not the bare layout, when a worked example exists — it already has the corner logo, footer, and any decorative autoshapes correctly wired). Do all structural work (add/delete/reorder slides) before editing any slide's content. - Fill in content. Edit the duplicated slide's XML directly. Preserve the recurring corner logo mark +
"Horizen Labs |‹#›"footer on every content slide (title slide instead gets the full lockup — seereferences/brand.md). Keep the template's native 21.33in × 12.19in canvas; don't renormalize to a standard 13.333×7.5 size. - Reuse template assets, don't recreate them. The template's own media library (see
references/layouts.md— reference slide 12) has both abstract lavender→teal gradient blob icons and literal navy line icons (gear, etc.) — copy from there instead of generating new icon art, unless nothing there fits. - Clean up. Run
scripts/clean.pyafter structural edits are final, then zip. - Validate.
scripts/office/validate.py out.pptx --original assets/hl-presentation-template.pptx(always pass--original— the template itself has some pre-existing XSD quirks from its Google Slides export that aren't yours to fix). On Windows, run withPYTHONUTF8=1set — without it the validator crashes with acharmap codec can't decode byteerror on this template's layouts/master (Windows' default non-UTF-8 encoding, not a real defect in the deck). - QA. Convert to images and visually check every new/changed slide per the pptx skill's QA section — pay particular attention to text fit, since IBM Plex Sans/Mono aren't on the universal safe-render font list (leave ~10% size slack, don't fully trust the LibreOffice preview's tight text-fit on those elements).
Key Rules
- Never ship slide 12 (the asset library) as real content — it's a spare-parts sheet, not a template layout. Copy individual icons out of it instead.
- Status colors: use the web tokens (
#EF4444error,#22C55Esuccess,#F59E0Bwarning,#3B82F6info), not the template theme's unusedaccent5/accent6swatches — seereferences/brand.mdfor why. - Fonts stay role-locked: IBM Plex Sans for headings, Roboto for body, IBM Plex Mono for labels/numerals/mono contexts — same rule as the web design system, never swap.
- Don't touch
ppt/theme/theme1.xml-derived defaults (Arial, stock Office accent colors) — that theme part is an unused leftover;theme2.xml("HL 2026 Theme") is the one actually wired to the slide master. - The
#FF0000red text in the raw template is template-authoring instructions ("replace this," "do not edit this deck"), not a brand color — don't carry it into generated decks. - One logo per slide: full lockup on the title slide only; the small corner mark + footer credit on every other slide.