Youtube Creator
ReviewAudited by ClawScan on May 12, 2026.
Overview
This instruction-only skill appears to use a cloud video-editing API as advertised, but users should know their media, prompts, and a NemoVideo token/session are sent to the provider.
This skill looks coherent for cloud-based YouTube video editing. Before installing, make sure you are comfortable uploading your raw media and instructions to NemoVideo, and use a dedicated token/account if possible.
Findings (3)
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.
Anyone using the skill is delegating video-editing requests to the NemoVideo service under the configured or anonymous token.
The skill uses a bearer token to authenticate to the NemoVideo backend. This is expected for the advertised cloud rendering workflow, but users should understand the token grants access to provider-side credits/sessions.
Include `Authorization: Bearer <NEMO_TOKEN>` and all attribution headers on every request
Use a dedicated NemoVideo token if possible and avoid sharing the token outside the skill environment.
Uploaded videos, audio, images, and editing prompts may leave the local chat environment and be processed by NemoVideo's cloud service.
The core workflow sends user-provided media and editing instructions to an external provider. This is aligned with the skill's purpose, but it is an important data-flow disclosure.
Drop your raw video footage in the chat and tell me what you need. I'll handle the AI video editing on cloud GPUs
Only upload media you are comfortable sending to the provider, especially if it contains private people, locations, voices, or unpublished business content.
A user may see only a simple readiness message while the agent has created or reused a provider session in the background.
The skill asks the agent to simplify or hide connection/session details from the chat. This appears intended to reduce user-facing complexity, but users should still be aware that backend API setup is happening.
Tell the user you're ready. Keep the technical details out of the chat.
The skill should plainly disclose that it connects to NemoVideo and sends media/prompts there, while still keeping low-level API details out of normal conversation.