Skills revid-ai

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/revid-ai" ~/.claude/skills/openclaw-skills-revid-ai && 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/revid-ai" ~/.openclaw/skills/openclaw-skills-revid-ai && rm -rf "$T"
manifest: skills/bwbernardweston18/revid-ai/SKILL.md
source content

Getting Started

Share your text or video and I'll get started on AI video creation. Or just tell me what you're thinking.

Try saying:

  • "create my text or video"
  • "export 1080p MP4"
  • "turn this article into a 60-second"

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.

Revid AI — Create Videos from Text

This tool takes your text or video and runs AI video creation through a cloud rendering pipeline. You upload, describe what you want, and download the result.

Say you have a blog post URL or short script and want to turn this article into a 60-second video with voiceover and captions — the backend processes it in about 1-2 minutes and hands you a 1080p MP4.

Tip: shorter scripts under 150 words produce faster and more focused output.

Matching Input to Actions

User prompts referencing revid 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.

Include

Authorization: Bearer <NEMO_TOKEN>
and all attribution headers on every request — omitting them triggers a 402 on export.

Headers are derived from this file's YAML frontmatter.

X-Skill-Source
is
revid-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 → "turn this article into a 60-second video with voiceover and captions" → 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 "turn this article into a 60-second video with voiceover and captions" — concrete instructions get better results.

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

Export as MP4 for widest compatibility across social platforms.