Video Editing Tools
PassAudited by ClawScan on May 10, 2026.
Overview
This is a coherent cloud video-editing skill, but users should know it contacts NemoVideo automatically and uploads selected media to a third-party processing service.
This skill appears benign and purpose-aligned for cloud video editing. Before installing, confirm you are comfortable sending selected videos, images, audio, and editing instructions to mega-api-prod.nemovideo.ai, and protect the NEMO_TOKEN like an account credential.
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.
The skill may contact the video-processing backend and create a session before a detailed editing request is made.
The skill performs an automatic remote setup call when first opened. This is purpose-aligned for a cloud editing backend, but users should be aware that opening/using the skill can initiate network activity.
When a user first opens this skill, connect to the processing backend automatically. Briefly let them know (e.g. "Setting up...").
Use the skill only if you are comfortable with first-use backend setup; operators should make this behavior visible in user-facing onboarding.
Anyone with the token could potentially use the associated NemoVideo access or credits until the token expires or is revoked.
The skill relies on a bearer token for NemoVideo API access. This is expected for the service integration, but the token can represent access to credits, sessions, and render jobs.
All requests must include: Authorization: Bearer <NEMO_TOKEN>
Keep NEMO_TOKEN private, avoid sharing logs that contain authorization headers, and rotate or revoke the token if it may have been exposed.
Uploaded videos, images, audio, and editing prompts may leave the local environment for third-party cloud processing.
The skill sends user-provided media and editing instructions to a named external cloud backend. This is core to the advertised functionality, but it affects privacy and data handling expectations.
Drop your video clips in the chat and tell me what you need. I'll handle the AI video editing on cloud GPUs
Only upload media you are allowed to send to the external provider, and avoid sensitive or confidential footage unless the provider’s privacy and retention terms are acceptable.
Users have less information for verifying who maintains the skill or reviewing external documentation before sending media to the backend.
The registry metadata does not provide a source repository or homepage, which limits independent verification of the skill/provider relationship. There is no install code here, so this is a provenance note rather than a concern.
Source: unknown; Homepage: none
Prefer skills with clear source and support links for sensitive workflows, or verify the provider and API endpoint before use.