pptx-author
- Repo stars 29,745
- Author updated Live
- Author repo financial-services
- Domain
- Documentation
- Compatible agents
-
- Claude Code
- Cursor
- Cline
- Codex
- Windsurf
- Gemini CLI
- +20
- Trust score
- 88 / 100 · community maintained
- Author / version / license
- @anthropics · no license declared
- Token usage
- Lean
- Setup complexity
- Plug-and-play
- External API key
- Not required
- Operating systems
- Unspecified (assume cross-platform)
- Runtime requirements
- Python
- Permissions
-
- Read-only
- Write / modify
- Network behavior
- Local-only
- Install commands
- 26 variants
Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.
Heads up: 未限定 allowed-tools，默认拥有全部工具权限。
---
name: pptx-author
description: Produce a .pptx file on disk (headless) instead of driving a live PowerPoint document — for mana…
category: documentation
runtime: Python
---
# pptx-author output preview
## PART A: Task fit
- Use case: Produce a .pptx file on disk (headless) instead of driving a live PowerPoint document — for managed-agent sessions with no open Office app. Use this skill when running headless (managed-agent / CMA mode) and you need to deliver a PowerPoint deck as a file artifact rather than editing a live document via mcpofficepowerpoint_*. runs entirely locally; runs o….
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “Output contract / How to build the deck / Conventions (mirror the live-Office pitch-deck skill)” and do not present inference as author intent.
## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “Produce a .pptx file on disk (headless) instead of driving a live PowerPoint document — for managed-agent sessions with no open Office app. Use this skill when running headless (managed-agent / CMA mode) and you need to deliver a PowerPoint deck as a file artifact rather than editing a live document via mcpofficepowerpoint_*. runs entirely locally; runs o…”.
- **02** When the source has headings, the agent prioritizes “Output contract / How to build the deck / Conventions (mirror the live-Office pitch-deck skill)” so the result follows the author’s structure.
- **03** Typical output includes task judgment, concrete steps, required commands or file edits, validation, and follow-up options.
- **04** Risk context follows the fingerprint: read files, write/modify files; mostly runs locally; usually needs no extra API key.
## Running Rules
- read files, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding scope.
- Return the result, validation criteria, and next iteration options.The source does not require a stable slash command. After installation, invoke the skill by name and describe the task.
Name target files or source material, expected output, forbidden changes, and whether network or shell access is allowed. Permission fingerprint: read files, write/modify files.
Start with a small task and check whether the result follows “Output contract / How to build the deck / Conventions (mirror the live-Office pitch-deck skill)”. Inspect diffs, logs, previews, or tests before expanding scope.
Confirm the final output includes a concrete result, evidence, and next action. If it stays generic, tighten inputs, boundaries, and acceptance criteria.
---
name: pptx-author
description: Produce a .pptx file on disk (headless) instead of driving a live PowerPoint document — for mana…
category: documentation
source: anthropics/financial-services
---
# pptx-author
## When to use
- Produce a .pptx file on disk (headless) instead of driving a live PowerPoint document — for managed-agent sessions wit…
- Use it when the task has clear inputs, repeatable steps, and validation criteria.
## What to provide
- Target material, scope, expected result, and forbidden changes.
- Whether network, commands, file writes, or external services are allowed.
## Execution rules
- Organize steps around “Output contract / How to build the deck / Conventions (mirror the live-Office pitch-deck skill)” and keep inference separate from source facts.
- read files, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding the task.
## Output requirements
- Return the deliverable, key evidence, validation method, and next action.
- Mark missing information as unknown; do not invent commands, platforms, or dependencies.The author source anchors workflow facts; repository files anchor sources and commands; Fluxly only adds fit, limitations, and quality judgment.
skill "pptx-author" {
input -> user goal + target files + boundaries + acceptance criteria
context -> Output contract / How to build the deck / Conventions (mirror the live-Office pitch-deck skill)
rules -> SKILL.md triggers / order / output contract
runtime -> Python | read files, write/modify files | mostly runs locally
guardrails -> usually needs no extra API key + small-sample validation + diff/log review
output -> copyable result + checklist + next iteration
}pptx-author
Use this skill when running headless (managed-agent / CMA mode) and you need to deliver a PowerPoint deck as a file artifact rather than editing a live document via mcp__office__powerpoint_*.
Output contract
- Write to
./out/<name>.pptx. Create./out/if it does not exist. - Return the relative path in your final message so the orchestration layer can collect it.
How to build the deck
Write a short Python script and run it with Bash. Use python-pptx:
from pptx import Presentation
from pptx.util import Inches, Pt
prs = Presentation("./templates/firm-template.pptx") # if a template is provided
# or: prs = Presentation()
slide = prs.slides.add_slide(prs.slide_layouts[5]) # title-only
slide.shapes.title.text = "Valuation Summary"
# ... add tables / charts / text boxes ...
prs.save("./out/pitch-<target>.pptx")Conventions (mirror the live-Office pitch-deck skill)
- One idea per slide. Title states the takeaway; body supports it.
- Every number traces to the model. If a figure comes from
./out/model.xlsx, footnote the sheet and cell. - Use the firm template when one is mounted at
./templates/; otherwise default layouts. - Charts: prefer embedding a PNG rendered from the model over native pptx charts when fidelity matters.
- No external sends. This skill writes a file; it never emails or uploads.
When NOT to use
If mcp__office__powerpoint_* tools are available (Cowork plugin mode), use those instead — they drive the user's live document with review checkpoints. This skill is the file-producing fallback for headless runs.
Decide Fit First
Design Intent
How To Use It
Boundaries And Review