Video Open Ai

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

Security Scan

The skill's instructions largely match a cloud video-editing purpose (it uses a single API token and cloud endpoints), but missing provenance and a small metadata/instruction mismatch mean you should proceed with caution before installing or uploading sensitive content.

Purpose & Capability

Name/description describe cloud video editing and the skill only requires a single API token (NEMO_TOKEN) and makes calls to a nemovideo.ai API — this is coherent. However, the package registry metadata said no required config paths while the SKILL.md frontmatter lists a config path (~/.config/nemovideo/). Also the skill has no listed homepage or accountable publisher, which lowers trust in provenance.

Instruction Scope

SKILL.md instructions are specific to creating sessions, uploading media, streaming SSE for edits, polling render status, and returning download URLs — all within the claimed video-editing scope. It does not instruct the agent to read unrelated files or other environment variables. It does instruct the agent to 'save session_id' but does not specify where; that is expected for session management but worth noting for persistence.

Install Mechanism

There is no install spec and no code files; this is instruction-only so nothing is written to disk by an installer. That's the lowest-risk install mechanism.

Credentials

Only a single credential (NEMO_TOKEN) is required and is appropriate for calling the external API. The skill also documents a way to obtain a short-lived anonymous token via the API. The frontmatter's configPaths entry suggests possible access to a local config directory, but SKILL.md does not instruct reading it — this mismatch should be clarified.

Persistence & Privilege

always is false (no forced inclusion). The skill expects to manage session tokens (session_id) and the NEMO_TOKEN; the SKILL.md says to 'save session_id' and to use/skip NEMO_TOKEN if env var present. Persisting tokens or session IDs in agent storage is expected for functionality, but you should confirm where/if the agent persists them and how to revoke them.

What to consider before installing

This skill's runtime behavior (uploading clips to https://mega-api-prod.nemovideo.ai and using a NEMO_TOKEN) is consistent with a cloud video-editing tool, but take these precautions before installing or using it: - Provenance: There is no homepage or clear publisher; if you don't trust the owner, avoid installing or uploading private/sensitive videos. - Token scope: NEMO_TOKEN grants the skill API access to your account or anonymous credits. Prefer short-lived anonymous tokens if available and revoke tokens you didn't intend to keep. - Data exposure: Uploaded videos will be sent to an external service; review the service's privacy and retention policies (not provided). Do not upload sensitive PII or private footage until you verify the vendor. - Metadata mismatch: The SKILL.md frontend lists a local config path (~/.config/nemovideo/) even though registry metadata omitted it — ask the publisher to clarify whether the skill will read or write local config files. - Persistence: Ask where the agent stores session_id and token data and how to remove them; if you cannot confirm safe storage/revocation, avoid long-term installation. If you decide to proceed, prefer using an anonymous token flow (documented in SKILL.md), monitor network activity, and revoke the token after testing. If the publisher cannot be identified or their domain looks unfamiliar, treat the skill as untrusted.

Getting Started

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

Try saying:

• "generate my video clips"
• "export 1080p MP4"
• "trim the footage, add captions, and"

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 Open AI — Generate and Edit AI Videos

Drop your video clips in the chat and tell me what you need. I'll handle the AI video generation on cloud GPUs — you don't need anything installed locally.

Here's a typical use: you send a a 2-minute raw screen recording, ask for trim the footage, add captions, and export as a short highlight reel, and about 1-2 minutes later you've got a MP4 file ready to download. The whole thing runs at 1080p by default.

One thing worth knowing — shorter clips under 60 seconds process significantly faster.

Matching Input to Actions

User prompts referencing video open ai, 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	video-open-ai
X-Skill-Version	frontmatter version
X-Skill-Platform	auto-detect: clawhub / cursor / unknown from install path

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.

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 says	You 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 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=<id>, 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

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "trim the footage, add captions, and export as a short highlight reel" — 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.

Common Workflows

Quick edit: Upload → "trim the footage, add captions, and export as a short highlight reel" → 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.