Professional Medical PPT Slide Production

Problem

When producing medical PPT slides, general LLM outputs often lack constraints for medical precision, slide structure, and protected professional content. This skill keeps the workflow inside a protected execution path: it checks the Python environment and authorization first, then fetches protected instructions before entering slide-production logic, reducing the risk of blindly generating content when permissions or environment prerequisites are missing.

How It Works

The execution path is explicit:
- It silently detects a usable Python command and prefers $PYTHON_CMD; on Windows, it can handle cases where python opens the Microsoft Store.
- It calls scripts/auth.py for authorization, and only continues when AUTH_OK is returned.
- If AUTH_REQUIRED, CREDENTIALS_MISSING, or credential expiry is detected, it should call WorkBuddy's connect_cloud_service to obtain a JWT and then bind it via --bind-jwt.
- After authorization succeeds, it retrieves protected instructions with scripts/protected.py; only the returned content should drive subsequent slide production.

Boundaries

It is best suited for engineers or medical content producers who already have a working Python environment, an active WorkBuddy login, and valid platform authorization. If network errors, expired signatures, insufficient VIP permissions, or protected.py failures occur, the skill should stop business output and report clearly rather than degrade into speculative generation.