Free Screen Record

Cloud-based free-screen-record tool that handles recording and editing screen captures for tutorials or demos. Upload MP4, MOV, WebM, AVI files (up to 500MB)...

Security Scan

The skill's requests and runtime instructions are generally consistent with a cloud video editing tool, but there are small inconsistencies and privacy considerations the user should understand before installing.

Purpose & Capability

The skill is a cloud-based screen-record editing tool and declares NEMO_TOKEN as its primary credential, which fits the purpose. However the SKILL.md YAML frontmatter references a config path (~/.config/nemovideo/) that is not reflected in the registry metadata — this inconsistency should be clarified.

Instruction Scope

Instructions are prescriptive about authenticating (using NEMO_TOKEN or obtaining an anonymous token), creating sessions, uploading files, starting exports, and streaming SSE. These are coherent with the stated purpose. They do instruct the agent to detect install paths (e.g., ~/.clawhub/, ~/.cursor/skills/) to set an X-Skill-Platform header — that implies the agent may probe the user's home filesystem for install locations, which is not strictly necessary for core functionality and should be justified.

Install Mechanism

There is no install spec and no code files — the skill is instruction-only, which minimizes on-disk risk.

Credentials

Only NEMO_TOKEN is required, which is appropriate for a cloud service token. The frontmatter also listed a config path (~/.config/nemovideo/) that suggests the skill might read a local config file — this is not declared in the registry metadata and would broaden access to local files if performed.

Persistence & Privilege

The skill does not request always:true or other elevated persistent privileges, and it does not declare any behavior that modifies other skills or global agent settings.

Assessment

This skill appears to do what it says: it will send uploaded videos to an external API (mega-api-prod.nemovideo.ai) and return edited outputs. Before installing: (1) confirm you trust the external service and domain; (2) avoid uploading sensitive recordings until you verify privacy/retention policy; (3) check whether the skill will read ~/.config/nemovideo/ or other paths — if you don't want local files probed, decline or ask the author to remove that behavior; (4) be aware the skill will create/use an anonymous NEMO_TOKEN if none is provided — treat any persistent NEMO_TOKEN as a credential and don't set a high-privilege secret as that env var; (5) test with non-sensitive data first. The main issues are metadata inconsistency (declared config paths vs registry) and the small privacy risk of probing install/config paths — these do not by themselves indicate malicious intent, but you should confirm them with the publisher.

Getting Started

Share your screen recordings and I'll get started on screen capture editing. Or just tell me what you're thinking.

Try saying:

• "edit my screen recordings"
• "export 1080p MP4"
• "trim the intro, add captions, and"

Quick Start Setup

This skill connects to a cloud processing backend. On first use, set up the connection automatically and let the user know ("Connecting...").

Token check: Look for NEMO_TOKEN in the environment. If found, skip to session creation. Otherwise:

• Generate a UUID as client identifier
• POST https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with X-Client-Id header
• Extract data.token from the response — this is your NEMO_TOKEN (100 free credits, 7-day expiry)

Session: POST https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Bearer auth and body {"task_name":"project"}. Keep the returned session_id for all operations.

Let the user know with a brief "Ready!" when setup is complete. Don't expose tokens or raw API output.

Free Screen Record — Record, Edit and Export Videos

Send me your screen recordings and describe the result you want. The screen capture editing runs on remote GPU nodes — nothing to install on your machine.

A quick example: upload a 2-minute screen recording of a software demo, type "trim the intro, add captions, and export as MP4", and you'll get a 1080p MP4 back in roughly 30-60 seconds. All rendering happens server-side.

Worth noting: shorter recordings under 5 minutes process significantly faster.

Matching Input to Actions

User prompts referencing free screen record, 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.

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

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

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.

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

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

Reading the SSE Stream

Text events go straight to the user (after GUI translation). Tool calls stay internal. Heartbeats and empty data: lines mean the backend is still working — show "⏳ Still working..." every 2 minutes.

About 30% of edit operations close the stream without any text. When that happens, poll /api/state to confirm the timeline changed, then tell the user what was updated.

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 intro, add captions, and export as 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.

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "trim the intro, add captions, and export as MP4" — concrete instructions get better results.

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

Export as MP4 for widest compatibility across platforms and devices.