Python PPTX Generator V2

Python PPTX Generator

Overview

This public intake copy packages plugins/antigravity-awesome-skills/skills/python-pptx-generator from https://github.com/sickn33/antigravity-awesome-skills into the native Omni Skills editorial shape without hiding its origin.

Use it when the operator needs the upstream workflow, support files, and repository context to stay intact while the public validator and private enhancer continue their normal downstream flow.

This intake keeps the copied upstream files intact and uses the external_source block in metadata.json plus ORIGIN.md as the provenance anchor for review.

Python PPTX Generator

Imported source sections that did not map cleanly to the public headings are still preserved below or in the support files. Notable imported sections: How It Works, Security & Safety Notes, Common Pitfalls, Limitations.

When to Use This Skill

Use this section as the trigger filter. It should make the activation boundary explicit before the operator loads files, runs commands, or opens a pull request.

• Use when the user wants a Python script that generates a .pptx file automatically
• Use when the user needs slide content drafted and encoded directly into python-pptx
• Use when the user wants a quick presentation generator for demos, classes, or internal briefings
• Use when the request clearly matches the imported source intent: Generate complete Python scripts that build polished PowerPoint decks with python-pptx and real slide content.
• Use when the operator should preserve upstream workflow detail instead of rewriting the process from scratch.
• Use when provenance needs to stay visible in the answer, PR, or review packet.

Operating Table

Workflow

This workflow is intentionally editorial and operational at the same time. It keeps the imported source useful to the operator while still satisfying the public intake standards that feed the downstream enhancer flow.

1. Confirm the user goal, the scope of the imported workflow, and whether this skill is still the right router for the task.
2. Read the overview and provenance files before loading any copied upstream support files.
3. Load only the references, examples, prompts, or scripts that materially change the outcome for the current request.
4. Execute the upstream workflow while keeping provenance and source boundaries explicit in the working notes.
5. Validate the result against the upstream expectations and the evidence you can point to in the copied files.
6. Escalate or hand off to a related skill when the work moves out of this imported workflow's center of gravity.
7. Before merge or closure, record what was used, what changed, and what the reviewer still needs to verify.

Imported Workflow Notes

Imported: Overview

Use this skill when the user wants a ready-to-run Python script that creates a PowerPoint presentation with python-pptx. It focuses on turning a topic brief into a complete slide deck script with real slide content, sensible structure, and a working save step.

Imported: How It Works

Step 1: Collect the Deck Brief

Ask for the topic, audience, tone, and target number of slides if the request does not already include them. If constraints are missing, pick conservative defaults and state them in the generated script comments.

Step 2: Plan the Narrative Arc

Outline the deck before writing code:

1. Title slide
2. Agenda or context
3. Core teaching or business points
4. Summary or next steps

Keep the slide count realistic for the requested audience and avoid filler slides.

Step 3: Generate the Python Script

Write a complete script that:

• imports Presentation from python-pptx
• creates the deck
• selects appropriate built-in layouts
• writes real titles and bullet points
• saves the file with a clear filename
• prints a success message after saving

Step 4: Keep the Output Runnable

The final answer should be a Python code block that can run after installing python-pptx. Avoid pseudocode, placeholders, or missing imports.

Examples

Example 1: Ask for the upstream workflow directly

Use @python-pptx-generator-v2 to handle <task>. Start from the copied upstream workflow, load only the files that change the outcome, and keep provenance visible in the answer.

Explanation: This is the safest starting point when the operator needs the imported workflow, but not the entire repository.

Example 2: Ask for a provenance-grounded review

Review @python-pptx-generator-v2 against metadata.json and ORIGIN.md, then explain which copied upstream files you would load first and why.

Explanation: Use this before review or troubleshooting when you need a precise, auditable explanation of origin and file selection.

Example 3: Narrow the copied support files before execution

Use @python-pptx-generator-v2 for <task>. Load only the copied references, examples, or scripts that change the outcome, and name the files explicitly before proceeding.

Explanation: This keeps the skill aligned with progressive disclosure instead of loading the whole copied package by default.

Example 4: Build a reviewer packet

