Video Editing Ai Tool Free
Analysis
This instruction-only cloud video-editing skill is coherent, but it will use a NEMO token, upload media and prompts to a cloud backend, and may be limited by credits or plan restrictions.
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.
“On first use, set up the connection automatically” ... “/api/upload-video/nemo_agent/me/<sid>” ... “/api/render/proxy/lambda”
The skill directs the agent to create a cloud session, upload media, and start exports through NEMO APIs. These are purpose-aligned for video editing, but they are real remote actions that can process files and consume service credits.
“Source: unknown” ... “Homepage: none”
There is no local install or helper code, but the package provenance information is sparse while the skill depends on a specific cloud service. This is a user-verification point rather than evidence of malicious supply-chain behavior.
“Video Editing AI Tool Free” ... “100 free credits, 7-day expiry” ... “Free plan export blocked” ... “Register or upgrade your plan to unlock export.”
The skill is marketed as free, while its own instructions disclose credit expiry and possible upgrade requirements for export. The limitation is disclosed, but users should not assume unlimited free exports.
“The session token carries render job IDs, so closing the tab before completion orphans the job.”
Cloud render jobs may continue or become orphaned after the user leaves the tab. This is disclosed and tied to the intended render workflow, not evidence of self-propagation or hidden autonomous behavior.
Checks whether tool use, credentials, dependencies, identity, account access, or inter-agent boundaries are broader than the stated purpose.
“Look for `NEMO_TOKEN` in the environment” ... “Extract `data.token` from the response — this is your NEMO_TOKEN” ... “Authorization: Bearer <NEMO_TOKEN>”
The skill uses a bearer token for the integrated NEMO cloud service. This is expected for the stated backend workflow, and the artifacts do not show token logging or unrelated credential use.
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” ... “Fetch current timeline state (`draft`, `video_infos`, `generated_media`).”
The workflow reuses a session_id and retrieves cloud timeline state. This is purpose-aligned for editing continuity, but session state can carry prior draft/media context into later operations.
“`/run_sse` | POST | Send a user message” ... “`/api/upload-video/nemo_agent/me/<sid>` | POST | Upload a file” ... “All requests must include ... `X-Skill-Platform`.”
The skill sends user prompts, media files, and attribution headers to a fixed external provider endpoint. This is disclosed and aligned with cloud editing, but it is still a sensitive data flow.