Ai Ai Video

v1.0.0

Turn a 2-minute raw screen recording or phone video into 1080p AI-edited videos just by typing what you need. Whether it's automatically editing and enhancin...

⭐ 0· 51·0 current·0 all-time

by@francemichaell-15

OpenClaw Prompt Flow

Install with OpenClaw

Best for remote or guided setup. Copy the exact prompt, then paste it into OpenClaw for francemichaell-15/ai-ai-video.

Previewing Install & Setup.

Prompt PreviewInstall & Setup

Install the skill "Ai Ai Video" (francemichaell-15/ai-ai-video) from ClawHub.
Skill page: https://clawhub.ai/francemichaell-15/ai-ai-video
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 ai-ai-video

ClawHub CLI

Package manager switcher

npx clawhub@latest install ai-ai-video

Security Scan

VirusTotal

Suspicious

View report →

OpenClaw

Suspicious

medium confidence

ℹ

Purpose & Capability

Name/description align with the instructions: the skill routes uploads and edit requests to a remote video-processing API and requires a NEMO_TOKEN. However, the SKILL.md metadata lists a config path (~/.config/nemovideo/) that is not reflected in the registry's declared required config paths—this discrepancy should be explained by the author.

Instruction Scope

The runtime instructions direct the agent to upload user-provided video/audio/files to https://mega-api-prod.nemovideo.ai and to generate or use NEMO_TOKENs and session IDs. They also describe deriving an X-Skill-Platform value by checking install paths (e.g., ~/.clawhub/, ~/.cursor/skills/), which implies inspecting local paths. Transmitting raw user video to a third-party service and inspecting install paths are privacy-sensitive actions and should be clearly disclosed and justified.

✓

Install Mechanism

Instruction-only skill with no install spec and no code files—nothing is written to disk by an installer. This is the lowest-risk install model.

ℹ

Credentials

The skill only requires a single credential (NEMO_TOKEN), which fits the declared purpose. Caveat: SKILL.md's metadata mentions a config path (~/.config/nemovideo/) and the instructions read local install-paths to set an attribution header; those accesses are not listed in the registry metadata and may expose local environment details.

✓

Persistence & Privilege

The skill is not force-included (always:false) and is user-invocable. It asks to save a session_id from the API, which is reasonable for session continuity; there is no instruction to modify other skills or system-wide configuration. Autonomous invocation is allowed by default but not by itself a problem.

What to consider before installing

This skill will upload whatever video/audio you provide to a third-party API at mega‑api‑prod.nemovideo.ai and uses a NEMO_TOKEN (or obtains a short-lived anonymous token) to do so. Before installing or using it: (1) confirm you trust that external service and are comfortable sending your footage off-device (do not upload sensitive/confidential videos), (2) ask the publisher why SKILL.md references ~/.config/nemovideo/ and local install paths (this is not declared in the registry), and (3) avoid setting a long-lived or highly privileged NEMO_TOKEN unless you understand what account it grants access to. If you need higher assurance, request the skill’s source or a privacy/security policy from the author, or test with non-sensitive sample videos first.

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

Runtime requirements

🎬 Clawdis

EnvNEMO_TOKEN

Primary envNEMO_TOKEN

latestvk97aszsytv6qekw1kvpgqk46gx853jwm

51downloads

0stars

1versions

Updated 1w ago

v1.0.0

MIT-0

Getting Started

Share your raw video footage and I'll get started on AI video editing. Or just tell me what you're thinking.

Try saying:

"edit my raw video footage"
"export 1080p MP4"
"automatically edit my video, remove silences,"

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.

AI Video Editor — Edit and Export AI Videos

Send me your raw video footage 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 screen recording or phone video, type "automatically edit my video, remove silences, and add background music", and you'll get a 1080p MP4 back in roughly 1-2 minutes. All rendering happens server-side.

Worth noting: shorter clips under 60 seconds process significantly faster and use fewer credits.

Matching Input to Actions

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

Base URL: https://mega-api-prod.nemovideo.ai

Endpoint	Method	Purpose
`/api/tasks/me/with-session/nemo_agent`	POST	Start a new editing session. Body: `{"task_name":"project","language":"<lang>"}`. Returns `session_id`.
`/run_sse`	POST	Send a user message. Body includes `app_name`, `session_id`, `new_message`. Stream response with `Accept: text/event-stream`. Timeout: 15 min.
`/api/upload-video/nemo_agent/me/<sid>`	POST	Upload a file (multipart) or URL.
`/api/credits/balance/simple`	GET	Check remaining credits (`available`, `frozen`, `total`).
`/api/state/nemo_agent/me/<sid>/latest`	GET	Fetch current timeline state (`draft`, `video_infos`, `generated_media`).
`/api/render/proxy/lambda`	POST	Start export. Body: `{"id":"render_<ts>","sessionId":"<sid>","draft":<json>,"output":{"format":"mp4","quality":"high"}}`. Poll status every 30s.

Accepted file types: mp4, mov, avi, webm, mkv, jpg, png, gif, webp, mp3, wav, m4a, aac.

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

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

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

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 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 → "automatically edit my video, remove silences, and add background music" → 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 "automatically edit my video, remove silences, and add background music" — 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 across all platforms and devices.

Comments

Loading comments...