agentsclimarketplace

Html slideshow

Skill nahiddotai/operator-powers/plugins/operator-powers/skills/html-slideshow

AI skills to operate and grow. Twenty-eight practical powers for non-technical operators.

Install
npx -y skills add nahiddotai/operator-powers --skill html-slideshow

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

  • 19 days oldThe repository was created 19 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

Create a responsive browser-based presentation, keynote-style HTML deck, workshop deck, pitch deck, or shareable horizontal slideshow and verify navigation and layout.

SKILL.md

2.3 KB, as published. Nobody here has run it

HTML Slideshow

Create a finished browser presentation that tells one coherent story and works without a slide platform.

Job contract

  • Owns: horizontal, browser-based slide decks.
  • Does not own: 1080x1350 social carousels (instagram-carousel-maker) or reusable visual identity (brand-system-builder).
  • Finished deliverable: working HTML deck, source attribution, and viewing instructions.

Workflow

  1. Establish audience, purpose, viewing context, duration, source material, and brand constraints.
  2. Create the story spine before styling: opening tension, development, proof, resolution, action.
  3. Choose a visual direction from the source, audience, and brand constraints. Use a small set of recurring motifs rather than a generic card-deck treatment.
  4. Use one idea per slide and vary composition to match the job of the slide. Cut content instead of shrinking type.
  5. Build semantic HTML, scoped CSS, keyboard and click navigation, slide counter, and responsive scaling.
  6. Avoid dependencies unless the user needs them. Keep external assets credited and legally usable.
  7. Test first, middle, last, overflow, keyboard controls, and common viewport sizes.
  8. Return the actual file, not only a storyboard.

Minimum quality bar

  • Clear visual hierarchy at presentation distance.
  • A visual direction that reflects the source or brand rather than an interchangeable template.
  • Real examples, screenshots, diagrams, or source-specific proof when the supplied material supports them.
  • Keyboard navigation with left/right arrows and space.
  • No clipped text or accidental scrollbars.
  • Respect prefers-reduced-motion when animation is used.
  • Source or credit factual claims and third-party media.

Delivery note

Report the deck path, slide count, how to open it, what was tested, and any external asset dependency.

Guardrails

  • Never invent statistics, customer quotes, logos, or endorsements.
  • Do not use copyrighted imagery without permission or a usable licence.
  • Do not publish or deploy the deck unless the user explicitly approves that external action.

Gives 1 of the 12 instructions most slides presentations skills give

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 slidehere, and in 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

  • establish audience purpose context and brand constraints
  • cut content instead of shrinking type
  • build semantic html with scoped css
  • implement keyboard and click navigation
  • implement slide counter and responsive scaling
  • avoid dependencies unless needed

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once.

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.