← Back to Skills Marketplace
dsewell-583h0

4k Editing With Openshot

by dsewell-583h0 · GitHub ↗ · v1.0.0 · MIT-0
cross-platform ✓ Security Clean
31
Downloads
0
Stars
0
Active Installs
1
Versions
Install in OpenClaw
/install 4k-editing-with-openshot
Description
Skip the learning curve of professional editing software. Describe what you want — cut the footage, add transitions, and export in 4K resolution like OpenSho...
README (SKILL.md)

Getting Started

Got raw video footage to work with? Send it over and tell me what you need — I'll take care of the AI 4K video editing.

Try saying:

  • "edit a 3-minute 4K drone footage clip into a 4K MP4"
  • "cut the footage, add transitions, and export in 4K resolution like OpenShot would"
  • "editing high-resolution 4K footage with OpenShot-style tools for indie filmmakers and content creators"

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.

4K Editing with OpenShot — Edit and Export 4K Videos

Drop your raw video footage in the chat and tell me what you need. I'll handle the AI 4K video editing on cloud GPUs — you don't need anything installed locally.

Here's a typical use: you send a a 3-minute 4K drone footage clip, ask for cut the footage, add transitions, and export in 4K resolution like OpenShot would, and about 1-3 minutes later you've got a MP4 file ready to download. The whole thing runs at 4K by default.

One thing worth knowing — splitting your 4K footage into shorter segments before uploading speeds up processing significantly.

Matching Input to Actions

User prompts referencing 4k editing with openshot, 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.

Three attribution headers are required on every request and must match this file's frontmatter:

Header Value
X-Skill-Source 4k-editing-with-openshot
X-Skill-Version frontmatter version
X-Skill-Platform auto-detect: clawhub / cursor / unknown from install path

Every API call needs Authorization: Bearer \x3CNEMO_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":"\x3Clang>"} — returns task_id, session_id.

Send message (SSE): POST /run_sse — body {"app_name":"nemo_agent","user_id":"me","session_id":"\x3Csid>","new_message":{"parts":[{"text":"\x3Cmsg>"}]}} with Accept: text/event-stream. Max timeout: 15 minutes.

Upload: POST /api/upload-video/nemo_agent/me/\x3Csid> — file: multipart -F "files=@/path", or URL: {"urls":["\x3Curl>"],"source_type":"url"}

Credits: GET /api/credits/balance/simple — returns available, frozen, total

Session state: GET /api/state/nemo_agent/me/\x3Csid>/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_\x3Cts>","sessionId":"\x3Csid>","draft":\x3Cjson>,"output":{"format":"mp4","quality":"high"}}. Poll GET /api/render/proxy/lambda/\x3Cid> 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.

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 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=\x3Cid>, 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

Common Workflows

Quick edit: Upload → "cut the footage, add transitions, and export in 4K resolution like OpenShot would" → Download MP4. Takes 1-3 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 "cut the footage, add transitions, and export in 4K resolution like OpenShot would" — concrete instructions get better results.

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

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

Usage Guidance
This skill appears purpose-aligned for cloud video editing and does not include local code, shell commands, or hidden persistence in the provided artifacts. Before installing, be comfortable sending your videos to the NemoVideo cloud service, protect the NEMO_TOKEN, and verify whether exports are actually delivered at the resolution you need.
Capability Analysis
Type: OpenClaw Skill Name: 4k-editing-with-openshot Version: 1.0.0 The skill provides a cloud-based video editing interface by connecting to the mega-api-prod.nemovideo.ai backend. It manages authentication via the NEMO_TOKEN environment variable or an anonymous token generation process, and it handles video processing tasks such as uploads, timeline state management, and rendering. The instructions in SKILL.md are consistent with the stated purpose of providing a remote editing service, and no evidence of malicious intent, unauthorized data exfiltration, or harmful prompt injection was found.
Capability Assessment
Purpose & Capability
The stated purpose is cloud-based video editing/export, and the API instructions align with that purpose. However, the marketing repeatedly promises 4K output while the pipeline details say output is up to 1080x1920, so users should verify the actual export resolution.
Instruction Scope
The skill routes user requests to cloud API actions such as upload, SSE editing, state checks, credits, and export. This is purpose-aligned, but file uploads and exports should remain tied to explicit user intent.
Install Mechanism
There is no install spec and no code files. The skill is instruction-only but depends on a third-party backend and a NEMO_TOKEN, including automatic anonymous-token setup if the token is absent.
Credentials
No local binaries or shell commands are required, which is proportionate. The main environmental impact is external network/API use and uploading user-provided media to the cloud.
Persistence & Privilege
The artifacts show use of a bearer token and session_id, with an anonymous token described as expiring after 7 days. No background process or hidden persistence is shown, though the frontmatter references a NemoVideo config path.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install 4k-editing-with-openshot
  3. After installation, invoke the skill by name or use /4k-editing-with-openshot
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.0
Initial release of 4K Editing with OpenShot — cloud-based 4K video editing for creators. - Upload MP4, MOV, AVI, or MKV videos (up to 500MB) and get 4K edited videos in minutes. - AI handles cutting, transitions, and exporting in 4K, simulating an OpenShot workflow. - No software installation needed; all processing happens on cloud GPUs. - Simple setup: automatic connection with anonymous token for 100 free credits. - Supports timeline preview, exporting, credits check, and iterative editing in-session. - Batch process multiple files or refine edits over several steps.
Metadata
Slug 4k-editing-with-openshot
Version 1.0.0
License MIT-0
All-time Installs 0
Active Installs 0
Total Versions 1
Frequently Asked Questions

What is 4k Editing With Openshot?

Skip the learning curve of professional editing software. Describe what you want — cut the footage, add transitions, and export in 4K resolution like OpenSho... It is an AI Agent Skill for Claude Code / OpenClaw, with 31 downloads so far.

How do I install 4k Editing With Openshot?

Run "/install 4k-editing-with-openshot" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is 4k Editing With Openshot free?

Yes, 4k Editing With Openshot is completely free, licensed under MIT-0. You can download, install and use it at no cost.

Which platforms does 4k Editing With Openshot support?

4k Editing With Openshot is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created 4k Editing With Openshot?

It is built and maintained by dsewell-583h0 (@dsewell-583h0); the current version is v1.0.0.

💬 Comments