YouTube Upload Videos Skill

Uploads a video to YouTube using the official YouTube Data API v3 and OAuth 2.0. Use this skill when the user asks to upload a video to YouTube. It supports...

This skill appears to do exactly what it says: upload videos via the official YouTube API. Before using it: - Provide your own Google OAuth client_secret.json and keep it private. Do not paste it into public places. - The script will create token.pickle in the current folder which stores OAuth credentials—treat that file as sensitive, restrict its filesystem permissions, and remove it if you suspect compromise. - The script opens a local auth flow (browser/URL) on first run; run this only on a machine you control. - Install dependencies via pip in a virtualenv if you want isolation and to avoid supply-chain surprises. - Review the code yourself if you need stronger assurance (it uses google-api-python-client and only contacts Google APIs). Revoke the OAuth client or token from your Google account if you suspect misuse.

Type: OpenClaw Skill Name: youtube-upload Version: 1.0.0 The OpenClaw YouTube Upload skill is classified as benign. All files, including `_meta.json`, `SKILL.md`, `scripts/upload.py`, and `README.md`, align with the stated purpose of uploading videos to YouTube using the official API. The Python script (`scripts/upload.py`) uses standard Google API client libraries, handles OAuth 2.0 authentication by generating a `token.pickle` file locally, and restricts its network activity to the YouTube Data API with the appropriate `youtube.upload` scope. There is no evidence of data exfiltration, malicious execution, persistence mechanisms, obfuscation, or prompt injection attempts in `SKILL.md` designed to mislead an AI agent into unauthorized actions. File access is limited to user-specified video files and client secrets, and the locally generated authentication token.