AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Presentation Making

skill-msimchowitz-writing-skills-presentation-making · by msimchowitz

Plan, create, revise, and review presentation decks with a clear narrative, accurate content, coherent visual system, editable source, and rendered-slide verification. Use for PowerPoint, Keynote, Google Slides, Beamer, lecture decks, talks, pitches, speaker notes, slide outlines, or slide-level visual and writing review.

No reviews yet
0 installs
32 views
0.0% view→install

Install

$ agentstack add skill-msimchowitz-writing-skills-presentation-making

✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-msimchowitz-writing-skills-presentation-making)

Reliability & compatibility

Security review passed
0 installs to date
no reviews yet
1mo ago

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
Are you the author of Presentation Making? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Presentation Making

Turn source material into a presentation built for an audience and a live explanation. Preserve technical accuracy while making the argument easier to follow than the source alone.

Load detailed guidance selectively

  • Read [deck-workflow.md](references/deck-workflow.md) before creating a new

deck or substantially restructuring an existing deck.

  • Read [visual-design-review.md](references/visual-design-review.md) when

selecting a visual system, designing layouts, or reviewing rendered slides.

  • For a narrow text edit to a few existing slides, use the core rules below

without loading both references.

Core rules

  • Establish the audience, purpose, venue, allotted time, source material, and

required output format before building.

  • Read the full source relevant to the talk. Do not invent claims, examples,

results, equations, references, or quotations.

  • Plan the narrative and the job of each slide before editing the deck.
  • Give each slide one primary point or teaching move.
  • Use an existing approved deck or template as the visual source when one is

available. Preserve its typography, margins, colors, and page furniture.

  • Keep one visual system. Do not mix themes or recreate a supplied style from

memory.

  • Prefer diagrams, equations, figures, plots, and concrete evidence over dense

prose. Do not add decorative images.

  • Keep visible text short enough to read at presentation distance. Put details

needed for delivery, but not simultaneous reading, in speaker notes.

  • Preserve notation exactly. Render mathematics with true superscripts,

subscripts, primes, limits, and conditioning notation.

  • Use progressive builds only when each step helps the spoken explanation.
  • Keep the source editable. Retain PowerPoint objects or compilable Beamer

source rather than flattening the deck into images.

  • Render and inspect every slide before delivery. Fix clipping, overflow,

accidental overlap, tiny text, inconsistent spacing, distorted images, placeholder residue, and unreadable citations.

Workflow

  1. Resolve the source and constraints.
  2. Write a slide plan with the point, evidence, layout, and build behavior for

every slide.

  1. Select a visual source and map planned slides to suitable layout families.
  2. Build the editable deck with the appropriate presentation tools.
  3. Render the complete deck and inspect every physical slide or overlay.
  4. Correct defects, rerender, and repeat until the review passes.
  5. Report the final deck path and any unresolved content questions.

When the user provides feedback, preserve the exact concern and convert repeated feedback into a short reusable rule for later decks.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet, be the first.

Versions

  • v0.1.0 Imported from the upstream source.