Review @python-pptx-generator-v2 using the copied upstream files plus provenance, then summarize any gaps before merge.

Explanation: This is useful when the PR is waiting for human review and you want a repeatable audit packet.

Imported Usage Notes

Imported: Examples

Example 1: Educational Deck

User: Create a 5-slide presentation on the basics of machine learning for a high school class.
Output: A complete Python script that creates a title slide, overview, core concepts, examples, and recap.

Example 2: Business Briefing

User: Generate a 7-slide deck for sales leadership on Q2 pipeline risks and mitigation options.
Output: A python-pptx script with executive-friendly slide titles, concise bullets, and a final recommendations slide.

Best Practices

Treat the generated public skill as a reviewable packaging layer around the upstream repository. The goal is to keep provenance explicit and load only the copied source material that materially improves execution.

• ✅ Use standard python-pptx layouts unless the user asks for custom positioning
• ✅ Write audience-appropriate bullet points instead of placeholders
• ✅ Save the output file explicitly in the script, for example output.pptx
• ✅ Keep slide titles short and the bullet hierarchy readable
• ❌ Do not return partial snippets that require the user to assemble the rest
• ❌ Do not invent unsupported styling APIs without checking python-pptx capabilities
• Keep the imported skill grounded in the upstream repository; do not invent steps that the source material cannot support.

Imported Operating Notes

Imported: Best Practices

• ✅ Use standard python-pptx layouts unless the user asks for custom positioning
• ✅ Write audience-appropriate bullet points instead of placeholders
• ✅ Save the output file explicitly in the script, for example output.pptx
• ✅ Keep slide titles short and the bullet hierarchy readable
• ❌ Do not return partial snippets that require the user to assemble the rest
• ❌ Do not invent unsupported styling APIs without checking python-pptx capabilities

Troubleshooting

Problem: The operator skipped the imported context and answered too generically

Symptoms: The result ignores the upstream workflow in plugins/antigravity-awesome-skills/skills/python-pptx-generator, fails to mention provenance, or does not use any copied source files at all. Solution: Re-open metadata.json, ORIGIN.md, and the most relevant copied upstream files. Check the external_source block first, then restate the provenance before continuing.

Problem: The imported workflow feels incomplete during review

Symptoms: Reviewers can see the generated SKILL.md, but they cannot quickly tell which references, examples, or scripts matter for the current task. Solution: Point at the exact copied references, examples, scripts, or assets that justify the path you took. If the gap is still real, record it in the PR instead of hiding it.

Problem: The task drifted into a different specialization

Symptoms: The imported skill starts in the right place, but the work turns into debugging, architecture, design, security, or release orchestration that a native skill handles better. Solution: Use the related skills section to hand off deliberately. Keep the imported provenance visible so the next skill inherits the right context instead of starting blind.

Related Skills

• @00-andruia-consultant - Use when the work is better handled by that native specialization after this imported skill establishes context.
• @00-andruia-consultant-v2 - Use when the work is better handled by that native specialization after this imported skill establishes context.
• @10-andruia-skill-smith - Use when the work is better handled by that native specialization after this imported skill establishes context.
• @10-andruia-skill-smith-v2 - Use when the work is better handled by that native specialization after this imported skill establishes context.

Additional Resources

Use this support matrix and the linked files below as the operator packet for this imported skill. They should reflect real copied source material, not generic scaffolding.

• README.md

Imported Reference Notes

Imported: Security & Safety Notes

• Install python-pptx only in an environment you control, for example a local virtual environment
• If the user will run the script on a shared machine, choose a safe output path and avoid overwriting existing presentations without confirmation
• If the request includes proprietary or sensitive presentation content, keep it out of public examples and sample filenames

Imported: Common Pitfalls

• Problem: The generated script uses placeholder text instead of real content Solution: Draft the narrative first, then turn each slide into specific titles and bullets

• Problem: The deck uses too many slides for the requested audience Solution: Compress the outline to the most important 4 to 8 slides unless the user explicitly wants a longer deck

• Problem: The script forgets to save or print a completion message Solution: Always end with prs.save(...) and a short success print

Imported: Limitations

• Use this skill only when the task clearly matches the scope described above.
• Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
• Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.