Video Editor Google Pixel

edit raw footage into edited MP4 clips with this skill. Works with MP4, MOV, WebM, MKV files up to 500MB. Google Pixel users use it for editing Google Pixel...

Security Scan

The skill's requirements and runtime instructions are consistent with a cloud-based video-editing integration; no unrelated credentials, installers, or privileged behaviors are requested, but there are a few small metadata/instruction inconsistencies and expected privacy trade-offs to note.

Purpose & Capability

Name/description (AI video editing for Pixel footage) match the runtime instructions: the SKILL.md describes uploading video files and calling a remote rendering API. The only required secret (NEMO_TOKEN) aligns with authenticating to that API. Minor inconsistency: registry metadata reported 'Required config paths: none' while the SKILL.md frontmatter lists a configPaths entry (~/.config/nemovideo/) — this is likely bookkeeping/inventory drift but should be clarified.

Instruction Scope

Instructions are focused on the service (token acquisition, session creation, uploads, render/export, polling). They do direct the agent to POST files and to include attribution headers. Two items to note: (1) the doc asks the agent to derive X-Skill-Platform by inspecting install paths (e.g. ~/.clawhub/, ~/.cursor/skills/), which implies reading the filesystem to detect install location; (2) the skill instructs generating and then using an anonymous token (NEMO_TOKEN) if none is present and to 'save' the session_id/token — behavior that is reasonable for session continuity but means tokens may be stored in the agent environment. Neither action is out-of-scope for a remote-editing integration, but both have privacy implications.

Install Mechanism

No install spec or code files are present — the skill is instruction-only and will not write or execute downloaded code on install. This is the lowest-risk installation model.

Credentials

Only one environment variable is requested (NEMO_TOKEN) and it is used to authenticate to the described nemo video API. The SKILL.md also describes creating an anonymous token via the service if none exists; no unrelated API keys, cloud credentials, or passwords are requested. The only slight proportionality concern is the earlier-mentioned configPaths entry in the frontmatter, which could imply the skill might read ~/.config/nemovideo/ — reasonable for this service but inconsistent with registry metadata and worth confirming.

Persistence & Privilege

The skill does not request always:true and does not ask to modify other skills or system-wide settings. It instructs saving a session_id and using/storing a short-lived NEMO_TOKEN (tokens expire after 7 days), which is appropriate for session-based remote rendering. The need to derive platform headers from install paths implies limited filesystem reads, but no elevated privileges are requested.

Assessment

This skill appears to be a straightforward client for a remote video-editing service and only needs a single API token (NEMO_TOKEN). Before installing: (1) confirm you trust the endpoint domain (mega-api-prod.nemovideo.ai) and review its privacy/retention policy for uploaded videos, (2) if you’re uncomfortable storing long-lived credentials, use the anonymous-token flow or a throwaway token as described (tokens are short-lived), (3) ask the maintainer to clarify the metadata inconsistency about config paths (~/.config/nemovideo/) and whether the skill will read local install/config directories, and (4) remember any video you upload will be transmitted to and processed by the external service — don’t upload sensitive content unless you’ve verified the provider’s security/privacy terms.

Getting Started

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

Try saying:

• "edit my raw footage"
• "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 for Google Pixel — Edit Pixel Footage and Export

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

A quick example: upload a 60-second Google Pixel video clip, type "trim the shaky parts, add transitions, and export as a clean MP4", and you'll get a 1080p MP4 back in roughly 30-60 seconds. All rendering happens server-side.

Worth noting: Google Pixel footage in 1080p processes faster than 4K recordings.

Matching Input to Actions

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

User says...	Action	Skip 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

Endpoint	Method	Purpose
/api/tasks/me/with-session/nemo_agent	POST	Start a new editing session. Body: {"task_name":"project","language":"<lang>"}. Returns session_id.
/run_sse	POST	Send 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>	POST	Upload a file (multipart) or URL.
/api/credits/balance/simple	GET	Check remaining credits (available, frozen, total).
/api/state/nemo_agent/me/<sid>/latest	GET	Fetch current timeline state (draft, video_infos, generated_media).
/api/render/proxy/lambda	POST	Start 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 video-editor-google-pixel, 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).

Every API call needs Authorization: Bearer <NEMO_TOKEN> plus the three attribution headers above. If any header is missing, exports return 402.

Error Handling

Code	Meaning	Action
0	Success	Continue
1001	Bad/expired token	Re-auth via anonymous-token (tokens expire after 7 days)
1002	Session not found	New session §3.0
2001	No credits	Anonymous: show registration URL with ?bind=<id> (get <id> from create-session or state response when needed). Registered: "Top up credits in your account"
4001	Unsupported file	Show supported formats
4002	File too large	Suggest compress/trim
400	Missing X-Client-Id	Generate Client-Id and retry (see §1)
402	Free plan export blocked	Subscription tier issue, NOT credits. "Register or upgrade your plan to unlock export."
429	Rate limit (1 token/client/7 days)	Retry in 30s once

SSE Event Handling

Event	Action
Text response	Apply GUI translation (§4), present to user
Tool call/result	Process internally, don't forward
heartbeat / empty data:	Keep waiting. Every 2 min: "⏳ Still working..."
Stream closes	Process 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.

Translating GUI Instructions

The backend responds as if there's a visual interface. Map its instructions to API calls:

• "click" or "点击" → execute the action via the relevant endpoint
• "open" or "打开" → query session state to get the data
• "drag/drop" or "拖拽" → send the edit command through SSE
• "preview in timeline" → show a text summary of current tracks
• "Export" or "导出" → run the 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)

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 as a clean MP4" — concrete instructions get better results.

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

Export as MP4 for widest compatibility across social platforms and devices.

Common Workflows

Quick edit: Upload → "trim the shaky parts, add transitions, and export as a clean MP4" → 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.