Trimmer Mp3
Analysis
This looks like a legitimate cloud-based audio/video trimming connector, but it sends user files and prompts to NemoVideo and uses a service 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.
/api/upload-video/nemo_agent/me/<sid> | POST | Upload a file (multipart) or URL. ... /api/render/proxy/lambda | POST | Start export.
The skill can upload user media and start cloud render/export jobs. These actions are central to the stated trimming/export purpose, but they are externally hosted operations.
Source: unknown; Homepage: none
The registry metadata does not provide source or homepage provenance. There is no local install code, but the user must trust the hosted backend and skill publisher.
The session token carries render job IDs, so closing the tab before completion orphans the job.
The artifact explicitly notes that cloud render jobs can become orphaned if the user leaves before completion, which could consume time or credits without a visible local session.
Tell the user you're ready. Keep the technical details out of the chat.
The skill asks the agent not to show backend connection details in chat. This can be a normal UX choice, but users should still understand the service is connecting to a third-party backend.
closing the tab before completion orphans the job
A render job may continue on the backend after the user closes the tab. This is disclosed and tied to user-initiated rendering, not evidence of self-propagation or hidden autonomous behavior.
Checks whether tool use, credentials, dependencies, identity, account access, or inter-agent boundaries are broader than the stated purpose.
All requests must include: Authorization: Bearer <NEMO_TOKEN>
The skill uses a bearer token for the NemoVideo API. This is expected for the integrated service and no artifact evidence shows unrelated credential use.
Checks for exposed credentials, poisoned memory or context, unclear communication boundaries, or sensitive data that could leave the user's control.
The session_id in the response is needed for all following requests.
The backend session links later upload, edit, state, and render operations. This is expected for a media-editing workflow but means task context is maintained remotely.
/run_sse | POST | Send a user message. Body includes app_name, session_id, new_message. Stream response with Accept: text/event-stream.
User messages are sent to an external backend over an SSE workflow. This is disclosed and aligned with the cloud-editing purpose, but it is a third-party communication boundary.
