Ai Batch Video
PassAudited by ClawScan on May 11, 2026.
Overview
This is a coherent cloud video-processing skill, but it uses a NemoVideo token/session and uploads selected media to a remote rendering API.
Before installing or using this skill, be comfortable sending the selected videos to NemoVideo's cloud API and using a NEMO_TOKEN or anonymous service token. Confirm which files will be uploaded and what export action will be run, especially for confidential product demos or customer media.
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.
Ambiguous requests could result in API calls, uploads, or exports in the current rendering session.
The skill directs the agent to drive a remote API workflow for upload, editing, export, and polling. This is central to the video-processing purpose, but it is still meaningful automation of external service actions.
Before handling any user request, establish a connection to the backend API... Upload: POST `/api/upload-video/nemo_agent/me/<sid>`... Export... Poll GET `/api/render/proxy/lambda/<id>` every 30s
Confirm the clips, edits, and export settings before allowing upload or export, especially for private media or credit-consuming operations.
The skill can act against the NemoVideo backend using the available token or a newly issued anonymous token.
The skill uses a bearer token or obtains an anonymous service token to create sessions and call the NemoVideo API. This is expected for the stated integration, but it grants service-level authority for rendering actions.
If `NEMO_TOKEN` is in the environment, use it directly... Otherwise, acquire a free starter token... All requests must include: `Authorization: Bearer <NEMO_TOKEN>`
Use a service-specific token with the minimum needed access, avoid sharing broader account credentials, and revoke or rotate the token if it is no longer needed.
Uploaded videos and generated outputs may be processed and temporarily stored by the external rendering provider.
User-selected video files or URLs are sent to the remote NemoVideo API. The destination and purpose are disclosed and aligned with cloud rendering, but the media may contain private or business-sensitive content.
This tool takes your multiple video clips and runs AI batch processing through a cloud rendering pipeline. You upload... Upload: POST `/api/upload-video/nemo_agent/me/<sid>` — file: multipart `-F "files=@/path"`
Only upload media you intend to send to NemoVideo, and review the provider's privacy, retention, and sharing terms for sensitive content.
You may not see details about backend session creation or token use in normal chat responses.
This appears to be UX guidance, but it could make token creation, session setup, and backend API details less visible to the user unless they ask. The broader artifact does disclose cloud rendering and API use.
Tell the user you're ready. Keep the technical details out of the chat.
Ask the agent to explain what service it is connecting to, what files it will upload, and what token it will use before starting sensitive jobs.