Skill flagged — suspicious patterns detected
ClawHub Security flagged this skill as suspicious. Review the scan results before using.
Max Studio API
v0.1.3Integrate with the Max Studio API for image generation, video generation, uploads, task polling, media downloads, JWT acquisition from labs.google/fx, and ba...
⭐ 0· 34·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
Capability signals
These labels describe what authority the skill may exercise. They are separate from suspicious or malicious moderation verdicts.
OpenClaw
Suspicious
high confidencePurpose & Capability
The skill's name and description (Max Studio API integration) align with the included code (API wrapper, download helpers, JWT acquisition). However the registry metadata claims no required environment variables or binaries, while the code clearly expects/uses MAX_STUDIO_API_KEY, MAX_STUDIO_JWT and may use GOOGLE_EMAIL / GOOGLE_PASSWORD. The code also requires Node + Playwright (chromium) and Python packages (requests) which are not declared. This mismatch between claimed requirements and actual needs is a coherence concern.
Instruction Scope
SKILL.md explicitly instructs reusing a fixed Chrome profile and describes three JWT acquisition modes including automating Google login and extracting access_token from labs.google/fx. The included fetch_labs_google_jwt.js will drive a persistent Chromium context, perform sign-in, call NextAuth endpoints, and write a storage state file. These actions involve reading/writing browser profile data and possibly using user Google credentials — scope that goes beyond simple API calls and is sensitive.
Install Mechanism
There is no install spec, yet the skill includes code that requires runtime dependencies: Python with requests, and a Node/Playwright script that needs Playwright and a Chromium channel. Playwright typically downloads browser binaries at runtime. The lack of any declared install or dependency instructions is an omission that increases risk (unexpected runtime side effects, missing binaries, or automatic browser downloads).
Credentials
The registry declares no required env vars, but the SKILL.md and code expect MAX_STUDIO_API_KEY and MAX_STUDIO_JWT and the JS script can accept GOOGLE_EMAIL and GOOGLE_PASSWORD (or env vars). Requesting Google credentials (password) and reusing a browser profile to extract tokens is sensitive. These credentials/ artifacts (cookies/storage state) give broad access to Google account state and are not proportionately documented or gated by the registry metadata.
Persistence & Privilege
The skill does not set always:true and does not attempt to modify other skills. It does, however, instruct using and reusing a persistent Chrome profile and writes storage state (labs-google-storage-state.json) to disk; that means credential/session artifacts may be persisted locally. This is expected for the claimed JWT-extraction feature but is a persistence consideration users should be aware of.
What to consider before installing
Before installing or running this skill, note these important points:
- The skill will need your Max Studio API key and a Google access token (JWT). The package metadata did NOT declare these env vars — expect to provide MAX_STUDIO_API_KEY and MAX_STUDIO_JWT when using it.
- The included Node script can automate Google sign-in and requires Google credentials (GOOGLE_EMAIL, GOOGLE_PASSWORD) or a pre-existing browser profile. Do NOT hand over your Google password unless you fully trust the skill author and understand the risks. Prefer the manual JWT option (have the user obtain and paste the token) if you want lower risk.
- The fetch_labs_google_jwt.js uses Playwright and persistent Chromium profiles and will read/write browser profile storage (cookies, tokens). That can expose account state; consider running this only in an isolated environment (throwaway VM or container) and pointing the profile directory to a location you control.
- The repository provides no install spec. You will need Python (requests) and Node + Playwright (and Playwright will likely download browser binaries). Verify and install dependencies from trusted sources before running. Inspect the code yourself if possible.
- If you must use it: (1) ask the author to declare required env vars and provide an install/dependency file (requirements.txt / package.json + playwright install instructions), (2) avoid supplying Google passwords — use manual JWTs or an isolated profile, (3) run the Playwright flow in a sandboxed environment and review the storageState file before reuse, and (4) confirm the BASE_URL and endpoints (max-studio.store vs .shop) match the vendor you expect.
Given these omissions and the sensitive browser automation behavior, treat the skill as suspicious until the author clarifies declared requirements and provides safer, documented dependency and credential handling.scripts/fetch_labs_google_jwt.js:68
Environment variable access combined with network send.
Patterns worth reviewing
These patterns may indicate risky behavior. Check the VirusTotal and OpenClaw results above for context-aware analysis before installing.Like a lobster shell, security has layers — review code before you run it.
latestvk973hgemw5eaj6g35py7p4qqv584s6n3
License
MIT-0
Free to use, modify, and redistribute. No attribution required.