MCPInstall

automating-keynote

Automates Apple Keynote using JXA with AppleScript dictionary discovery. Use when asked to "create Keynote presentations", "automate slide decks", "JXA Keynote scripting", or "generate presentations programmatically". Covers document lifecycle, slides, text, shapes, images, tables, charts, transitions, and UI scripting fallback.

Installs
114
Last 24h
—
Trending rank
—
Security
Not audited

Install

Works with every agent the skills CLI supports.

npx skills add https://github.com/spillwavesolutions/automating-mac-apps-plugin --skill automating-keynote
  1. 01

    Install

    Run the command in your project. The CLI asks which agents to install for.

  2. 02

    Describe the task

    Ask your agent for something this skill covers. It loads automating-keynote automatically when relevant.

  3. 03

    Review the result

    The agent follows the SKILL.md steps, scripts and references bundled with the skill.

SKILL.md

The instructions your agent reads when the skill is triggered.

Automating Keynote (JXA-first, AppleScript discovery)

Contents

Relationship to the macOS automation skill

  • This skill focuses on Keynote-specific automation (documents, slides, charts).
  • Use automating-mac-apps for cross-app workflows or general macOS scripting foundations.
  • Assumes Apple Events knowledge from the related skill.
  • PyXA Installation: To use PyXA examples in this skill, see the installation instructions in automating-mac-apps skill (PyXA Installation section).

Core Framing

  • JXA (JavaScript for Automation) enables macOS app scripting with JavaScript syntax.
  • AppleScript dictionaries define Keynote's object model—discover via Script Editor.
  • JXA objects are specifiers: read with methods like .name(), write with assignments.
  • Production scripts use JXA for reliability; AppleScript for prototyping.
  • Important: The JXA Path() function is required when specifying file paths to Keynote (e.g., for images, exports, or opening documents). Use Path("/path/to/file") instead of plain strings.

Workflow (default)

  1. Discover terms in Script Editor > File > Open Dictionary > Keynote.
  2. Prototype minimal AppleScript: tell application "Keynote" to get name of document 1.
  3. Port to JXA: Application("Keynote").documents[0].name() with try-catch blocks.
  4. Validate with read-only probes: Application("Keynote").documents.length > 0.
  5. Use UI scripting only when dictionary lacks features (e.g. Application("System Events")).

Quick Examples

Prototype (AppleScript):

tell application "Keynote"
    get name of document 1
end tell

Production (JXA):

const keynote = Application("Keynote");
if (keynote.documents.length > 0) {
    console.log(keynote.documents[0].name());
}

Create Slide:

const doc = keynote.documents[0];
const slide = doc.slides.push(keynote.Slide({baseSlide: doc.masterSlides['Title - Center']}));
slide.defaultTitleItem.objectText = "New Slide";

Add Image to Slide (note Path() usage):

const slide = doc.slides[0];
const img = keynote.Image({
  file: Path("/Users/you/Desktop/diagram.png"),  // Path() required!
  position: { x: 100, y: 100 },
  width: 800
});
slide.images.push(img);

Validation Checklist

After implementing Keynote automation:

  • Verify Keynote is running and accessible
  • Test slide creation with master slide assignment
  • Confirm image paths use Path() function
  • Check text rendering in default text items
  • Validate export operations complete without errors

When Not to Use

  • For cross-platform presentation automation (use PowerPoint with Python libraries)
  • When AppleScript alone suffices (skip JXA complexity)
  • For web-based presentations (Google Slides, reveal.js)
  • For non-macOS platforms

What to load

  • Keynote JXA basics + runtime caveats: automating-keynote/references/keynote-basics.md
  • Keynote recipes (slides, text, images, export): automating-keynote/references/keynote-recipes.md
  • Deck generator example: automating-keynote/references/keynote-deck-generator.md
  • Chart-aware deck pattern: automating-keynote/references/keynote-chart-aware-deck.md
  • Advanced workflows (charts bridge, magic move, UI scripting): automating-keynote/references/keynote-advanced.md
  • PyXA (Python) practical examples: automating-keynote/references/keynote-pyxa.md
  • PyXA API Reference (complete class/method docs): automating-keynote/references/keynote-pyxa-api-reference.md

FAQ

What does the automating-keynote skill do?

Automates Apple Keynote using JXA with AppleScript dictionary discovery. Use when asked to "create Keynote presentations", "automate slide decks", "JXA Keynote scripting", or "generate presentations programmatically". Covers document lifecycle, slides, text, shapes, images, tables, charts, transitions, and UI scripting fallback.

How do I install automating-keynote?

Run npx skills add https://github.com/spillwavesolutions/automating-mac-apps-plugin --skill automating-keynote in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/automating-keynote/ (personal) or .claude/skills/automating-keynote/ (project).

Which AI agents can use automating-keynote?

Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.

Is automating-keynote safe to install?

No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.

Who maintains automating-keynote?

It is published by spillwavesolutions in spillwavesolutions/automating-mac-apps-plugin. It has 114 recorded installs.

More from spillwavesolutions/automating-mac-apps-plugin

View all →

automating-mac-apps

spillwavesolutions/automating-mac-apps-plugin

Open the skill to read its SKILL.md instructions.

138 installs

automating-calendar

spillwavesolutions/automating-mac-apps-plugin

Open the skill to read its SKILL.md instructions.

Popular frontend & design skills

View category →

setup-matt-pocock-skills

mattpocock/skills

Configure this repo for the engineering skills: set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.

Frontend & Design1.1M installs

frontend-design

anthropics/skills

Guidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults.

OfficialFrontend & Design1M installs

hyperframes-animation

heygen-com/hyperframes

All animation knowledge for HyperFrames — atomic motion rules, multi-phase scene blueprints, scene transitions, broader motion-design techniques, AND the seven runtime adapters (GSAP default, plus Lottie, Three.js, Anime.js, CSS keyframes, Web Animations API, TypeGPU). Use for any motion or animation task: pick 2-4 rules and compose, or load a blueprint, or look up runtime-specific API (e.g. GSAP eases / Lottie player / Three.js mixer). Also covers auditing an existing composition's choreography (animation map) and 24 named text-animation effects. HyperFrames-native: single paused timeline, seek-safe, deterministic.

prototype

mattpocock/skills

Build a throwaway prototype to answer a design question. Use when the user wants to sanity-check whether a state model or logic feels right, or explore what a UI should look like.

Frontend & Design999.2K installs

hyperframes-core

heygen-com/hyperframes

The HyperFrames composition contract — build one renderable project. Use for composition structure, the data- timing attributes, class="clip", tracks, sub-compositions, variables, framework-owned media playback, deterministic-render rules, and validation. Read before writing composition HTML.

Frontend & Design930.5K installs

vercel-react-best-practices

vercel-labs/agent-skills

React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.

OfficialFrontend & Design843.1K installs