Zsky Ai

v1.0.0

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

0· 107·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 vcarolxhberger/zsky-ai.

Previewing Install & Setup.
Prompt PreviewInstall & Setup
Install the skill "Zsky Ai" (vcarolxhberger/zsky-ai) from ClawHub.
Skill page: https://clawhub.ai/vcarolxhberger/zsky-ai
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 zsky-ai

ClawHub CLI

Package manager switcher

npx clawhub@latest install zsky-ai
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
medium confidence
Purpose & Capability
Name/description match the declared API endpoints and the single required credential (NEMO_TOKEN). Asking for a service token and a session lifecycle is proportionate for a cloud video-rendering skill.
Instruction Scope
SKILL.md instructs the agent to check the NEMO_TOKEN, obtain an anonymous token from the stated nemovideo.ai endpoint if missing, create sessions, upload files, use SSE, poll render status, and download results — all consistent with a remote rendering workflow. The file-upload behavior will require reading user-specified video files (expected). The skill also describes detecting install path (~/.clawhub, ~/.cursor/skills) to populate X-Skill-Platform headers; that implies reading/install-path detection but does not request unrelated files or credentials.
Install Mechanism
Instruction-only skill with no install spec or code to write to disk; lowest-risk install footprint.
Credentials
Only NEMO_TOKEN is required which matches the API usage. Metadata lists a config path (~/.config/nemovideo/) that the instructions do not explicitly reference — this is not necessarily malicious but is an unexplained artifact to be aware of.
Persistence & Privilege
always:false and no request to modify other skills or system-wide config. The skill can be invoked autonomously (platform default) which is expected for a user-invocable integration.
Assessment
This skill appears to do what it says: it will upload your video files to a nemovideo.ai backend using a NEMO_TOKEN (or fetch an anonymous token). Before installing or using it, consider: (1) The backend domain is external and the service will receive any uploaded video and metadata — do not upload sensitive videos you wouldn't want transmitted off-device. (2) The skill can auto-create a short-lived anonymous token (100 free credits, 7-day expiry); if you prefer, provide your own NEMO_TOKEN instead of using anonymous auth. (3) The metadata mentions a config path (~/.config/nemovideo/) even though the instructions don't use it — check what data (if any) would be read from that location in your environment. (4) Verify you trust the unknown publisher/endpoint since there is no homepage or known vendor listed. If any of these are unacceptable, do not enable the skill or only use it with non-sensitive test videos.

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

Runtime requirements

🎬 Clawdis
EnvNEMO_TOKEN
Primary envNEMO_TOKEN
latestvk9733hvtpej7qbz5ptnkgnanhd84tawj
107downloads
0stars
1versions
Updated 1w ago
v1.0.0
MIT-0

Getting Started

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

Try saying:

  • "edit a 2-minute raw video recording into a 1080p MP4"
  • "enhance the video with AI effects and auto-edit the footage"
  • "auto-editing and enhancing video footage with AI for 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.

Zsky AI — AI Edit and Export Videos

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 2-minute raw video recording, type "enhance the video with AI effects and auto-edit the footage", and you'll get a 1080p MP4 back in roughly 30-60 seconds. All rendering happens server-side.

Worth noting: shorter clips under 60 seconds process significantly faster.

Matching Input to Actions

User prompts referencing zsky ai, 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.

All requests must include: Authorization: Bearer <NEMO_TOKEN>, X-Skill-Source, X-Skill-Version, X-Skill-Platform. Missing attribution headers will cause export to fail with 402.

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

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

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

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 → "enhance the video with AI effects and auto-edit the footage" → 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 "enhance the video with AI effects and auto-edit the footage" — concrete instructions get better results.

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

Export as MP4 for widest compatibility.

Comments

Loading comments...