With Music
Analysis
This skill is a cloud video-music editor that appears coherent, but users should expect their media to be uploaded to NemoVideo and processed through remote API sessions.
Findings (8)
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.
"Backend says" ... "click [button]" ... "Execute via API" ... "Export button" ... "Execute export workflow"
Backend text is treated as operational instruction for API actions, so the remote service can influence the agent's workflow inside the editing session.
"/api/upload-video/nemo_agent/me/<sid>" ... "Upload a file"; "/api/render/proxy/lambda" ... "Start export"
The skill exposes upload, state, SSE, credit, and render API operations. These are aligned with video editing but can mutate a cloud session and consume service resources.
Source: unknown; Homepage: none
The registry metadata provides limited provenance for the skill publisher/source, although no install scripts or code dependencies are present.
The session token carries render job IDs, so closing the tab before completion orphans the job.
Cloud render jobs can outlive the active interaction if the session is interrupted, which may leave work in progress without local control.
On first use, set up the connection automatically and let the user know ("Connecting...").The skill performs automatic token/session setup with brief user-facing messaging. This is aligned with onboarding, but users should notice that a remote account/session is being created.
Checks whether tool use, credentials, dependencies, identity, account access, or inter-agent boundaries are broader than the stated purpose.
"Token check": Look for `NEMO_TOKEN` ... POST `https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token` ... Extract `data.token`
The skill requires or obtains a NemoVideo bearer token. This is expected for the service and no artifact shows hardcoded, leaked, or unrelated credentials.
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; `/api/state/nemo_agent/me/<sid>/latest` ... Fetch current timeline state
The workflow relies on remote session state and timeline state, which can persist context about the user's media and edits during the task.
`/run_sse` ... "Send a user message" ... "Stream response"; "Tool call/result" ... "Process internally, don't forward"
The skill communicates with a remote agent-like backend over SSE and processes tool-call events internally. The endpoint is disclosed and purpose-aligned, but this is still a sensitive provider communication path.
