Editor Not Generator
Analysis
This is a purpose-aligned cloud video editing skill, but it sends your media and prompts to NemoVideo and uses a token-based cloud session.
Findings (7)
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.
Checks for instructions or behavior that redirect the agent, misuse tools, execute unexpected code, cascade across systems, exploit user trust, or continue outside the intended task.
The backend responds as if there's a visual interface. Map its instructions to API calls: ... "click" or "点击" → execute the action via the relevant endpoin
The external backend's responses can be converted into follow-on API actions. This is disclosed and purpose-aligned for video editing, but it means provider text can steer the workflow.
| `/api/upload-video/nemo_agent/me/<sid>` | POST | Upload a file (multipart) or URL. | ... | `/api/render/proxy/lambda` | POST | Start export. |
The skill exposes cloud upload and render/export operations. These are central to the stated video editing purpose, but they can transfer user media and may affect service credits or subscription status.
Source: unknown; Homepage: none
The registry provenance fields do not identify a public source or homepage for a cloud-backed integration. This is not unsafe by itself, but it reduces how easily users can verify the provider and instructions.
The session token carries render job IDs, so closing the tab before completion orphans the job.
A cloud render job can continue or become orphaned after the user closes the tab. This is disclosed and tied to the export workflow, not hidden local persistence.
Checks whether tool use, credentials, dependencies, identity, account access, or inter-agent boundaries are broader than the stated purpose.
Look for `NEMO_TOKEN` in the environment... POST `https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token` ... Extract `data.token` from the response — this is your NEMO_TOKEN
The skill uses an environment token or provisions an anonymous service token for NemoVideo. This is expected for the cloud integration and no credential leakage or unrelated privilege use is shown.
Checks for exposed credentials, poisoned memory or context, unclear communication boundaries, or sensitive data that could leave the user's control.
Keep the returned `session_id` for all operations. ... Fetch current timeline state (`draft`, `video_infos`, `generated_media`).
The skill relies on a persistent cloud session and timeline state. This is necessary for iterative video editing, but session state and media-derived context can influence later operations.
`/run_sse` | POST | Send a user message. Body includes `app_name`, `session_id`, `new_message`. Stream response with `Accept: text/event-stream`.
User messages and session identifiers are sent to an external SSE backend. The endpoint and authentication are disclosed and purpose-aligned, but it is a third-party communication channel carrying user content.
