officecli-pptx
Use this skill any time a .pptx file is involved -- as input, output, or both. This includes: creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text from any .pptx file; 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', 'pitch', or references a .pptx filename.
npx skills add iOfficeAI/OfficeCLI --skill officecli-pptx --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
What it does
Instructs the agent to handle .pptx files across input and output tasks, including creating, reading/parsing, editing, combining/splitting slides, and working with templates, layouts, speaker notes, or comments. Trigger conditions: when user mentions 'deck', 'slides', 'presentation', 'pitch', or references a .pptx filename.
How it works
Provides a setup to install OfficeCLI if missing, with platform-specific commands. Emphasizes a help-first rule to consult officecli help commands for pptx elements, verbs, and JSON schemas. Enforces shell and execution discipline for quoting element paths, escaping, and JSON heredocs. Encourages incremental execution: perform one command, check exit code, then continue. Requires adherence to the deliverables standards for decks, including explicit typography sizing, layout rules, and slide structure. Mentions multiple design principles (layout, fonts, color, chart types, animation), and tells how to verify and test (view checks, live verification for animations).
Key steps explicit in the skill:
- Install officecli if missing using the provided curl/irm commands per OS.
- Verify installation via officecli --version.
- Use commands like:
officecli help pptx,officecli help pptx <element>, andofficecli help pptx <verb> <element>for guidance. - Follow the shell/execution discipline for quoting and escaping, especially with slide paths and JSON batch operations.
- Use incremental execution: one command, check exit code, then continue.
- Ensure all decks meet the deliverables standards (one idea per slide, explicit type hierarchy, typography, color, and visual rules).
- Use
view textto confirm that money values and shell variable expansions survive when writing content.
The skill prescribes concrete commands or files by reference, not direct execution text in this summary: it instructs to run help commands, install scripts, and a batch approach for content creation, while keeping structure and QA checks explicit in the steps above.
When to use it
Trigger conditions are explicit: whenever the user mentions 'deck', 'slides', 'presentation', 'pitch', or references a .pptx filename. The skill does not specify additional runtime conditions beyond these triggers.
What it can touch
The skill declares tools: claude-code, codex. It includes guidance for interacting with the OfficeCLI tool and shell/JSON inputs, but it does not enumerate specific file paths or commands beyond the help and install instructions. It references commands like officecli help pptx and officecli batch, and uses file paths in examples such as "/slide[1]/..." within its guidance. All such touches are described in the procedural text and are not listed as a separate touchable artifact here.
Caveats
- It emphasizes consulting help before guessing property names or aliases.
- It instructs to ensure static-readability of slides and to verify live animations where applicable.
- It requires adherence to a strict set of deck-delivery rules (typography, layout, color, and animation guidelines) and warns that any deviation may render the deck non-compliant.
- Licensing noted as Apache-2.0 for the skill.
# OfficeCLI PPTX Skill ## Setup If `officecli` is missing: - **macOS / Linux**: `curl -fsSL https://d.officecli.ai/install.sh | bash` - **Windows (PowerShell)**: `irm https://d.officecli.ai/install.ps1 | iex` Verify with `officecli --version` (open a new terminal if PATH hasn't picked up). If install fails, download a binary from https://github.com/iOfficeAI/OfficeCLI/releases. ## ⚠️ Help-First Rule **This skill teaches what good slides look like, not every command flag. When a property name, enum value, or alias is uncertain, consult help BEFORE guessing.** ```bash officecli help pptx # List all pptx elements officecli help pptx <element> # Full element schema (e.g. shape, chart, animation, connector, zoom, group) officecli help pptx <verb> <element> # Verb-scoped (e.g. add shape, set slide) officecli help pptx <element> --json # Machine-readable schema ``` Help reflects the installed CLI version. When skill and help disagree, **help is authoritative**. Triggers to run help immediately: `UNSUPPORTED props:` warning, unknown animation preset, `connector.shape=` enum drifts, prop-vs-alias (`lineWidth` vs `line.width`, `color` vs `font.color`). ## Shell & Execution Discipline **Shell
- Setup
- ⚠️ Help-First Rule
- Shell & Execution Discipline
- Requirements for Outputs
- All decks
- Visual delivery floor (applies to EVERY deck)
- Design Principles
- Grid, margins, negative space
- Font pairings
- Color and contrast
- Chart-choice decision table
- Animation
- Layout patterns & data display
- Image treatment (only when a slide uses a photo / screenshot / logo)
officecli help pptx # List all pptx elements officecli help pptx <element> # Full element schema (e.g. shape, chart, animation, connector, zoom, group) officecli help pptx <verb> <element> # Verb-scoped (e.g. add shape, set slide) officecli help pptx <element> --json # Machine-readable schema officecli create "$FILE" officecli open "$FILE" Cover — dark fill, centered title officecli add "$FILE" / --type slide --prop layout=blank --prop background=1E2761 officecli add "$FILE" /slide[1] --type shape --prop text="FY26 Strategic Review" \ Content — white fill, title + body + notes
What does the officecli-pptx skill do?
Use this skill any time a .pptx file is involved -- as input, output, or both. This includes: creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text from any .pptx file; 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', 'pitch', or references a .pptx filename.
How do I install it?
Run `npx skills add iOfficeAI/OfficeCLI --skill officecli-pptx --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From iOfficeAI/OfficeCLI, a repository with 25,311 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.