claude

slides-mcp

Edit Google Slides through the slides-mcp MCP server: when to use run_deck_script, write_speaker_notes or exec_batch_update, plus Request kinds, objectId discovery, the EMU cheat sheet, the autofit:NONE invariant, and worked examples.

0 on GitHubby luutuankietMITupdated 10 days ago

Not in a marketplace yet, so it loads for one session with --plugin-dir.

Plugin slides-mcp in luutuankiet/slides-mcp. Commands read from the repo's manifest — 9 days ago.

What it installs

Skills (3)

  • codebase-map

    Where behaviour lives in this repo — a per-area map of which files and line ranges own what, so you can open the right file instead of searching for it. Use before hunting for where something is implemented, before adding a feature that touches existing behaviour, and when a change seems to need edi

  • repo-maintenance

    This repo keeps a catalogue of its own traps — failure modes that produce no error, so you find them by symptom, not by stack trace — plus its reference pages and its decision records. Use before debugging behaviour that is wrong but not crashing, before editing shared state, and whenever you finish

  • slides-mcp

    Editing Google Slides through the slides-mcp server - when to use run_deck_script (edits that depend on deck data), write_speaker_notes, or raw exec_batch_update requests, plus the Request cheat sheet. Skip this skill if you are only reading decks.

View source on GitHub

Maintain slides-mcp?

This page updates itself from your repo. Add the badge to your README, or get it Featured to pin it above the organic results with a followed link to your site.

claude & codex pluginslisted