Hire Youtube Video
PassAudited by ClawScan on May 11, 2026.
Overview
This appears to be a normal cloud video-editing skill, but it sends selected media to NemoVideo and uses or creates a token/session that may consume credits.
Install only if you are comfortable using NemoVideo's cloud service. Do not upload private or sensitive footage unless you trust the provider's privacy practices, keep NEMO_TOKEN secret, and confirm exports if you are concerned about credit usage.
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.
Using the skill can automatically create a cloud session and perform editing/export workflow calls for the video task.
The agent is instructed to make provider API calls automatically as part of setup and to convert backend UI-style responses into API actions. This is purpose-aligned for a cloud editor, but users should know actions can be taken within the remote video session.
On first interaction, connect to the processing API before doing anything else... Backend says "click [button]" / "点击" | Execute via API
Use it only when you intend to use the NemoVideo cloud workflow, and ask the agent to confirm before exporting if credits or final output matter.
The token may allow access to the user's NemoVideo session and credits for rendering/exporting.
The skill uses a bearer token or creates an anonymous token for the NemoVideo service. This is expected for the provider integration, but the token authorizes sessions and credit-backed operations.
If `NEMO_TOKEN` environment variable is already set, use it... Free token: Generate a UUID... response field `data.token` becomes your NEMO_TOKEN... All requests must include: `Authorization: Bearer <NEMO_TOKEN>`
Keep NEMO_TOKEN private, prefer a scoped or disposable token if available, and monitor provider credit usage.
Uploaded videos, images, audio, or media URLs may leave the local machine and be processed by NemoVideo's servers.
The skill sends user-selected media or URLs to a third-party cloud service for processing. The destination is disclosed and purpose-aligned, but retention and privacy details are not described in the provided artifacts.
All rendering happens server-side... Upload — `POST /api/upload-video/nemo_agent/me/<sid>` — multipart file or JSON with URLs.
Only upload footage you are comfortable sending to that provider, and check the provider's privacy and retention terms for sensitive content.
Users have less provenance information before trusting the skill with media uploads and provider tokens.
The registry metadata does not provide a source repository or homepage, making it harder to independently verify who maintains the skill or its relationship to the remote API.
Source: unknown; Homepage: none
Verify the NemoVideo domain and service legitimacy before using the skill with valuable or private footage.