agentsclimarketplace

Presentation deck qa

Skill samulee003/agentic-ppt-skills/skills/presentation-deck-qa

Agent skills that route a presentation from source to stage-ready through an 8-gate pipeline. Extracted from open-slide.

Install
npx -y skills add samulee003/agentic-ppt-skills --skill presentation-deck-qa

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

Finalizes a complete presentation with aligned notes, verified evidence and timing, preview QA, and a fresh export of the chosen delivery format(s). Use when the production-qa gate is current, final downloads are requested, exports changed, or a deck must be proven stage-ready.

SKILL.md

3.9 KB, as published. Nobody here has run it

Finalize the deck for delivery

Use when production-qa is the current gate or when a deck needs final delivery. Author to the engine's technical rules (from its adapter).

Engine

This gate renders and exports, so it needs the slide engine chosen at the prototype gate. Resolve it before QA:

  • Read the engine from the status tracker via node .agents/skills/make-presentation/scripts/status.mjs next <work-root> (the JSON block in STATUS.md carries an engine field set at the prototype gate). Fall back to the ## Engine line in PRESENTATION-BRIEF.md if the tracker has no engine recorded.
  • If no engine is recorded anywhere, ask the user now, one question, with a recommended default (see adapters/; the bundled reference adapter is open-slide).
  • Read adapters/<engine>/qa.md for that engine's preview surface, export command, export format(s), and inspection steps. The sections below are the engine-agnostic backbone; the adapter supplies the engine-specific surface and exports.

Choose context

  • Use pipeline mode when presentation-work/<deck-id>/ exists. Validate its status with the shipped helper. Read the current mode from STATUS.md.
  • Use standalone mode when pipeline artifacts and STATUS.md are absent.
  • In standalone mode, derive a minimal QA context from the deck and notes: purpose, likely audience, material claims, main/backup range, timing assumptions, and unresolved risks.
  • Do not create a pipeline work area solely for finalization; only create or update STATUS.md when a pipeline work area exists.

Align content

  • Read repo instructions, the full deck, notes, and unresolved QA risks. In pipeline mode also read available PRESENTATION-BRIEF.md, EVIDENCE-LEDGER.md, STORY.md, STORYBOARD.md, GRILL-LOG.md, and SPEAKER-SCRIPT.md.
  • Check visible claims, notes, timing, and delivery wording for consistency with the approved brief, evidence ledger, story, and script.
  • Reject stale, unsupported, or contradictory claims instead of polishing around them.
  • Confirm slide count equals note count, including backup pages.
  • Check factual consistency across slides, notes, references, and exports.
  • Confirm the main-talk range, backup range, total timing, and per-slide timing.
  • Confirm one necessary job and one dominant message per slide.
  • In research-enhanced mode, require a per-slide fact check plus a reference and Q&A backup plan before export approval.

Verify the preview

  • Run the relevant repo checks and target build.
  • Review the complete deck in the engine's live preview surface.
  • Inspect full-page renders or a contact sheet, then inspect changed, dense, and image-heavy pages at full size.
  • Reject verbose paragraphs and nested text tiers. Split the slide rather than shrink text or hide overflow.
  • Treat clipping, unreadable type, inconsistent page grammar, or notes drift as failed QA.

Export and inspect

  • After deck or exporter changes, produce a fresh export in each chosen delivery format; old downloads are not repaired.
  • Follow adapters/<engine>/qa.md for the engine's export steps, archive integrity, geometry, and any native-application inspection.
  • If the preview and any export disagree, the export is not complete.

Record and hand off

  • Complete templates/QA-REPORT.md with evidence for every section and any remaining caveats.
  • In pipeline mode, update the production-qa gate in STATUS.md through .agents/skills/make-presentation/scripts/status.mjs.
  • Provide direct links to every exported file, page/note counts, timing, inspected pages, and explicit export verification evidence.

Gives 0 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 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

  • resolve the chosen slide engine before QA
  • read the engine adapter QA instructions
  • verify slide count equals note count
  • confirm talk range, backup range, and slide timing
  • reject stale, unsupported, or contradictory claims
  • review the complete deck in live preview

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.