Video Trimmer Download For Pc
PassAudited by ClawScan on May 10, 2026.
Overview
This appears to be a purpose-aligned cloud video trimming skill, but users should know it sends selected media and prompts to NemoVideo and uses or creates a bearer token.
Before installing, be comfortable with cloud processing: upload only videos or audio you intend to share with NemoVideo, use a dedicated token if possible, and keep an eye on credits or subscription limits during exports.
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.
Your chosen videos, images, or audio can be uploaded to the provider and rendered in the cloud.
The skill directs the agent to upload user-selected media and start cloud render/export jobs. This is central to video trimming, but users should understand these actions happen against an external API and may affect credits or generated outputs.
`/api/upload-video/nemo_agent/me/<sid>` | POST | Upload a file ... `/api/render/proxy/lambda` | POST | Start export.
Only provide media you intend to process externally, and confirm exports or large jobs when credit usage matters.
The skill can act within the NemoVideo session/credit scope associated with the token it uses.
The skill uses a NemoVideo bearer token, or creates an anonymous token, to authenticate cloud editing requests. This is expected for the integration and the artifact says not to expose tokens.
Every API call needs `Authorization: Bearer <NEMO_TOKEN>` ... If found, skip to session creation. Otherwise ... POST ... `anonymous-token` ... Extract `data.token`.
Use a token intended for this service, avoid sharing it in chat, and revoke or rotate it if you no longer trust the skill.
Editing instructions and related session state may be processed by the remote service, not only locally.
The skill establishes a streaming provider workflow where user messages and backend responses drive editing actions. This is purpose-aligned, but it means prompts and workflow state are shared with the external backend.
`/run_sse` | POST | Send a user message ... Stream response ... Text events go straight to the user ... Tool calls stay internal.
Do not include private information in edit prompts unless you are comfortable sharing it with the provider.
It may be harder to verify who maintains the service or review its privacy/security practices before uploading media.
The registry does not provide a source repository or homepage. There is no local code install, but users still rely on an external backend whose provenance is not documented here.
Source: unknown; Homepage: none
Review the provider and avoid uploading sensitive recordings unless you trust the service.