Video Online Ai

PassAudited by VirusTotal on May 3, 2026.

Overview

Type: OpenClaw Skill Name: video-online-ai Version: 1.0.0 The video-online-ai skill is a legitimate tool for cloud-based video editing, facilitating communication between the OpenClaw agent and the backend API at mega-api-prod.nemovideo.ai. The SKILL.md provides clear instructions for session management, file uploads, and handling Server-Sent Events (SSE) for processing. While it requests access to a configuration directory (~/.config/nemovideo/) and environment variables (NEMO_TOKEN), these are standard requirements for its stated purpose of managing video projects and authentication. No indicators of malicious intent, data exfiltration, or unauthorized command execution were identified.

Findings (0)

Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.

What this means

Private videos, audio, images, and editing instructions may be processed by the third-party cloud service.

Why it was flagged

The skill is designed to send user videos, edit prompts, and related session data to an external cloud API. That is expected for this online editing purpose, but user media can be sensitive.

Skill content
This tool takes your video clips and runs AI video editing through a cloud rendering pipeline. You upload, describe what you want, and download the result. ... All calls go to `https://mega-api-prod.nemovideo.ai`.
Recommendation

Only upload media you are comfortable sending to the Nemovideo backend, and review the provider's privacy, retention, and account terms if the content is sensitive.

What this means

Anyone with the token may be able to use the associated service credits/session, and local service configuration could contain account-related data.

Why it was flagged

The skill requires or obtains a bearer token for the video service and declares a local Nemo config path. This is plausible for a service integration, but it is credential/account-related authority.

Skill content
requires": {"env": ["NEMO_TOKEN"], "configPaths": ["~/.config/nemovideo/"]} ... Every API call needs `Authorization: Bearer <NEMO_TOKEN>`
Recommendation

Use a dedicated token/account where possible, avoid exposing NEMO_TOKEN in logs or screenshots, and verify why the local config path is needed before granting access.

What this means

Asking for export/download can trigger cloud rendering and credit usage on the service.

Why it was flagged

User phrases are mapped to remote actions such as export/render jobs. This is central to the skill's purpose, but it can create remote work and may consume credits.

Skill content
| "export" / "导出" / "download" / "send me the video" | → §3.5 Export | ✅ | ... **Export** — `POST /api/render/proxy/lambda`
Recommendation

Confirm cost or credit usage before exporting important or large projects, especially if using a paid or limited account.

What this means

Users may not automatically see when a token/session is created or which endpoint is contacted.

Why it was flagged

The skill tells the agent not to show technical connection details during normal chat. The backend is disclosed in SKILL.md, so this is a transparency note rather than evidence of deception.

Skill content
Tell the user you're ready. Keep the technical details out of the chat.
Recommendation

Ask the agent to disclose connection, upload, and export details before uploading sensitive media.

NoteHigh Confidence
ASI10: Rogue Agents
What this means

A render may keep running remotely, potentially consuming credits or leaving an unfinished job in the service.

Why it was flagged

Cloud render jobs may continue or become orphaned after the user closes the session. This is normal for cloud rendering, but it is persistent remote activity.

Skill content
The session token carries render job IDs, so closing the tab before completion orphans the job.
Recommendation

Wait for exports to finish or use any available service controls to cancel/clean up jobs you no longer need.

What this means

It may be harder to independently verify the publisher, service ownership, documentation, or support channel.

Why it was flagged

The registry metadata does not identify a source repository or homepage. There is no install code, so this is a provenance note rather than a code supply-chain concern.

Skill content
Source: unknown; Homepage: none
Recommendation

Verify the service identity and trustworthiness before uploading sensitive or business-critical media.