Apple Style PPT Maker

Create Apple-style minimalist presentation slides through a strict JSON-first workflow. Use when an agent must clarify user requirements, lock topic/content/...

Security Scan

The skill's requirements, code and instructions are consistent with an image-generating PPT workflow that uses a Gemini/Google GenAI key; nothing in the package indicates clear misdirection or hidden exfiltration, but it does load environment files from parent/home locations so you should confirm no sensitive credentials will be picked up.

Purpose & Capability

Name/description request Gemini API keys and a CLI runner (uv) and the code files call a Google GenAI client to generate images and export PPTX — these requirements align with an image-generation→PPTX workflow.

Instruction Scope

Runtime instructions are narrowly scoped to: require uv, clarify requirements with the user, build/validate a JSON plan, generate images via the GenAI client, allow per-slide regeneration, and export PPTX. They do not instruct unrelated system access. One notable behavior: the utility will search for and load .env files from the current dir, the skill dir, plan parents and a home path (.codex/skills/...) which can cause environment variables from ancestor or home locations to be loaded into the process.

Install Mechanism

No remote download/install spec; scripts are included and declare their Python dependencies via PEP-723 inline metadata. The workflow expects 'uv' to be present to bootstrap dependencies; no untrusted network fetches or obfuscated installers are present in the repository.

Credentials

The only required credentials are Gemini API keys (APPLE_STYLE_PPT_MAKER_GEMINI_API_KEY or GEMINI_API_KEY), which are appropriate for the stated purpose. However, the code will auto-load .env files from a list of candidate locations (including parent folders and a home .codex path), which could cause unrelated secrets present in those files to be loaded into the process — review any .env files in ancestor directories/home before running.

Persistence & Privilege

The skill does not request always:true, does not modify other skills, and writes outputs only to configured output directories (and snapshots history subfolders). It does not request system-wide persistent privileges beyond reading/writing files where run.

Assessment

This skill appears to do what it says: it uses a Gemini API key to generate images and assembles them into a PPTX. Before installing/running: 1) Ensure you are willing to provide a Gemini/Google GenAI API key (APPLE_STYLE_PPT_MAKER_GEMINI_API_KEY or GEMINI_API_KEY) because slide text and prompts will be sent to that remote API. 2) Confirm there are no sensitive credentials in .env files in the current directory, any parent directories, or your home (.codex/skills/...) because the skill will search and load .env from those locations. 3) Install the required 'uv' runner (or run the scripts directly with Python if you prefer), and review outputs directory paths to avoid overwriting important files. If you want to reduce scope, set the required API key explicitly in the environment before running and run the scripts from an isolated project directory without stray .env files.

Overview

Drive a deterministic presentation pipeline for Apple-style minimalist decks. Enforce requirement clarification, strict schema validation, full-plan review, consistent slide rendering, selective page regeneration, and PPTX export.

Workflow

0. Check uv availability. If missing, stop and ask the user to install uv.
1. Clarify requirements with the user.
2. Build and validate slides_plan.json.
3. Get user review for the full JSON plan before image generation.
4. Generate all slide images at default 2K and webp.
5. Run result review and regenerate specific pages when requested.
6. Export slides to final.pptx.

Step 0: Verify uv

Run:

uv --version

If the command fails:

• stop the workflow immediately
• ask the user to install uv
• continue only after uv is available

Step 1: Clarify Requirements

Use a friendly, conversational tone. Do not expose internal schema field names to the user.

Ask in natural language and confirm:

• this deck's core topic
• target audience and meeting context
• expected speaking duration and target page count
• desired tone and language
• must-keep points and sensitive points to avoid

Follow user input language by default. Do not generate images before all clarification items are confirmed.

Internal mapping rule (do not show to user):

• map the confirmed answers to the internal requirement fields used by the JSON plan

Step 2: Build Structured Slide JSON

Create slides_plan.json and validate it against references/slides-schema.json. Start from references/slides-plan-template.json when you need a fast baseline.

Use references/apple-style-spec.md to keep visual consistency and style quality.

Define both content and visual intent for each page:

• text payload (on_slide_text)
• visual blueprint (visual_blueprint)
• consistency checks (consistency_checks)

Step 3: Review Full Plan Before Rendering

Always show the complete slides_plan.json to the user. Pause until the user approves the full plan. Apply edits to the JSON plan first, then render images.

Step 4: Generate Slide Images

Run:

uv run scripts/generate_slides.py --plan slides_plan.json --out outputs/deck_a

Defaults:

• resolution: 2K
• format: webp
• aspect ratio: 16:9
• model: gemini-3-pro-image-preview (Nano Banana Pro path)

Generated files:

• images/slide-XX.webp
• prompts/slide-XX.prompt.md
• meta/slide-XX.meta.json
• deck_manifest.json

Step 5: Review and Regenerate Specific Page

Run:

uv run scripts/regenerate_slide.py \
  --plan slides_plan.json \
  --slide 4 \
  --change "Simplify data narrative and increase whitespace" \
  --out outputs/deck_a

Behavior:

• Regenerate only the target slide.
• Snapshot prior image, prompt, and metadata to history/.
• Update manifest revision metadata.

Step 6: Export PPTX

Run:

uv run scripts/export_pptx.py \
  --images-dir outputs/deck_a/images \
  --output-pptx outputs/deck_a/final.pptx

Environment

Set one of:

• APPLE_STYLE_PPT_MAKER_GEMINI_API_KEY
• GEMINI_API_KEY

Optional:

• place .env in current directory
• place .env in this skill directory

Dependency management:

• each executable script uses PEP 723 inline metadata
• run scripts with uv run ... so dependencies bootstrap automatically

Notes

• Keep style and spacing consistent across all pages.
• Prefer concise, readable text over dense paragraphs.
• Use regeneration instead of re-rendering the entire deck for isolated edits.