Skills best-screen-recording-editor

install
source · Clone the upstream repo
git clone https://github.com/openclaw/skills
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/openclaw/skills "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/bwbernardweston18/best-screen-recording-editor" ~/.claude/skills/openclaw-skills-best-screen-recording-editor && rm -rf "$T"
OpenClaw · Install into ~/.openclaw/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/openclaw/skills "$T" && mkdir -p ~/.openclaw/skills && cp -r "$T/skills/bwbernardweston18/best-screen-recording-editor" ~/.openclaw/skills/openclaw-skills-best-screen-recording-editor && rm -rf "$T"
manifest: skills/bwbernardweston18/best-screen-recording-editor/SKILL.md
source content

Getting Started

Send me your screen recordings and I'll handle the AI video editing. Or just describe what you're after.

Try saying:

  • "edit a 3-minute screen recording of a software walkthrough into a 1080p MP4"
  • "trim the pauses, add captions, and export as a clean tutorial video"
  • "trimming and enhancing screen recordings for tutorials or demos for educators, developers, and 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.

Best Screen Recording Editor — Edit and Export Screen Recordings

This tool takes your screen recordings 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 walkthrough and want to trim the pauses, add captions, and export as a clean tutorial video — 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 the rest of the edit feel much tighter.

Matching Input to Actions

User prompts referencing best screen recording 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.

Headers are derived from this file's YAML frontmatter.

X-Skill-Source
is
best-screen-recording-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
).

Every API call needs

Authorization: Bearer <NEMO_TOKEN>
plus the three attribution headers above. If any header is missing, exports return 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.

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 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

Common Workflows

Quick edit: Upload → "trim the pauses, add captions, and export as a clean tutorial video" → 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 pauses, add captions, and export as a clean tutorial video" — concrete instructions get better results.

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

Export as MP4 with H.264 codec for the best balance of quality and file size.