agentsclimarketplace

Web ppt

Skill realraelrr/knot-skills/skills/web-ppt

Curated Knot agent skills distribution for Codex workspaces, office files, ingestion, Markdown rendering, planning, and handoff.

Install
npx -y skills add realraelrr/knot-skills --skill web-ppt

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

One thing to look at

  • 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 single-file horizontal HTML presentation decks with rich visual style. Use when the user asks for a web PPT, HTML slides, magazine-style deck, Swiss-style deck, horizontal swipe deck, or a shareable presentation that should open directly in a browser. Use office-pptx instead when the requested final artifact is a native PowerPoint .pptx file.

The file declares its own license as AGPL-3.0. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

3.5 KB, as published. Nobody here has run it

Web PPT Skill

Create a single-file HTML deck using the vendored upstream runtime. Knot owns only this entry adapter: skill name, trigger semantics, delivery boundary, and verification routing. Keep assets/, references/, scripts/, and LICENSE synchronized with the upstream source commit recorded in UPSTREAMS.md.

Routing

Use this skill for browser-based presentation deliverables:

  • web PPT or HTML slides
  • magazine-style or Swiss-style decks
  • horizontal swipe decks
  • shareable presentations that should open directly in a browser

Use office-pptx instead when the requested final artifact is a native PowerPoint .pptx file. Do not use this skill for document extraction, knowledge ingestion, or Office XML-level editing.

Templates

  • Style A: editorial magazine / e-ink feel, serif display type, warm visual tone.
  • Style B: Swiss international style, dense grid, strong functional accent color.

Workflow

  1. Resolve the target style. If the user does not specify, choose Style A for narrative/editorial topics and Style B for technical, product, roadmap, or data-heavy topics.
  2. Clarify only blocking inputs: audience, duration/page count, source material, images or screenshots, theme color, and hard constraints.
  3. Copy the matching template into the work area:
    • Style A: assets/template.html
    • Style B: assets/template-swiss.html
  4. Plan the slide outline before editing HTML. Keep one idea per slide.
  5. Use upstream reference files for detailed workflow and style rules:
    • Style A layouts: references/layouts.md
    • Style B locked layouts: references/swiss-layout-lock.md
    • Style B examples and rules: references/layouts-swiss.md
    • Components: references/components.md
    • Themes: references/themes.md or references/themes-swiss.md
    • Image prompt guidance: references/image-prompts.md
    • Screenshot framing: references/screenshot-framing.md
    • Final QA: references/checklist.md
  6. Write final deliverables under the current direct-user workspace deliverables/ directory, or under the current authorized group workspace deliverables/ directory in group scope. Use the Knot delivery helper expected by the workspace.
  7. Open the generated index.html in a browser and visually inspect every slide before delivery.

Style Rules

  • Do not mix Style A and Style B CSS/components in the same deck.
  • For Style B, follow the upstream conservative Swiss defaults in the bundled validator and references. Do not relax those defaults locally.
  • Use real content, data, images, or generated assets. Do not leave placeholder blocks, lorem ipsum, unused sample slides, or broken image paths.
  • Avoid emoji as interface decoration; use icons or typography from the template.
  • Keep browser delivery simple: the generated deck should open directly as a local HTML file unless the user asks for hosting.

Verification

Before claiming completion:

node scripts/validate-swiss-deck.mjs path/to/index.html  # Style B only

Then inspect the deck in a browser. Fix visible overlap, clipped text, misaligned images, missing assets, blank slides, or navigation problems before handoff.

Gives 0 of the 12 instructions most pdf office docs skills give

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

  • extract text using pdfplumberin 92 of 635, across 25 files
  • create PDFs using reportlabin 83 of 635, across 16 files
  • read FORMS.md to fill out PDF formsin 80 of 635, across 13 files
  • OCR scanned PDFs using pytesseractin 77 of 635, across 10 files
  • merge or split PDFs using qpdfin 70 of 635, across 3 files
  • use Excel formulas instead of hardcoded calculated valuesin 68 of 635, across 12 files
  • unpack edit xml and repack existing documentsin 63 of 635, across 8 files
  • document sources for hardcoded valuesin 61 of 635, across 9 files
  • write minimal python code without unnecessary commentsin 59 of 635, across 7 files
  • run the recalculation script after adding or modifying formulasin 58 of 635, across 6 files
  • fix all identified formula errors and recalculatein 58 of 635, across 6 files
  • format years as text stringsin 57 of 635, across 5 files

Said here and by no other author read

  • create a single-file HTML deck
  • plan the slide outline before editing
  • choose Style A for narrative topics
  • choose Style B for technical topics
  • clarify only blocking inputs
  • use real content in the deck

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.