youtube-summarizer

Functionally, the skill matches its stated purpose: extract YouTube IDs, fetch transcripts via a local MCP transcript server, produce summaries, store full transcripts, and optionally send files to messaging platforms. The highest risks are supply-chain (git clone + npm build + inline execution of unpinned third-party code), privileged filesystem usage (hard-coded /root paths), and an explicit external file-delivery channel (message CLI → Telegram). The MCP server's Android-emulation to bypass IP blocking raises additional policy and misuse concerns. There is no direct evidence of embedded malicious code in the provided fragment (no obfuscated payloads, no hard-coded credentials), but the operational pattern could enable remote code execution or data exfiltration if followed automatically. Recommendations: do not run automated installation or node -e snippets without reviewing and pinning the third-party repository; avoid writing transcripts to root-owned, world-accessible locations; require explicit operator consent before installing or sending files externally; add integrity checks (commit SHA/signatures) and limit privileges/sandboxing for any executed third-party binaries.