Screen Recording Editor Online

Get edited screen recordings ready to post, without touching a single slider. Upload your screen recording files (MP4, MOV, WebM, AVI, up to 500MB), say some...

Security Scan

The skill's requirements and runtime instructions are broadly consistent with an online video-editing frontend that talks to nemo's cloud API, but there are minor metadata/instruction inconsistencies and privacy considerations you should review before installing.

Purpose & Capability

The skill requests a single API credential (NEMO_TOKEN) and describes endpoints and workflows for uploading, editing, and exporting videos on a nemo cloud service — this aligns with the declared purpose of cloud AI video editing.

Instruction Scope

SKILL.md is explicit about making network calls to https://mega-api-prod.nemovideo.ai (session creation, SSE chat, upload, export). It also describes deriving headers from the YAML frontmatter and detecting X-Skill-Platform from install path locations, which implies checking the agent's install-directory paths; this is within scope for header population but is a modest additional filesystem probe beyond the stated upload/edit flow.

Install Mechanism

Instruction-only skill with no install spec and no code files — nothing is written to disk by an installer, which is the lowest-risk installation model.

Credentials

Only NEMO_TOKEN is required which is proportional to calling the nemo API. However, SKILL.md/YAML references a config path (~/.config/nemovideo/) in its frontmatter (metadata) while the registry summary showed no required config paths — this mismatch should be clarified. The skill also supports generating an anonymous token by POSTing a UUID to the service if NEMO_TOKEN is absent (expected but worth noting because it contacts an external auth endpoint).

Persistence & Privilege

always:false and no system-wide config modifications are requested. The skill can be invoked autonomously (platform default) but it does not request elevated or persistent privileges.

Assessment

This skill appears to do what it says: it uploads your recordings to a third‑party cloud service (nemovideo) for AI editing and requires a NEMO_TOKEN or will fetch an anonymous starter token. Before installing, consider: 1) Privacy — your raw video/audio will be sent to an external server; confirm you’re comfortable with that and check the provider’s privacy/security policy. 2) Credentials — only provide NEMO_TOKEN if you trust the service; prefer using an ephemeral/anonymous token if possible. 3) Metadata mismatch — the skill's YAML references a config path (~/.config/nemovideo/) and asks the agent to detect install paths for a header; ask the author to confirm whether the skill reads local installation directories or config files. 4) No source/homepage — lack of a vendor homepage or source reduces traceability; request a provider link, docs, and terms of service before use. If you want higher assurance, ask the author to supply a homepage/privacy policy and to remove or document any local filesystem checks.

Getting Started

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

Try saying:

• "edit my screen recording files"
• "export 1080p MP4"
• "trim the pauses, add captions, and"

Getting Connected

Before handling any user request, establish a connection to the backend API. Show a brief status like "Connecting...".

If NEMO_TOKEN is in the environment, use it directly and create a session. Otherwise, acquire a free starter token:

• Generate a UUID as client identifier
• POST to https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with the X-Client-Id header
• The response includes a token with 100 free credits valid for 7 days — use it as NEMO_TOKEN

Then create a session by POSTing to https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Bearer authorization and body {"task_name":"project","language":"en"}. The session_id in the response is needed for all following requests.

Tell the user you're ready. Keep the technical details out of the chat.

Screen Recording Editor Online — Edit and Export Screen Recordings

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

Say you have a 3-minute screen recording of a software tutorial and want to trim the pauses, add captions, and insert a title card at the start — the backend processes it in about 1-2 minutes and hands you a 1080p MP4.

Tip: trim dead air and long pauses first — it makes every other edit faster and cleaner.

Matching Input to Actions

User prompts referencing screen recording editor online, 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.

All calls go to https://mega-api-prod.nemovideo.ai. The main endpoints:

1. Session — POST /api/tasks/me/with-session/nemo_agent with {"task_name":"project","language":"<lang>"}. Gives you a session_id.
2. Chat (SSE) — POST /run_sse with session_id and your message in new_message.parts[0].text. Set Accept: text/event-stream. Up to 15 min.
3. Upload — POST /api/upload-video/nemo_agent/me/<sid> — multipart file or JSON with URLs.
4. Credits — GET /api/credits/balance/simple — returns available, frozen, total.
5. State — GET /api/state/nemo_agent/me/<sid>/latest — current draft and media info.
6. Export — POST /api/render/proxy/lambda with render ID and draft JSON. Poll GET /api/render/proxy/lambda/<id> every 30s for completed status and download URL.

Formats: 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 screen-recording-editor-online, 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.

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)

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

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.

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

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "trim the pauses, add captions, and insert a title card at the start" — concrete instructions get better results.

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

Export as MP4 with H.264 codec for the best compatibility across platforms and devices.

Common Workflows

Quick edit: Upload → "trim the pauses, add captions, and insert a title card at the start" → 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.