Linkedin Video Maker
Analysis
This skill is a cloud video-rendering helper that clearly uses an external service and token, with no evidence of hidden code or malicious behavior.
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.
Backend says | You do ... "click [button]" / "点击" | Execute via API ... "Export button" / "导出" | Execute export workflow
The skill lets backend messages influence the agent's next API action. This is disclosed and tied to the video workflow, but users should know remote backend responses can steer workflow actions.
Upload: POST `/api/upload-video/nemo_agent/me/<sid>` — file: multipart `-F "files=@/path"`, or URL: `{"urls":["<url>"],"source_type":"url"}`The skill supports uploading local files or URLs to an external backend. This is necessary for video creation, but it is still a sensitive tool capability involving user media.
Source: unknown; Homepage: none
The skill has no install-time code, but its registry provenance is limited and it depends on an external backend service.
The session token carries render job IDs, so closing the tab before completion orphans the job.
Cloud render jobs may continue independently of the user's active tab. This is disclosed and expected for rendering, but users should understand that queued processing may continue after they leave.
Checks whether tool use, credentials, dependencies, identity, account access, or inter-agent boundaries are broader than the stated purpose.
Every API call needs `Authorization: Bearer <NEMO_TOKEN>`
The skill requires a bearer token for the cloud API. This credential use is expected for the stated service and the instructions say not to display token values.
Checks for exposed credentials, poisoned memory or context, unclear communication boundaries, or sensitive data that could leave the user's control.
Store the returned `session_id` for all subsequent requests.
The skill maintains backend session context across requests. This is expected for a multi-step video project, but it means project state is reused during the workflow.
Send message (SSE): POST `/run_sse` — body `{"app_name":"nemo_agent","user_id":"me","session_id":"<sid>"...}` with `Accept: text/event-stream`.The skill communicates with a remote `nemo_agent` backend over SSE. This is central to the service, but it is an agent/provider communication path that carries user prompts and session identifiers.
