ericrisco/rsc-harness / skills/presentations
presentations
VerifiedUse when building, theming, or exporting a presentation deck — pitch, sales, keynote, board/QBR, leave-behind one-pager — from slide structure to a token-based theme to PDF or editable PPTX (Marp, Slidev, python-pptx). NOT the words (that is `marketing`), NOT the visual tokens (that is `design`), NOT the investor story arc (that is `pitch-deck`).
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 20.6 KB |
| evals/README.md | markdown | 2.8 KB |
| evals/cases.yaml | config | 6.4 KB |
| references/brand-grounding.md | markdown | 9.0 KB |
| references/markdown-decks.md | markdown | 11.8 KB |
| references/pptx-python.md | markdown | 10.6 KB |
| references/slide-design.md | markdown | 17.6 KB |
| references/storytelling-and-decks.md | markdown | 10.0 KB |
| scripts/verify.shexecutable | script | 9.7 KB |
evals/cases.yaml
View on GitHubskill: presentations
should_trigger:
- prompt: "Build me an investor pitch deck for our seed round — 12 slides, exported to PDF."
why: "Core use case: an investor/pitch deck with a defined slide count and PDF export. The skill owns deck structure, theme, and export."
- prompt: "Turn this product memo into slides I can present at the all-hands next week."
why: "Doc-to-deck conversion for an internal all-hands is explicitly in scope ('Turning an existing doc, memo, or notes into a slide-by-slide deck')."
- prompt: "I need an editable .pptx of our Q3 board review that the CFO can change in PowerPoint."
why: "Native editable PPTX hand-off for a non-technical stakeholder is the python-pptx pipeline this skill orchestrates; QBR/board review is a named deck type."
- prompt: "Make my conference talk look incredible — it's code-heavy and I want live syntax highlighting on the slides."
why: "A keynote/conference talk with code-heavy content is in scope; the skill routes this to the Slidev pipeline. User never names a tool but describes a deck."
- prompt: "Our sales slides look like a generic AI template. Re-skin them to match our brand and tighten the story."
why: "Re-skinning/restructuring an existing deck to be on-brand and less generic is an explicit Use-when bullet; spans the brand-grounding gate plus theme-from-tokens."
- prompt: "Can you whip up a one-page leave-behind exec summary we can hand out after the demo?"
why: "A leave-behind one-pager / executive summary is an explicit deliverable this skill produces, including the presenter-vs-leave-behind variant logic."
- prompt: "Storyboard a keynote that opens with a hook, has one idea per slide, and ends with a clear ask."
why: "Deck arc, assertion-headline storyboarding, one-idea-per-slide, and a closing CTA are the skill's core narrative/design responsibilities, even without naming PDF/PPTX."
should_not_trigger:
- prompt: "Write the headline, value prop, and three benefit bullets for our landing hero — just the copy."
route_to: "marketing"
why: "Writing the words/copy in isolation (no deck layout or export) is explicitly delegated to marketing; this skill consumes that copy, it does not author it."
- prompt: "Define our brand's OKLCH color palette, type pairing, and spacing scale as design tokens."
route_to: "design"
why: "Choosing the visual tokens (palette, type, spacing, motion personality) is design's job; presentations only maps existing tokens into a slide theme."
- prompt: "Build a scroll-driven animated landing page for our product launch in Next.js."
route_to: "nextjs"
why: "A web-native, scroll/animation-heavy landing page is not a deck; the build belongs to design + nextjs, per the explicit Do-NOT-use bullet."
- prompt: "Produce a 60-second animated explainer video of how our product works, with motion graphics."
route_to: "none"
why: "A video/motion explainer as the deliverable is explicitly out of scope — this skill uses motion only as restrained slide transitions, never as the medium. No catalog sibling owns video."
- prompt: "Build the financial model spreadsheet — revenue projections, cohort retention, and a 5-year P&L."
route_to: "none"
why: "A live financial model/spreadsheet (the numbers engine) is explicitly excluded; this skill renders slides and cites the model as source of truth. No catalog sibling owns modeling."
- prompt: "Generate a Postgres query to compute monthly churn so we have a number for the deck."
route_to: "postgresdb"
why: "A pure-SQL/data task belongs to postgresdb; the deck only consumes the resulting number. The mention of 'deck' is incidental, not a deck-building request."
capability:
- scenario: "User asks: 'Build a 6-slide seed pitch deck. Thesis: onboarding v2 is why we can raise now. We have churn and activation numbers. Export to PDF, and we may need an editable PPTX for the CFO.'"
must_include:
- "Runs the brand-grounding gate FIRST — locate brand study in 02-DOCS/wiki/brand/ via root CLAUDE.md; STOP and interview if absent/incomplete; never fabricate voice; cite which brand articles grounded the deck."
- "Storyboards an assertion-headline spine (one assertion per slide, e.g. 'Onboarding v2 cut churn 40%'), not topic labels, with one idea per slide and a single locked thesis."
- "Picks a pipeline deliberately: Markdown (Marp/Slidev) when a stunning PDF is the hero vs python-pptx when the CFO must edit in PowerPoint; asks the disambiguating question or builds Markdown + warns Marp/Slidev PPTX is image-per-slide, not editable text."
- "Themes from design tokens (OKLCH palette, type scale, spacing from 02-DOCS/wiki/stack/design.md) mapped once into the theme — no hand-picked hex per slide."
- "Enforces projection legibility: body >= 24pt (28-32pt for a talk), ~6 words/line, ~6 lines/slide ceiling, contrast >= 4.5:1, 16:9."
- "Requires every metric to trace to a source and marks gaps [[NEEDS PROOF]] — never invents numbers to fill a chart."
- "Exports verified: PDF vector with fonts embedded (e.g. pdffonts shows 'emb yes'), runs scripts/verify.sh / the Deck QA gate before claiming done."
- scenario: "User asks: 'Make my conference talk slides legible and not death-by-bullets. There's a chart showing engagement went up after a redesign.'"
must_include:
- "Applies assertion-evidence: the slide title states the claim ('User engagement rose 43% after the redesign') and the chart is the evidence — not a 'Engagement' label over bullets."
- "Separates spoken vs shown: minimal on-slide text, talk track / elaboration moved to speaker notes; warns against reading slides verbatim."
- "Sets talk-grade type: body ~28-32pt, ~6 words/line and ~6 lines/slide as a ceiling; splits a crowded slide into more slides rather than shrinking text."
- "Designs the chart to make ONE point named in the headline: removes gridlines/clutter, direct labels, one pre-attentive highlighted series; bans 3-D pies, rainbow palettes, dual axes."
- "Uses restrained motion: one transition family <= 300ms, builds that reveal one idea at a time, honors reduced-motion in HTML pipelines — never animation as decoration."
- "Bans filler/hype words (revolutionary, seamless, game-changer, supercharge) and scores the draft >= 4/5 on the design rubric axes (audience-centered, visual clarity, cognitive load, accessibility) before shipping."
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| canvas-designanthropics/skillsCreate beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| docxanthropics/skillsUse this skill whenever the user wants to create, read, edit, or manipulate Word documents (.docx files) or Word templates (.dotx files). Triggers include: any mention of 'Word doc', 'word document', '.docx', '.dotx', or requests to produce professional documents with formatting like tables of contents, headings, page numbers, or letterheads. Also use when extracting or reorganizing content from .docx or .dotx files, inserting or replacing images in documents, performing find-and-replace in Word files, working with tracked changes or comments, or converting content into a polished Word document. If the user asks for a 'report', 'memo', 'letter', 'template', or similar deliverable as a Word or .docx file, use this skill. Do NOT use for PDFs, spreadsheets, Google Docs, or general coding tasks unrelated to document generation. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| pdfanthropics/skillsUse this skill whenever the user wants to do anything with PDF files. This includes reading or extracting text/tables from PDFs, combining or merging multiple PDFs into one, splitting PDFs apart, rotating pages, adding watermarks, creating new PDFs, filling PDF forms, encrypting/decrypting PDFs, extracting images, and OCR on scanned PDFs to make them searchable. If the user mentions a .pdf file or asks to produce one, use this skill. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| pptxanthropics/skillsUse this skill any time a .pptx or .potx file is involved in any way — as input, output, or both. This includes: creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text from any .pptx or .potx file (even if the extracted content will be used elsewhere, like in an email or summary); editing, modifying, or updating existing presentations; combining or splitting slide files; working with templates (.potx), layouts, speaker notes, or comments. Trigger whenever the user mentions "deck," "slides," "presentation," or references a .pptx or .potx filename, regardless of what they plan to do with the content afterward. If a .pptx or .potx file needs to be opened, created, or touched, use this skill. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |