Skill flagged — suspicious patterns detected

ClawHub Security flagged this skill as suspicious. Review the scan results before using.

Trimmer Editor

v1.0.0

Get trimmed edited clips ready to post, without touching a single slider. Upload your raw video footage (MP4, MOV, AVI, WebM, up to 500MB), say something lik...

0· 69·0 current·0 all-time

Install

OpenClaw Prompt Flow

Install with OpenClaw

Best for remote or guided setup. Copy the exact prompt, then paste it into OpenClaw for tk8544-b/trimmer-editor.

Previewing Install & Setup.
Prompt PreviewInstall & Setup
Install the skill "Trimmer Editor" (tk8544-b/trimmer-editor) from ClawHub.
Skill page: https://clawhub.ai/tk8544-b/trimmer-editor
Keep the work scoped to this skill only.
After install, inspect the skill metadata and help me finish setup.
Required env vars: NEMO_TOKEN
Use only the metadata you can verify from ClawHub; do not invent missing requirements.
Ask before making any broader environment changes.

Command Line

CLI Commands

Use the direct CLI path if you want to install manually and keep every step visible.

OpenClaw CLI

Bare skill slug

openclaw skills install trimmer-editor

ClawHub CLI

Package manager switcher

npx clawhub@latest install trimmer-editor
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Suspicious
medium confidence
Purpose & Capability
The declared primary credential (NEMO_TOKEN) and endpoints match a cloud video trimming/rendering service, which is coherent with the skill's description. However, the skill has no public homepage or known source, which reduces trust and makes it harder to validate why certain metadata (config path ~/.config/nemovideo/) is declared.
Instruction Scope
SKILL.md stays within trimming/export scope: it instructs obtaining/using a token (or generating an anonymous one), creating a session, uploading video, streaming edits via SSE, checking credits, and starting renders. It does not instruct reading unrelated system files or environment variables beyond NEMO_TOKEN. It does instruct including attribution headers (derived from install path) which could leak local path information.
Install Mechanism
Instruction-only skill with no install spec and no code files — minimal install risk. Nothing is downloaded or written by an installer step in the package itself.
Credentials
Only NEMO_TOKEN is required as an env var and is appropriate for a cloud-rendering API. The metadata also declares a config path (~/.config/nemovideo/) which is plausible for storing credentials/session state but should be verified since the SKILL.md does not explicitly describe reading that path.
Persistence & Privilege
It does not request 'always: true' or system-wide changes; it asks to store session_id for job tracking (normal for stateful APIs). No indications the skill will modify other skills or agent-wide configs.
What to consider before installing
Before installing or using this skill: 1) Verify the backend (mega-api-prod.nemovideo.ai) and owner — there is no homepage or official source listed. 2) Do not upload sensitive/personal videos until you confirm privacy, retention, and billing policies; anonymous tokens grant cloud storage/processing access for 7 days. 3) Be aware the skill will send an Authorization Bearer token and additional headers on every request; the header that derives from your install path may reveal local path info. 4) If you proceed, test with non-sensitive short clips first, monitor requests, and revoke any generated tokens after use. 5) If you need higher assurance, ask the publisher for a privacy policy, source repository, or official documentation before trusting real content.

Like a lobster shell, security has layers — review code before you run it.

Runtime requirements

✂️ Clawdis
EnvNEMO_TOKEN
Primary envNEMO_TOKEN
latestvk97eryjgf3vbvw36k4cf9608ed852y47
69downloads
0stars
1versions
Updated 1w ago
v1.0.0
MIT-0

Getting Started

Ready when you are. Drop your raw video footage here or describe what you want to make.

Try saying:

  • "trim a 10-minute interview recording with long pauses into a 1080p MP4"
  • "trim the silences and cut the clip down to 3 minutes"
  • "cutting and trimming long videos into shorter polished clips for content creators"

Automatic Setup

On first interaction, connect to the processing API before doing anything else. Show a brief status like "Setting things up...".

Token: If NEMO_TOKEN environment variable is already set, use it and skip to Session below.

Free token: Generate a UUID as client identifier, then POST to https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with header X-Client-Id: <uuid>. The response field data.token becomes your NEMO_TOKEN (100 credits, 7-day expiry).

Session: POST to https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Bearer auth and body {"task_name":"project"}. Save session_id from the response.

Confirm to the user you're connected and ready. Don't print tokens or raw JSON.

Trimmer Editor — Trim and Export Clean Clips

This tool takes your raw video footage and runs AI trim editing through a cloud rendering pipeline. You upload, describe what you want, and download the result.

Say you have a 10-minute interview recording with long pauses and want to trim the silences and cut the clip down to 3 minutes — the backend processes it in about 30-60 seconds and hands you a 1080p MP4.

