agentsclimarketplace

Slide deck

Skill protosphinx/sphinxstack/skills/slide-deck

A stack of skills for your AI agent, made for people starting from zero. 103 skills and 149 project briefs — load one into Codex, Claude Code, Copilot, Gemini, or Cursor and do the thing.

Install
npx -y skills add protosphinx/sphinxstack --skill slide-deck

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • 17 days oldThe repository was created 17 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
  • 0 stars0 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.

What its author says it does

Copied from the file, not written here

Turn their presentation into a deck that doesn't look templated. Restructured, restyled, presenter notes, exported. Use when they say "help with my slides", "my presentation looks bad", or a talk is coming up.

SKILL.md

2.8 KB, 609 tokens by cl100k_base, as published. Nobody here has run it

slide-deck

Rebuild a deck with someone who has a real presentation coming up — a class talk, club pitch, or project demo. Start from what they actually have to say, not from a theme. Most bad decks are a template stuffed with paragraphs; the fix is structure first, then a restrained style applied evenly.

Structure before style

  1. Ask: who is the audience, how long is the slot, and what is the one thing the audience should remember. Write that sentence down; it becomes the closing slide.
  2. Get their existing slides or outline. Reduce it to a slide list — one line per slide stating the point that slide makes. Merge or remove a slide that has no distinct point before styling.
  3. Budget: roughly one slide per minute of slot, fewer is fine. Reordering happens on the list, where it is cheap.

The slide rules

Apply these while building, explaining each once, the first time it bites:

  • One point per slide. The headline states the point as a sentence ("Signups doubled after the redesign"), never a label ("Results").
  • Almost no body text. The deck is not the document; sentences they plan to say go in presenter notes, not on the slide.
  • One font, two sizes, two colors plus an accent. If they have a brand kit, use it exactly.
  • Data gets one chart per slide with the takeaway as the headline. Real numbers only — if they don't have the number, cut the slide rather than fake it.
  • Images only when they carry the point. No decorative stock photos, no clip art.

Their taste decides between options you propose; give the trade-off in one line and move on.

Notes and rehearsal

Write presenter notes for every slide: 2–4 short lines in their speaking voice, first line is the opener for that slide. Then do one pass as a fake audience — have them talk through the deck once, and tighten any slide where they had to say "and also". Time it against the slot.

Export

Build in whatever they will actually present from: Google Slides or PowerPoint if they have it, otherwise an HTML deck printed to PDF. Whatever the tool, end with:

  • The deck exported as PDF (survives any projector)
  • The editable source in their account or repo
  • Notes attached to the slides, or as a separate one-pager they can print

Done

  • The editable deck and a PDF export open correctly
  • Every slide has one stated point, all numbers and sources are checked, and presenter notes are complete
  • One timed rehearsal fits the actual slot on the presentation device or a realistic substitute

If the talk is part of a bigger project, suggest design-critique later on the deck itself.

Gives 0 of the 12 instructions most slides presentations skills give in 609 tokens

Counted across 568 of the 571 authors here whose files we hold, read 2026-08-06

  • include a visual element on every slidein 52 of 568, across 21 files
  • put one idea per slidein 50 of 568, across 42 files
  • state the design approach before writing codein 38 of 568, across 8 files
  • validate XML immediately after each editin 37 of 568, across 7 files
  • rasterize gradients and icons as PNG images before referencing themin 37 of 568, across 7 files
  • generate and inspect thumbnails to validate layoutin 37 of 568, across 7 files
  • commit to a single visual motif across every slidein 37 of 568, across 12 files
  • use web-safe fonts onlyin 36 of 568, across 7 files
  • keep 0.5 inch minimum marginsin 35 of 568, across 9 files
  • use two-column layout for slides with charts or tablesin 34 of 568, across 5 files
  • save a template inventory analysis to a filein 33 of 568, across 4 files
  • use subagents to visually inspect rendered slidesin 33 of 568, across 9 files

Said here and by no other author read

  • write down the one thing the audience should remember
  • reduce existing slides to a one-line per slide list
  • merge or remove any slide with no distinct point
  • budget roughly one slide per minute
  • write headlines as sentences rather than labels
  • put sentences to be spoken in presenter notes

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.