slides
This Claude Code skill creates and edits PowerPoint presentation decks (.pptx files) using PptxGenJS with bundled layout helpers and validation utilities. Use it when building new decks from scratch, recreating slides from reference materials like screenshots or PDFs, modifying existing slide content, adding charts and diagrams, or troubleshooting layout problems such as text overflow, element overlaps, and font substitution issues.
git clone --depth 1 https://github.com/fcakyon/claude-codex-settings /tmp/slides && cp -r /tmp/slides/plugins/openai-office-skills/skills/slides ~/.claude/skills/slidesSKILL.md
# Slides ## Overview Use PptxGenJS for slide authoring. Do not use `python-pptx` for deck generation unless the task is inspection-only; keep editable output in JavaScript and deliver both the `.pptx` and the source `.js`. Keep work in a task-local directory. Only copy final artifacts to the requested destination after rendering and validation pass. ## Bundled Resources - `assets/pptxgenjs_helpers/`: Copy this folder into the deck workspace and import it locally instead of reimplementing helper logic. - `scripts/render_slides.py`: Rasterize a `.pptx` or `.pdf` to per-slide PNGs. - `scripts/slides_test.py`: Detect content that overflows the slide canvas. - `scripts/create_montage.py`: Build a contact-sheet style montage of rendered slides. - `scripts/detect_font.py`: Report missing or substituted fonts as LibreOffice resolves them. - `scripts/ensure_raster_image.py`: Convert SVG/EMF/HEIC/PDF-like assets into PNGs for quick inspection. - `references/pptxgenjs-helpers.md`: Load only when you need API details or dependency notes. ## Workflow 1. Inspect the request and determine whether you are creating a new deck, recreating an existing deck, or editing one. 2. Set the slide size up front. Default to 16:9 (`LAYOUT_WIDE`) unless the source material clearly uses another aspect ratio. 3. Copy `assets/pptxgenjs_helpers/` into the working directory and import the helpers from there. 4. Build the deck in JavaScript with an explicit theme font, stable spacing, and editable PowerPoint-native elements when practical. 5. Run the bundled scripts from this skill directory or copy the needed ones into the task workspace. Render the result with `render_slides.py`, review the PNGs, and fix layout issues before delivery. 6. Run `slides_test.py` for overflow checks when slide edges are tight or the deck is dense. 7. Deliver the `.pptx`, the authoring `.js`, and any generated assets that are required to rebuild the deck. ## Authoring Rules - Set theme fonts explicitly. Do not rely on PowerPoint defaults if typography matters. - Use `autoFontSize`, `calcTextBox`, and related helpers to size text boxes; do not use PptxGenJS `fit` or `autoFit`. - Use bullet options, not literal `•` characters. - Use `imageSizingCrop` or `imageSizingContain` instead of PptxGenJS built-in image sizing. - Use `latexToSvgDataUri()` for equations and `codeToRuns()` for syntax-highlighted code blocks. - Prefer native PowerPoint charts for simple bar/line/pie/histogram style visuals so reviewers can edit them later. - For charts or diagrams that PptxGenJS cannot express well, render SVG externally and place the SVG in the slide. - Include both `warnIfSlideHasOverlaps(slide, pptx)` and `warnIfSlideElementsOutOfBounds(slide, pptx)` in the submitted JavaScript whenever you generate or substantially edit slides. - Fix all unintentional overlap and out-of-bounds warnings before delivering. If an overlap is intentional, leave a short code comment near the relevant element. ## Recreate Or Edit Existing Slides - Render the source deck or reference PDF first so you can compare slide geometry visually. - Match the original aspect ratio before rebuilding layout. - Preserve editability where possible: text should stay text, and simple charts should stay native charts. - If a reference slide uses raster artwork, use `ensure_raster_image.py` to generate debug PNGs from vector or odd image formats before placing them. ## Validation Commands Examples below assume you copied the needed scripts into the working directory. If not, invoke the same script paths relative to this skill folder. ```bash # Render slides to PNGs for review python3 scripts/render_slides.py deck.pptx --output_dir rendered # Build a montage for quick scanning python3 scripts/create_montage.py --input_dir rendered --output_file montage.png # Check for overflow beyond the original slide canvas python3 scripts/slides_test.py deck.pptx # Detect missing or substituted fonts python3 scripts/detect_font.py deck.pptx --json ``` Load `references/pptxgenjs-helpers.md` if you need the helper API summary or dependency details.
Agent-browser usage guide. Read this before running any agent-browser commands. Covers the snapshot-and-ref workflow, navigating pages, interacting with elements (click, fill, type, select), extracting text and data, taking screenshots, managing tabs, handling forms and auth, waiting for content, running multiple browser sessions in parallel, and troubleshooting common failures. Use when the user asks to interact with a website, fill a form, click something, extract data, take a screenshot, log into a site, test a web app, or automate any browser task.
Automate Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify, etc.) using agent-browser via Chrome DevTools Protocol. Use when the user needs to interact with an Electron app, automate a desktop app, connect to a running app, control a native app, or test an Electron application. Triggers include "automate Slack app", "control VS Code", "interact with Discord app", "test this Electron app", "connect to desktop app", or any task requiring automation of a native Electron application.
Use this skill whenever the user wants to create, read, edit, or manipulate Word documents (.docx files). Triggers include: any mention of 'Word doc', 'word document', '.docx', or requests to produce professional documents with formatting like tables of contents, headings, page numbers, or letterheads. Also use when extracting or reorganizing content from .docx files, inserting or replacing images in documents, performing find-and-replace in Word files, working with tracked changes or comments, or converting content into a polished Word document. If the user asks for a 'report', 'memo', 'letter', 'template', or similar deliverable as a Word or .docx file, use this skill. Do NOT use for PDFs, spreadsheets, Google Docs, or general coding tasks unrelated to document generation.
Use when tasks involve reading, creating, or reviewing PDF files where rendering and layout matter; prefer visual checks by rendering pages (Poppler) and use Python tools such as `reportlab`, `pdfplumber`, and `pypdf` for generation and extraction.
Use this skill any time a .pptx file is involved in any way — as input, output, or both. This includes: creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text from any .pptx file (even if the extracted content will be used elsewhere, like in an email or summary); editing, modifying, or updating existing presentations; combining or splitting slide files; working with templates, layouts, speaker notes, or comments. Trigger whenever the user mentions \"deck,\" \"slides,\" \"presentation,\" or references a .pptx filename, regardless of what they plan to do with the content afterward. If a .pptx file needs to be opened, created, or touched, use this skill.
Use this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like \"the xlsx in my downloads\") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.
This skill should be used when user asks to "query Azure resources", "list storage accounts", "manage Key Vault secrets", "work with Cosmos DB", "check AKS clusters", "use Azure MCP", or interact with any Azure service.
This skill should be used when user encounters "Tavily MCP error", "Tavily API key invalid", "web search not working", "Tavily failed", or needs help configuring Tavily integration.