Tip: splitting into smaller segments before uploading speeds up processing.

Matching Input to Actions

User prompts referencing trimmer editor, aspect ratio, text overlays, or audio tracks get routed to the corresponding action via keyword and intent classification.

User says...ActionSkip SSE?
"export" / "导出" / "download" / "send me the video"→ §3.5 Export
"credits" / "积分" / "balance" / "余额"→ §3.3 Credits
"status" / "状态" / "show tracks"→ §3.4 State
"upload" / "上传" / user sends file→ §3.2 Upload
Everything else (generate, edit, add BGM…)→ §3.1 SSE

Cloud Render Pipeline Details

Each export job queues on a cloud GPU node that composites video layers, applies platform-spec compression (H.264, up to 1080x1920), and returns a download URL within 30-90 seconds. The session token carries render job IDs, so closing the tab before completion orphans the job.

Base URL: https://mega-api-prod.nemovideo.ai

EndpointMethodPurpose
/api/tasks/me/with-session/nemo_agentPOSTStart a new editing session. Body: {"task_name":"project","language":"<lang>"}. Returns session_id.
/run_ssePOSTSend a user message. Body includes app_name, session_id, new_message. Stream response with Accept: text/event-stream. Timeout: 15 min.
/api/upload-video/nemo_agent/me/<sid>POSTUpload a file (multipart) or URL.
/api/credits/balance/simpleGETCheck remaining credits (available, frozen, total).
/api/state/nemo_agent/me/<sid>/latestGETFetch current timeline state (draft, video_infos, generated_media).
/api/render/proxy/lambdaPOSTStart export. Body: {"id":"render_<ts>","sessionId":"<sid>","draft":<json>,"output":{"format":"mp4","quality":"high"}}. Poll status every 30s.

Accepted file types: mp4, mov, avi, webm, mkv, jpg, png, gif, webp, mp3, wav, m4a, aac.

Headers are derived from this file's YAML frontmatter. X-Skill-Source is trimmer-editor, X-Skill-Version comes from the version field, and X-Skill-Platform is detected from the install path (~/.clawhub/ = clawhub, ~/.cursor/skills/ = cursor, otherwise unknown).

Include Authorization: Bearer <NEMO_TOKEN> and all attribution headers on every request — omitting them triggers a 402 on export.

Error Handling

CodeMeaningAction
0SuccessContinue
1001Bad/expired tokenRe-auth via anonymous-token (tokens expire after 7 days)
1002Session not foundNew session §3.0
2001No creditsAnonymous: show registration URL with ?bind=<id> (get <id> from create-session or state response when needed). Registered: "Top up credits in your account"
4001Unsupported fileShow supported formats
4002File too largeSuggest compress/trim
400Missing X-Client-IdGenerate Client-Id and retry (see §1)
402Free plan export blockedSubscription tier issue, NOT credits. "Register or upgrade your plan to unlock export."
429Rate limit (1 token/client/7 days)Retry in 30s once

SSE Event Handling

EventAction
Text responseApply GUI translation (§4), present to user
Tool call/resultProcess internally, don't forward
heartbeat / empty data:Keep waiting. Every 2 min: "⏳ Still working..."
Stream closesProcess final response

~30% of editing operations return no text in the SSE stream. When this happens: poll session state to verify the edit was applied, then summarize changes to the user.

Backend Response Translation

The backend assumes a GUI exists. Translate these into API actions:

Backend saysYou do
"click [button]" / "点击"Execute via API
"open [panel]" / "打开"Query session state
"drag/drop" / "拖拽"Send edit via SSE
"preview in timeline"Show track summary
"Export button" / "导出"Execute export workflow

Draft field mapping: t=tracks, tt=track type (0=video, 1=audio, 7=text), sg=segments, d=duration(ms), m=metadata.

Timeline (3 tracks): 1. Video: city timelapse (0-10s) 2. BGM: Lo-fi (0-10s, 35%) 3. Title: "Urban Dreams" (0-3s)

Common Workflows

Quick edit: Upload → "trim the silences and cut the clip down to 3 minutes" → Download MP4. Takes 30-60 seconds for a 30-second clip.

Batch style: Upload multiple files in one session. Process them one by one with different instructions. Each gets its own render.

Iterative: Start with a rough cut, preview the result, then refine. The session keeps your timeline state so you can keep tweaking.

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "trim the silences and cut the clip down to 3 minutes" — concrete instructions get better results.

Max file size is 500MB. Stick to MP4, MOV, AVI, WebM for the smoothest experience.

Export as MP4 for widest compatibility.

Comments

Loading comments...