Skill flagged — suspicious patterns detected

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

Video Editor Iphone

v1.0.0

Skip the learning curve of professional editing software. Describe what you want — trim the shaky parts, add transitions, and export in portrait mode — and g...

0· 61·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 susan4731-wilfordf/video-editor-iphone.

Previewing Install & Setup.
Prompt PreviewInstall & Setup
Install the skill "Video Editor Iphone" (susan4731-wilfordf/video-editor-iphone) from ClawHub.
Skill page: https://clawhub.ai/susan4731-wilfordf/video-editor-iphone
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 video-editor-iphone

ClawHub CLI

Package manager switcher

npx clawhub@latest install video-editor-iphone
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Suspicious
medium confidence
Purpose & Capability
The skill is an instruction-only cloud video editor and asks for a single API credential (NEMO_TOKEN), which is consistent with calling an external rendering API. However, the SKILL.md metadata references a config path (~/.config/nemovideo/) and platform detection based on install paths (~/.clawhub/, ~/.cursor/skills/) even though the registry lists no required config paths; this mismatch suggests the skill expects to inspect local filesystem/install-paths, which is not clearly justified by the stated purpose.
!
Instruction Scope
Runtime instructions include creating anonymous tokens, POSTing video uploads, long-polling SSE endpoints, and saving a session_id. They also require constructing custom headers including X-Skill-Platform by detecting install paths on the host. The instructions do not specify where session_id or anonymous tokens are stored and imply the agent may examine install/config paths; reading those paths is out of scope for a pure cloud uploader and is not clearly justified.
Install Mechanism
No install script or code is provided (instruction-only), so nothing is written to disk by an installer. That minimizes supply-chain risk.
Credentials
The only declared credential is NEMO_TOKEN (primaryEnv), which is proportionate for an API-backed editor. The skill also describes generating an anonymous token if none is present. Concern: SKILL.md metadata lists a config path (~/.config/nemovideo/) and implies inspecting install directories, but those paths were not declared in the registry's required config paths — this is an unexplained discrepancy.
Persistence & Privilege
The skill is not force-installed (always:false) and does not request system-wide privileges. It instructs the agent to 'save session_id' but does not define where; if the agent wrote tokens or session IDs to disk, that would increase persistence but the spec gives no explicit write instructions. Autonomous invocation is allowed (platform default) but not by itself a concern.
What to consider before installing
This skill mostly behaves like a cloud video editing connector, but before installing or using it you should: 1) Confirm whether the agent will read your home/config directories or detect install paths — ask the author why X-Skill-Platform requires scanning ~/.clawhub/ or similar. 2) Verify where session tokens (NEMO_TOKEN or anonymous tokens) and session_id will be stored (in memory vs. on disk) and for how long. 3) Ensure you trust the endpoint (https://mega-api-prod.nemovideo.ai) before uploading private videos. 4) If you don't want the agent to inspect your filesystem, refuse granting access to config/installation paths and require the author to remove that requirement. These clarifications would reduce the remaining ambiguity and could change the assessment to benign.

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

Runtime requirements

📱 Clawdis
EnvNEMO_TOKEN
Primary envNEMO_TOKEN
latestvk978n9gm76xk33xv36ssnpdhr584st6t
61downloads
0stars
1versions
Updated 2w ago
v1.0.0
MIT-0

Getting Started

Share your iPhone video clips and I'll get started on AI video editing. Or just tell me what you're thinking.

Try saying:

  • "edit my iPhone video clips"
  • "export 1080p MP4"
  • "trim the shaky parts, add transitions,"

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.

Video Editor iPhone — Edit iPhone Clips and Export

Drop your iPhone video clips in the chat and tell me what you need. I'll handle the AI video editing on cloud GPUs — you don't need anything installed locally.

Here's a typical use: you send a a 60-second iPhone camera recording, ask for trim the shaky parts, add transitions, and export in portrait mode, and about 30-60 seconds later you've got a MP4 file ready to download. The whole thing runs at 1080p by default.

One thing worth knowing — iPhone MOV files upload directly — no conversion needed before editing.

Matching Input to Actions

User prompts referencing video editor iphone, 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.

Headers are derived from this file's YAML frontmatter. X-Skill-Source is video-editor-iphone, 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).

All requests must include: Authorization: Bearer <NEMO_TOKEN>, X-Skill-Source, X-Skill-Version, X-Skill-Platform. Missing attribution headers will cause export to fail with 402.

API base: https://mega-api-prod.nemovideo.ai

Create session: POST /api/tasks/me/with-session/nemo_agent — body {"task_name":"project","language":"<lang>"} — returns task_id, session_id.

Send message (SSE): POST /run_sse — body {"app_name":"nemo_agent","user_id":"me","session_id":"<sid>","new_message":{"parts":[{"text":"<msg>"}]}} with Accept: text/event-stream. Max timeout: 15 minutes.

Upload: POST /api/upload-video/nemo_agent/me/<sid> — file: multipart -F "files=@/path", or URL: {"urls":["<url>"],"source_type":"url"}

Credits: GET /api/credits/balance/simple — returns available, frozen, total

Session state: GET /api/state/nemo_agent/me/<sid>/latest — key fields: data.state.draft, data.state.video_infos, data.state.generated_media

Export (free, no credits): POST /api/render/proxy/lambda — body {"id":"render_<ts>","sessionId":"<sid>","draft":<json>,"output":{"format":"mp4","quality":"high"}}. Poll GET /api/render/proxy/lambda/<id> every 30s until status = completed. Download URL at output.url.

Supported formats: mp4, mov, avi, webm, mkv, jpg, png, gif, webp, mp3, wav, m4a, aac.

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 JSON uses short keys: t for tracks, tt for track type (0=video, 1=audio, 7=text), sg for segments, d for duration in ms, m for metadata.

Example timeline summary:

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

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

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "trim the shaky parts, add transitions, and export in portrait mode" — concrete instructions get better results.

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

Export as MP4 for widest compatibility across iOS and Android devices.

Common Workflows

Quick edit: Upload → "trim the shaky parts, add transitions, and export in portrait mode" → 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.

Comments

Loading comments...