Brand Video Maker Free
Analysis
This skill appears purpose-aligned for making videos, but it sends your images, text, and render jobs to a NemoVideo cloud service using a service token.
Findings (7)
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.
Checks for instructions or behavior that redirect the agent, misuse tools, execute unexpected code, cascade across systems, exploit user trust, or continue outside the intended task.
The backend responds as if there's a visual interface. Map its instructions to API calls: - "click" or "点击" → execute the action via the relevant endpoint
Remote backend text can influence the agent to perform follow-up API actions. This is purpose-aligned for the service workflow, but users should know backend responses are treated as operational instructions.
Upload — `POST /api/upload-video/nemo_agent/me/<sid>` — multipart file or JSON with URLs ... Export — `POST /api/render/proxy/lambda` with render ID and draft JSON.
The skill can upload media and start export/render operations through external APIs. These actions are central to the video-making purpose, but they affect user media and service credits.
Source: unknown Homepage: none
The skill has limited provenance metadata. There are no install dependencies or code files, but users are still relying on the authored instructions and the external cloud backend.
Each export job queues on a cloud GPU node ... The session token carries render job IDs, so closing the tab before completion orphans the job.
Export jobs can continue remotely and become hard to track if the session is interrupted. This is disclosed and tied to rendering, but users should notice the remote-job behavior.
Checks whether tool use, credentials, dependencies, identity, account access, or inter-agent boundaries are broader than the stated purpose.
Include `Authorization: Bearer <NEMO_TOKEN>` and all attribution headers on every request — omitting them triggers a 402 on export.
The skill requires a bearer token for the NemoVideo service. This is expected for the cloud integration, but the token authorizes session and render activity.
Checks for exposed credentials, poisoned memory or context, unclear communication boundaries, or sensitive data that could leave the user's control.
Keep the returned `session_id` for all operations. ... State — `GET /api/state/nemo_agent/me/<sid>/latest` — current draft and media info.
The skill relies on remote session state containing draft and media information. This is necessary for editing continuity, but that state can influence later actions in the same project.
All calls go to `https://mega-api-prod.nemovideo.ai`. ... Chat (SSE) — `POST /run_sse` ... Upload — `POST /api/upload-video/nemo_agent/me/<sid>`
Prompts, media uploads, chat messages, and render state are sent to an external provider over documented endpoints. This is disclosed and purpose-aligned, but it crosses a data boundary.
