Video Editing With Chromebook

v1.0.0

Get edited MP4 clips ready to post, without touching a single slider. Upload your video clips (MP4, WebM, MOV, AVI, up to 500MB), say something like "trim th...

0· 73·0 current·0 all-time

Install

OpenClaw Prompt Flow

Install with OpenClaw

Best for remote or guided setup. Copy the exact prompt, then paste it into OpenClaw for dsewell-583h0/video-editing-with-chromebook.

Previewing Install & Setup.
Prompt PreviewInstall & Setup
Install the skill "Video Editing With Chromebook" (dsewell-583h0/video-editing-with-chromebook) from ClawHub.
Skill page: https://clawhub.ai/dsewell-583h0/video-editing-with-chromebook
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-editing-with-chromebook

ClawHub CLI

Package manager switcher

npx clawhub@latest install video-editing-with-chromebook
Security Scan
VirusTotalVirusTotal
Pending
View report →
OpenClawOpenClaw
Benign
medium confidence
Purpose & Capability
The name/description (remote GPU-based video editing for Chromebook users) matches the declared runtime actions (uploading video files, creating sessions, SSE editing, rendering/export). The sole required credential (NEMO_TOKEN) is appropriate for an API-backed editing service. Minor inconsistency: the SKILL.md YAML frontmatter lists a config path (~/.config/nemovideo/) while the registry metadata earlier reported no required config paths — likely an authoring oversight, not a functional red flag.
Instruction Scope
The SKILL.md limits behavior to API calls for session creation, SSE message passing, uploads, and export polling — all expected. It also instructs using local file paths (multipart file uploads) and generating/storing session_id, which is necessary for uploads. It asks the agent to detect install path to set an attribution header (X-Skill-Platform); that is unnecessary for core function and requires the agent to inspect its environment, but is not inherently malicious. Overall, instructions stay within the stated video-editing scope.
Install Mechanism
No install spec and no code files — instruction-only skill. This is the lowest-risk install model; nothing will be written to disk by an installer step.
Credentials
The skill requests a single credential (NEMO_TOKEN) as its primary env var, which is proportionate to calling a paid/authorized external API. The SKILL.md frontmatter additionally mentions a config path (~/.config/nemovideo/), which implies the skill might read or prefer local config, but the registry metadata did not declare required config paths — this mismatch should be clarified. No unrelated secrets or broad credential access are requested.
Persistence & Privilege
always is false and the skill does not request platform-wide privileges. It asks to store ephemeral session_id and to use tokens for API calls — normal for this type of integration.
Assessment
This skill appears to do what it says: call a remote video-editing API, upload your clips, and return rendered MP4s. Before installing: 1) Understand that uploaded videos are sent to https://mega-api-prod.nemovideo.ai — do not upload sensitive or private footage unless you trust the service and have reviewed its privacy policy. 2) NEMO_TOKEN is an API bearer token; treat it like a password — only provide a token with the minimal necessary scope and revoke it if you stop using the skill. 3) Ask the skill author to clarify the config-path mention (~/.config/nemovideo/) and why the agent must detect its install path for headers; this is a minor inconsistency but worth confirming. 4) If you prefer not to supply a long-lived token, the skill's anonymous-token flow is available but provides limited credits and temporary access. If any behavior beyond uploading files and calling the documented API appears (e.g., reading other files, accessing unrelated env vars, or altering other skills), stop and revoke tokens.

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

Runtime requirements

💻 Clawdis
EnvNEMO_TOKEN
Primary envNEMO_TOKEN
latestvk977vf1gfnn1p8s6tvs5v6qhmx85d6eh
73downloads
0stars
1versions
Updated 5d ago
v1.0.0
MIT-0

Getting Started

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

Try saying:

  • "edit a 3-minute screen recording from a Chromebook into a 1080p MP4"
  • "trim the pauses, add transitions, and export as MP4"
  • "editing videos on a Chromebook without installing desktop software for Chromebook users and students"

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 Editing with Chromebook — Edit and Export Videos Online

Send me your video clips 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 3-minute screen recording from a Chromebook, type "trim the pauses, add transitions, and export as MP4", and you'll get a 1080p MP4 back in roughly 1-2 minutes. All rendering happens server-side.

Worth noting: WebM files from Chromebook screen recorders upload directly without conversion.

Matching Input to Actions

User prompts referencing video editing with chromebook, 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 video-editing-with-chromebook, 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.

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.

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.

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)

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

Tips and Tricks

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

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

Export as MP4 for widest compatibility across devices and platforms.

Common Workflows

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

Comments

Loading comments...