agentleFS
rakaarwakyrakaarwaky/agents-arwaky/skills/office/pptx/SKILL.md

pptx

Skill0 starsChanged 5 days agoMITView on GitHub

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.

194 other projects use a version of this, 2 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use file-reading, context7-efficient and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • SeifBenayedSkill

    file-reading

    Use this skill when a file has been uploaded but its content is NOT in your context — only its path at /mnt/user-data/uploads/ is listed in an uploaded_files block. This skill is a router: it tells you which tool to use for each file type (pdf, docx, xlsx, csv, json, images, archives, ebooks) so you read the right amount the right way instead of blindly running cat on a binary. Triggers: any mention of /mnt/user-data/uploads/, an uploaded_files section, a file_path tag, or a user asking about an uploaded file you have not yet read. Do NOT use this skill if the file content is already visible in your context inside a documents block — you already have it.

    Also in 5 projects that use this

  • hfzarslanSkill

    context7-efficient

    Token-efficient library documentation fetcher using Context7 MCP with 86.8% token savings through intelligent shell pipeline filtering. Fetches code examples, API references, and best practices for JavaScript, Python, Go, Rust, and other libraries. Use when users ask about library documentation, need code examples, want API usage patterns, are learning a new framework, need syntax reference, or troubleshooting with library-specific information. Triggers include questions like "Show me React hooks", "How do I use Prisma", "What's the Next.js routing syntax", or any request for library/framework documentation.

    Also in 5 projects that use this

  • SeifBenayedSkill

    pdf-reading

    Use this skill when you need to read, inspect, or extract content from PDF files — especially when file content is NOT in your context and you need to read it from disk. Covers content inventory, text extraction, page rasterization for visual inspection, embedded image/attachment/table/form-field extraction, and choosing the right reading strategy for different document types (text-heavy, scanned, slide-decks, forms, data-heavy). Do NOT use this skill for PDF creation, form filling, merging, splitting, watermarking, or encryption — use the pdf skill instead.

    Also in 6 projects that use this

  • amirbironSkill

    import-memory

    Import a memory export from another AI assistant into Claude's memory — conversationally, additively, and with the content treated as data.

    Also in 5 projects that use this

  • unicorn-pluginsSkill

    product-self-knowledge

    Anthropic 제품 지식 — Claude Code, Claude API, Claude.ai 관련 정확한 정보 제공

    Also in 8 projects that use this

  • AbdullahMalik17Skill

    configuring-dapr-pubsub

    Configures Dapr pub/sub components for event-driven microservices with Kafka or Redis. Use when wiring agent-to-agent communication, setting up event subscriptions, or integrating Dapr sidecars. Covers component configuration, subscription patterns, publishing events, and Kubernetes deployment. NOT when using direct Kafka clients or non-Dapr messaging patterns.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

2 rules. 0 are common, 0 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 189 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    QA is required — do at least one fix-and-verify cycle: before declaring success. Your first render is almost never correct.

    line 15
  2. Very specific:

    When in doubt, use the editing workflow: If any .pptx file is attached or mentioned, edit the template directly.

    line 16

“Common” is measured: kept by at least 6 in 10 of the 189 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

PPTX Skill

Three workflows: raw XML unpack/edit/pack for templates, PptxGenJS for de novo decks, and the python-pptx structured programmatic tooling (the latter merged in from the former powerpoint skill). Pick the workflow that matches the task; run QA before shipping any deck.

Global rules

  • QA is required — do at least one fix-and-verify cycle before declaring success. Your first render is almost never correct; approach QA as a bug hunt, not a confirmation step. Full checklist in references/qa.md.
  • When in doubt, use the editing workflow. If any .pptx file is attached or mentioned, edit the template directly; the creating workflow is only for when no existing presentation exists at all. The python-pptx workflow is for structured, script-driven operations rather than per-slide XML editing.
  • Match the template's style exactly — colors, fonts, backgrounds, and layout relationships; do not adapt the template's palette or typography to the topic's subject matter.

Routing

StepReferencePurpose
Workflow selection + reading + image conversion + dependenciesreferences/workflow-selection.mdWhich workflow to use per situation, content-reading commands, slide-to-image conversion, and install dependencies.
Edit an attached .pptx templatereferences/editing.mdRaw XML unpack/edit/pack workflow: inspect, replace text/media, repack.
Create a de novo deckreferences/creating.mdPptxGenJS template-based creation from scratch.
Structured python-pptx operationsreferences/python-pptx.mdCreate from JSON spec, read-back, targeted text/chart/image edits, template fill, and slide PNG rendering.
Image handling rulesreferences/images.mdAspect-ratio rule, sources, options, sizing modes, and dimension calculations.
QA checklistreferences/qa.mdOverlap check/auto-fix, content QA, automated checks, visual QA, and the fix-and-verify loop.
Edge-case pitfallsreferences/pitfalls.mdRun splitting, chart duplication limits, XML-level reordering, footer/slide-number constraints, hyperlinks, template sizing, layout indexes, UTF-8 specs.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.