Maker Free Browser
Analysis
This instruction-only cloud video editor is purpose-aligned, but it sends clips, prompts, and project state to NemoVideo's servers using a bearer token.
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.
The backend responds as if there's a visual interface. Map its instructions to API calls: - "click" or "点击" → execute the action via the relevant endpoint
Remote backend responses are explicitly allowed to drive subsequent API actions. This is aligned with the service workflow, but it makes backend-provided instructions influential over agent behavior.
All calls go to `https://mega-api-prod.nemovideo.ai`. The main endpoints: ... **Chat (SSE)** ... **Upload** ... **Credits** ... **State** ... **Export**
The skill directs the agent to call multiple remote APIs, including upload and export endpoints. The scope is bounded to the disclosed NemoVideo service and matches the video-creation purpose.
Source: unknown; Homepage: none
There are no packages or install scripts, but the registry metadata does not provide a source repository or homepage for provenance review.
The session token carries render job IDs, so closing the tab before completion orphans the job.
The artifact identifies a containment issue where an in-progress remote render can become untracked if the session is interrupted.
this is your NEMO_TOKEN (100 free credits, 7-day expiry)
The skill is branded as free, while the instructions disclose a credit-based anonymous token with an expiry. The limitation is disclosed, but users should not assume unlimited free use.
Checks whether tool use, credentials, dependencies, identity, account access, or inter-agent boundaries are broader than the stated purpose.
Include `Authorization: Bearer <NEMO_TOKEN>` and all attribution headers on every request
The skill uses a bearer token for all NemoVideo API operations. This is declared and purpose-aligned, but the token authorizes account/session actions and credit use.
Checks for exposed credentials, poisoned memory or context, unclear communication boundaries, or sensitive data that could leave the user's control.
**State** — `GET /api/state/nemo_agent/me/<sid>/latest` — current draft and media info
The skill retrieves and relies on remote session state containing project drafts and media information. This is expected for editing, but it means session context persists and can influence later actions in that project.
**Upload** — `POST /api/upload-video/nemo_agent/me/<sid>` — multipart file or JSON with URLs.
The workflow transmits user media or media URLs to an external provider endpoint. The endpoint is disclosed and purpose-aligned, but it crosses a local-to-cloud data boundary.
