Article To Video Ai
PassAudited by ClawScan on May 6, 2026.
Overview
This instruction-only skill is coherent for cloud article-to-video generation, but users should know it sends supplied content to an external NemoVideo API using a bearer token and remote session.
This skill appears safe to use for its intended purpose if you are comfortable sending article content to nemovideo.ai. Avoid uploading confidential documents unless you have verified the provider’s privacy terms, use a dedicated NEMO_TOKEN, and monitor remote render sessions until they complete.
Findings (5)
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.
Articles, files, URLs, and prompts may be processed by the NemoVideo backend, so confidential or regulated content could leave the local environment.
The skill clearly discloses that user-provided article content is sent to a cloud backend for processing, but the artifact does not describe retention or privacy boundaries.
This tool takes your written articles and runs AI video creation through a cloud rendering pipeline. You upload, describe what you want, and download the result.
Use only content you are comfortable sending to the provider, and check the provider’s privacy and retention terms before uploading sensitive documents.
The agent can act within the NemoVideo session associated with the token, including creating sessions, uploading inputs, checking credits, and exporting renders.
The skill uses a bearer token for the external service. This is expected for the integration and no artifact shows hardcoded, logged, or unrelated token use.
Include `Authorization: Bearer <NEMO_TOKEN>` and all attribution headers on every request
Use a dedicated token for this skill when possible and avoid sharing token values in chat or documents.
The provider backend may cause the agent to perform additional video-editing or export API steps inside the NemoVideo workflow.
The skill instructs the agent to translate backend GUI-style responses into API calls. This appears purpose-aligned, but it means remote backend responses can drive further service actions.
Backend says | You do ... "click [button]" / "点击" | Execute via API
Review the generated video state and export result, and do not treat backend messages as permission for actions outside the intended video project.
Users have less registry-provided information for verifying the publisher or support channel for this external API integration.
The registry metadata does not provide a source repository or homepage, limiting provenance review for the service integration, though no install code is present.
Source: unknown; Homepage: none
Install only if you trust the listed owner and the nemovideo.ai service, and prefer integrations with clear source or vendor documentation.
A render may keep running remotely or become difficult to recover if the session is interrupted.
Remote render jobs and session state can outlive the immediate chat interaction. This is expected for cloud rendering but should be visible to users.
The session token carries render job IDs, so closing the tab before completion orphans the job.
Let render jobs finish before closing the session, and clear or rotate the token if you no longer want the skill to access the service.