presentations
- Repo stars 36,883
- Author updated Live
- Author repo CodeWhale
- Domain
- Data
- Compatible agents
-
- Claude Code
- Cursor
- Cline
- Codex
- Windsurf
- Gemini CLI
- +20
- Trust score
- 88 / 100 · community maintained
- Author / version / license
- @Hmbown · 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: presentations
description: Create, edit, inspect, or convert PowerPoint decks and PPTX slide presentations with practical l…
category: data
runtime: Python
---
# presentations output preview
## PART A: Task fit
- Use case: Create, edit, inspect, or convert PowerPoint decks and PPTX slide presentations with practical layout and verification steps. Use this skill when the user asks for slides, a deck, a PowerPoint file, or a improve the slide's job over flattened screenshots of text. runs entirely locally; runs on Python. Works with Claude Code, Cursor, Cline and 23 more..
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “Workflow” and do not present inference as author intent.
## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “Create, edit, inspect, or convert PowerPoint decks and PPTX slide presentations with practical layout and verification steps. Use this skill when the user asks for slides, a deck, a PowerPoint file, or a improve the slide's job over flattened screenshots of text. runs entirely locally; runs on Python. Works with Claude Code, Cursor, Cline and 23 more.”.
- **02** When the source has headings, the agent prioritizes “Workflow” 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. Choose the trigger
The source does not require a stable slash command. After installation, invoke the skill by name and describe the task.
Provide inputs and boundaries
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.
Validate with a small run
Start with a small task and check whether the result follows “Workflow”. Inspect diffs, logs, previews, or tests before expanding scope.
Review before delivery
Confirm the final output includes a concrete result, evidence, and next action. If it stays generic, tighten inputs, boundaries, and acceptance criteria.
---
name: presentations
description: Create, edit, inspect, or convert PowerPoint decks and PPTX slide presentations with practical l…
category: data
source: Hmbown/CodeWhale
---
# presentations
## When to use
- Create, edit, inspect, or convert PowerPoint decks and PPTX slide presentations with practical layout and verification…
- 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 “Workflow” 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. Evidence boundary and execution chain
The author source anchors workflow facts; repository files anchor sources and commands; Fluxly only adds fit, limitations, and quality judgment.
skill "presentations" {
input -> user goal + target files + boundaries + acceptance criteria
context -> Workflow
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
}Presentations
Use this skill when the user asks for slides, a deck, a PowerPoint file, or a
.pptx deliverable.
Workflow
- Determine the deck purpose, audience, slide count, and output path.
- Build an outline with one clear claim or job per slide.
- Use available local tools:
python-pptxfor editable PPTX creation and edits- LibreOffice for conversion or preview export when installed
- Existing images, screenshots, charts, or generated assets only when they improve the slide's job
- Keep slides editable. Prefer native text boxes, tables, charts, and images over flattened screenshots of text.
- Use restrained layouts: clear title, concise body, enough whitespace, and consistent type sizes. Avoid cramming paragraphs onto slides.
- Verify the PPTX by reopening it, checking slide count and visible text, and exporting previews when a renderer is available.
If python-pptx or a renderer is missing, ask before installing dependencies.
Do not claim visual QA passed unless previews were actually generated and
inspected.
Decide Fit First
Design Intent
How To Use It
Boundaries And Review