Omnicast

What to check before running/installing: 1) Missing/undocumented credentials: SKILL.md and package.json mention GEMINI_API_KEY and OPENAI_API_KEY, but config/secrets.js references ELEVENLABS_API_KEY and the app includes googleapis and a Google Sign-In client — which strongly suggests you also need Google OAuth (client ID/secret or OAuth tokens) and possibly ElevenLabs keys. Confirm exactly which environment variables (and how credentials/tokens are stored) before supplying secrets. 2) Inspect omitted files: The evaluation truncated several files (youtube.js, linkedin.js, utils/geminiClient.js, and others). Open those files and verify how tokens/refresh tokens are handled, whether credentials are sent to third-party endpoints, and whether any credentials are persisted to disk or uploaded externally. 3) Prompt usage: The app sends explicit system-style prompts to AI SDKs. This is expected for composing/formatting outputs, but review those prompt strings for any unwanted data leakage instructions or hidden directives. 4) Network & SSRF protections: The ingest route includes DNS-based SSRF protection that blocks many private ranges, which is good, but DNS checks and regex-based private IP detection can be incomplete. If you plan to ingest untrusted URLs, consider running the service in a restricted network environment or sandbox. 5) Run in isolation first: Because the code will download external media (YouTube, arbitrary HTTP URLs) and call cloud LLM/TTS APIs, run it locally in an isolated machine or container until you confirm behavior. Ensure FFmpeg is installed independently and verify file write locations (the downloads folder is created under the project directory). 6) Least privilege for credentials: Create service-specific API keys and limit their scope where possible (e.g., dedicated Google OAuth client with limited scopes, ephemeral tokens if feasible). Never paste high-privilege keys into apps until you understand how they are used and stored. 7) If you need higher confidence: Provide the full content of the omitted files (routes/youtube.js, routes/linkedin.js, utils/geminiClient.js, and any remaining truncated files) so they can be audited for unexpected network calls, credential exfiltration, or writes to unexpected paths. Until then, treat undocumented env vars and the prompt-injection flag as red flags.