Ai Video Background
v1.0.0Change, replace, and customize video backgrounds with AI — swap backgrounds in real-time, add virtual environments, blur distracting backgrounds, replace gre...
⭐ 0· 48·0 current·0 all-time
bypeandrover adam@peand-rover
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
The skill is an instruction-only wrapper for a video-background API (NemoVideo). Requesting a NEMO_TOKEN and performing an HTTPS POST to a nemovideo.ai endpoint is consistent with the described capability.
Instruction Scope
SKILL.md contains a curl example that uploads videos to https://mega-api-prod.nemovideo.ai/api/v1/generate with an Authorization: Bearer $NEMO_TOKEN. The instructions do not ask the agent to read unrelated local files, but they do direct uploading potentially sensitive video content to an external service — this is expected but privacy-sensitive.
Install Mechanism
No install spec or code is provided (instruction-only). That reduces on-disk risk — the main runtime risk is network transmission of user video data to the external API.
Credentials
The declared primary credential (NEMO_TOKEN) is appropriate for calling the NemoVideo API. However, the registry summary listed 'Required env vars: none' while primaryEnv is NEMO_TOKEN, and metadata lists a config path (~/.config/nemovideo/). This small inconsistency should be clarified (the skill will need the token — either via env var or config file).
Persistence & Privilege
The skill is not marked 'always: true' and has no install steps that modify other skills or system-wide settings. The agent may call it autonomously (default), which is normal; combine that with credential use consciously.
Assessment
This skill appears internally consistent: it uploads videos to a NemoVideo API using a NEMO_TOKEN and replaces/blur backgrounds as described. Before installing or enabling it, consider: 1) Privacy: recorded videos (and anything visible in frames) will be sent to a third-party endpoint — confirm the service's data retention, processing, and deletion policies. 2) Credentials: provide a service-specific NEMO_TOKEN (do not reuse high-privilege tokens such as cloud provider or GitHub tokens). 3) Metadata mismatch: the registry summary says no required env vars while the skill uses NEMO_TOKEN and a config path (~/.config/nemovideo/); ask the publisher how the token is expected to be supplied (env var vs config file) and whether the skill will read that config path automatically. 4) Test safely: try with non-sensitive sample videos first. 5) Network trust: verify the endpoint (nemovideo.ai) and confirm you trust the operator before sending sensitive content.Like a lobster shell, security has layers — review code before you run it.
latestvk97a7yaygkdev8z71159ngkwfn83stkm
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
Runtime requirements
🖼️ Clawdis
Primary envNEMO_TOKEN