Add Text To Video
PassAudited by ClawScan on May 10, 2026.
Overview
This is a cloud video-editing skill that openly uses a Nemo token and uploads user-selected videos for remote processing; no hidden or malicious behavior is supported by the provided artifacts.
Before installing, make sure you are comfortable sending selected videos and editing prompts to the Nemo cloud service. Protect the NEMO_TOKEN like a password and review uploads/exports for private or proprietary content.
Findings (4)
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.
The cloud video editor can guide edit/export actions inside the current project session.
The skill converts backend GUI-style responses into concrete API actions. This is aligned with the video-editing purpose, but it is still tool orchestration driven by remote workflow messages.
"click" or "点击" → execute the action via the relevant endpoint ... "Export" or "导出" → run the export workflow
Use it for intended video-editing tasks and review what file is uploaded and what export is requested before relying on the result.
Anyone with the token may be able to access the associated Nemo service session or credits.
The skill requires a service credential for Nemo API access. This is expected for the cloud backend and is disclosed, with an instruction not to expose tokens.
All requests must include: `Authorization: Bearer <NEMO_TOKEN>`
Keep NEMO_TOKEN private, use only the intended token, and rotate or remove it if you stop using the service.
Your video files, prompts, and project state may be sent to and processed by the Nemo cloud service.
The skill communicates with a remote Nemo agent/backend and uploads user-selected videos or URLs for processing. The destination is disclosed and purpose-aligned.
Send message (SSE): POST `/run_sse` ... `app_name":"nemo_agent` ... Upload: POST `/api/upload-video/nemo_agent/me/<sid>`
Only upload media you are comfortable sending to the provider, especially if it contains private, proprietary, or personal content.
A cloud render job may remain unfinished or detached if you close the session early.
Render jobs may continue or remain on the provider side after the user interface closes. The behavior is disclosed and scoped to the render job.
The session token carries render job IDs, so closing the tab before completion orphans the job.
Wait for exports to finish when possible, and check the provider/session state if a job appears stuck or abandoned.