Skill flagged — suspicious patterns detected

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

Video Editor For Beginners Mac

v1.0.0

Turn a 2-minute iPhone recording of a birthday party into 1080p polished edited clips just by typing what you need. Whether it's editing home or hobby videos...

0· 50·0 current·0 all-time
bypeandrover adam@peand-rover

Install

OpenClaw Prompt Flow

Install with OpenClaw

Best for remote or guided setup. Copy the exact prompt, then paste it into OpenClaw for peand-rover/video-editor-for-beginners-mac.

Previewing Install & Setup.
Prompt PreviewInstall & Setup
Install the skill "Video Editor For Beginners Mac" (peand-rover/video-editor-for-beginners-mac) from ClawHub.
Skill page: https://clawhub.ai/peand-rover/video-editor-for-beginners-mac
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-for-beginners-mac

ClawHub CLI

Package manager switcher

npx clawhub@latest install video-editor-for-beginners-mac
Security Scan
VirusTotalVirusTotal
Suspicious
View report →
OpenClawOpenClaw
Suspicious
medium confidence
Purpose & Capability
The name/description (cloud video editing) align with the runtime instructions (upload clips, remote rendering, download URL). Requested primary credential (NEMO_TOKEN) is appropriate for a remote rendering service. However, SKILL.md frontmatter declares a required config path (~/.config/nemovideo/) while the registry metadata lists no required config paths — this mismatch is unexplained and worth clarifying.
Instruction Scope
Instructions are scoped to creating/using an API token, creating a session, uploading files, streaming SSE, polling render status, and returning download URLs — all expected for a cloud editor. They instruct the agent to auto-generate an anonymous token if none is present and to 'store the returned session_id' without specifying storage boundaries. The document also requires detecting an install path/platform for an attribution header (X-Skill-Platform), which implies the agent may inspect its environment/install location. These behaviors are plausible but should be explicit (where tokens/session IDs are stored, what local paths are read).
Install Mechanism
Instruction-only skill with no install spec and no code files. Lowest install risk — nothing is written by an installer step. All runtime risk comes from network calls described in SKILL.md.
!
Credentials
Only NEMO_TOKEN is declared as required, which fits the service. But SKILL.md's frontmatter declares a config path (~/.config/nemovideo/) that was not listed in the registry's requirements — this is an inconsistency. The skill also instructs generating and using anonymous tokens (POST to https://mega-api-prod.nemovideo.ai) and says to 'store' tokens/session IDs; it's unclear whether this implies writing to disk or setting environment variables. Confirming where sensitive tokens are kept and whether the skill will read ~/.config/nemovideo/ or other local files is important.
Persistence & Privilege
The skill is not always:true and does not request elevated platform privileges. Autonomous invocation is allowed (default) but not unusual. There is no explicit instruction to modify other skills or global agent settings.
What to consider before installing
This skill looks like a legitimate cloud-based video editor, but verify a few things before enabling it: - Confirm the config-path mismatch: SKILL.md mentions ~/.config/nemovideo/ while the registry metadata says none — ask the author whether the skill will read that directory and why. Reading that path could expose local config or credentials. - Understand token handling: the skill will POST to https://mega-api-prod.nemovideo.ai to obtain anonymous tokens if NEMO_TOKEN is absent. Ask where the returned token and session_id are stored (in-memory only, written to disk, or set as environment variables). Prefer in-memory/session storage and short TTLs. - Privacy: using the skill uploads your raw videos to an external service. If videos contain sensitive content, do not upload until you verify the service's privacy policy and data retention practices. - Attribution headers: the skill requires X-Skill-Source/Version/Platform headers derived from its frontmatter and install path — confirm whether auto-detecting/install-path inspection exposes any local metadata you do not want shared. - Domain verification: review the API domain (mega-api-prod.nemovideo.ai) and, if possible, validate the service operator. If you need stronger assurance, request hosted documentation or a homepage/source repository. If the author can clarify the config path usage, token storage policy, and data retention/privacy terms, the inconsistencies would likely be resolved and confidence could be raised.

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

Runtime requirements

🎬 Clawdis
EnvNEMO_TOKEN
Primary envNEMO_TOKEN
latestvk974p7pdr53tg1qp4zsxvhncgn85jr86
50downloads
0stars
1versions
Updated 2d ago
v1.0.0
MIT-0

Getting Started

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

Try saying:

  • "edit a 2-minute iPhone recording of a birthday party into a 1080p MP4"
  • "trim the boring parts, add transitions, and put background music"
  • "editing home or hobby videos without learning complex software for Mac users new to video editing"

First-Time Connection

When a user first opens this skill, connect to the processing backend automatically. Briefly let them know (e.g. "Setting up...").

Authentication: Check if NEMO_TOKEN is set in the environment. If it is, skip to step 2.

  1. Obtain a free token: Generate a random UUID as client identifier. POST to https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with header X-Client-Id set to that UUID. The response data.token is your NEMO_TOKEN — 100 free credits, valid 7 days.
  2. Create a session: POST to https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Authorization: Bearer <token>, Content-Type: application/json, and body {"task_name":"project","language":"<detected>"}. Store the returned session_id for all subsequent requests.

Keep setup communication brief. Don't display raw API responses or token values to the user.

Video Editor for Beginners on Mac — Edit and Export Videos Easily

Send me your raw video clips and describe the result you want. The AI-assisted video editing runs on remote GPU nodes — nothing to install on your machine.

A quick example: upload a 2-minute iPhone recording of a birthday party, type "trim the boring parts, add transitions, and put background music", and you'll get a 1080p MP4 back in roughly 1-2 minutes. All rendering happens server-side.

Worth noting: shorter clips under 3 minutes process significantly faster on first export.

Matching Input to Actions

User prompts referencing video editor for beginners mac, 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.

Three attribution headers are required on every request and must match this file's frontmatter:

HeaderValue
X-Skill-Sourcevideo-editor-for-beginners-mac
X-Skill-Versionfrontmatter version
X-Skill-Platformauto-detect: clawhub / cursor / unknown from install path

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.

Error Codes

  • 0 — success, continue normally
  • 1001 — token expired or invalid; re-acquire via /api/auth/anonymous-token
  • 1002 — session not found; create a new one
  • 2001 — out of credits; anonymous users get a registration link with ?bind=<id>, registered users top up
  • 4001 — unsupported file type; show accepted formats
  • 4002 — file too large; suggest compressing or trimming
  • 400 — missing X-Client-Id; generate one and retry
  • 402 — free plan export blocked; not a credit issue, subscription tier
  • 429 — rate limited; wait 30s and retry 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 boring parts, add transitions, and put background music" → Download MP4. Takes 1-2 minutes 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 boring parts, add transitions, and put background music" — 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 across Mac, iPhone, and social platforms.

Comments

Loading comments...