Video Editing In Ai Free
Analysis
This is an instruction-only cloud video editing skill; the main thing to understand is that your videos and prompts are sent to NemoVideo using a token, and free-tier limits may apply.
Findings (8)
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.
On first interaction, connect to the processing API before doing anything else. Show a brief status like "Setting things up...".
This directs the agent to initiate provider setup as the first action when the skill is used. It is aligned with the cloud-editing purpose, but it can cause an automatic network/session action before detailed user discussion.
`/api/upload-video/nemo_agent/me/<sid>` | POST | Upload a file (multipart) or URL. ... `/api/render/proxy/lambda` | POST | Start export.
The skill gives the agent provider API actions that can upload media and start cloud render jobs. These actions are central to the stated purpose, but they can move user files off-device and consume service credits.
Source: unknown; Homepage: none
The provided metadata does not identify an official source or homepage for the skill. There is no installable code here, but provenance is still relevant because the skill relies on a third-party cloud video service.
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 requests can create remote render jobs that continue outside the immediate chat flow. This is normal for cloud rendering, but a mistaken upload/export can propagate into a queued job or credit usage.
displayName: "Video Editing in AI Free — Edit and Export Videos Free" ... `402` | Free plan export blocked | ... "Register or upgrade your plan to unlock export."
The skill marketing emphasizes free editing/export, while the instructions also disclose credits, expiry, and possible upgrade requirements. This is not hidden, but users should understand the free tier may have limits.
Checks whether tool use, credentials, dependencies, identity, account access, or inter-agent boundaries are broader than the stated purpose.
`requires`: {"env": ["NEMO_TOKEN"]} ... All requests must include: `Authorization: Bearer <NEMO_TOKEN>`The skill requires a service token and uses it as Bearer authentication for all provider requests. This is expected for the NemoVideo integration and there is no artifact evidence of unrelated credential use.
Checks for exposed credentials, poisoned memory or context, unclear communication boundaries, or sensitive data that could leave the user's control.
Save `session_id` from the response. ... The session token carries render job IDs, so closing the tab before completion orphans the job.
The workflow depends on server-side session state and render job identifiers. This is expected for cloud editing, but session state can persist beyond a single message and should be treated as sensitive workflow context.
This tool takes your raw video footage and runs AI video editing through a cloud rendering pipeline. You upload, describe what you want, and download the result.
The skill communicates with an external provider API and sends user media and editing prompts to that provider. The cloud flow is disclosed and purpose-aligned, but it is still a sensitive data transfer.
