Slides/PPT generation and voice narration

What to check before installing: - Metadata vs runtime: The registry metadata says no env vars, but SKILL.md and every script require SLIDES_2SLIDES_API_KEY. Treat that as a documentation bug — confirm the skill will only need that single API key before installing. - API key safety: This skill sends your SLIDES_2SLIDES_API_KEY to https://2slides.com endpoints. Only provide the key if you trust that service and are willing to accept API usage and credit costs (narration and high-res generation can be expensive). Rotate the key later if you test it in a shared environment. - Dependencies and execution environment: The bundle includes Python scripts that use the 'requests' package but there is no install spec. Run them in an isolated environment (virtualenv/container) and install packages from a trusted source (pip). Avoid running arbitrary scripts system-wide without review. - Verify domain and endpoints: The scripts only call https://2slides.com/api/v1. Confirm that domain (and certificate) is legitimate and matches the service you expect. - Sandboxing: If you have doubts, run the scripts in a sandboxed VM or container, and monitor outbound network calls to confirm only 2slides endpoints are contacted. - Cost & privacy: Be aware that uploads (content, reference images, documents) and generated audio/images are sent to the vendor. Check the provider's privacy policy if you handle sensitive data. - Fixes recommended: Ask the publisher to correct the registry metadata to declare SLIDES_2SLIDES_API_KEY and to add a minimal install section listing Python and 'requests' (and any other deps). If the publisher cannot be reached, treat the missing metadata as a risk factor and follow the sandboxing guidance above.