Skill flagged — suspicious patterns detected
ClawHub Security flagged this skill as suspicious. Review the scan results before using.
Google Colab GPU Runtime
v1.3.0Execute code on Google Colab GPU runtimes (T4/L4/A100/H100) and manage persistent storage via Google Drive. Use when tasks need GPU compute (ML training, inf...
⭐ 0· 107·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name/description (Colab GPU runtimes + Drive persistence + TTS) align with the provided scripts: colab_run.py (assign/connect kernels, GPU selection), colab_drive.py (Drive upload/download), colab_tts.py (F5-TTS orchestration). No unrelated credentials or services are requested in metadata.
Instruction Scope
Runtime instructions include creating/updating ~/.colab-mcp-auth-token.json and optionally ~/colab-mcp-oauth-config.json, injecting that token into scripts sent to Colab, and mounting Drive from inside Colab. This is necessary for Drive persistence but means an OAuth token (including refresh token) is embedded into scripts uploaded to remote Colab runtimes — a sensitive but expected step for this functionality. Minor mismatch: SKILL.md says 'No browser needed (headless API)' while reauth_with_drive.py explicitly opens a browser or prints a URL for interactive auth.
Install Mechanism
This is instruction-only (no remote download/install spec). The scripts bootstrap a local .colab-venv and install Python deps using a helper tool named 'uv' (the README instructs 'pip install uv'). Re-exec behavior and venv creation are local and self-contained; there are no external arbitrary archive downloads or URL shorteners.
Credentials
The skill requires access to a local OAuth token file (~/.colab-mcp-auth-token.json) and optionally a client config file for reauth; these are directly related to Colab/Drive access and are proportionate. However, the token contains sensitive scopes and refresh tokens. The TTS helper optionally calls ElevenLabs APIs using an API key passed by the user (not stored by the skill) — also proportionate to the TTS feature.
Persistence & Privilege
The skill does write local state (.colab-venv/, ~/.colab-runtime-state.json, ~/.openclaw/private/ren-voice/) and creates temporary files (inject_and_run.sh creates a token-bearing temp script with restricted permissions and cleans it up). always:false and normal model invocation are used. It does not modify other skills or global agent settings.
Assessment
This skill appears to do what it claims, but it requires and manipulates sensitive OAuth tokens. Before installing: (1) Understand that you must create/maintain ~/.colab-mcp-auth-token.json (contains OAuth tokens and refresh tokens) and that inject_and_run.sh will embed a base64 copy of that token into a temporary script that is uploaded and executed on a Colab VM — that exposes the token to the remote runtime. (2) Use a dedicated Google account or GCP project if you want to limit blast radius, and restrict OAuth client credentials as much as possible. (3) Only run reauth_with_drive.py on a trusted machine/browser and ensure ~/colab-mcp-oauth-config.json is the genuine client config you expect. (4) Consider revoking the token after use or periodically rotating it. (5) Note the small mismatch: the skill advertises 'no browser needed' yet reauth may open a browser for initial Drive scope consent. (6) Review and confirm you trust any code you inject to Colab (templates include token placeholders and Drive access). If any of these steps are unacceptable, do not install or run the skill.Like a lobster shell, security has layers — review code before you run it.
colabvk97ckayfpxgxxxv3rr2wnd12798358g6drivevk97ckayfpxgxxxv3rr2wnd12798358g6gpuvk97ckayfpxgxxxv3rr2wnd12798358g6latestvk97ckayfpxgxxxv3rr2wnd12798358g6trainingvk97ckayfpxgxxxv3rr2wnd12798358g6ttsvk97ckayfpxgxxxv3rr2wnd12798358g6
License
MIT-0
Free to use, modify, and redistribute. No attribution required.