Ai Video Editor Contact Number

contact support request into support team response with this skill. Works with MP4, MOV, AVI, WebM files up to 500MB. existing NemoVideo users use it for rea...

Security Scan

The skill's requirements and runtime instructions are coherent with its stated purpose (contacting NemoVideo support and routing/processing uploaded video), but you should be aware it will send media and metadata to nemovideo.ai and it declares a local config path that isn't clearly referenced in the prose.

Purpose & Capability

Name/description (contacting NemoVideo support and submitting video jobs) align with the single required credential (NEMO_TOKEN) and the API endpoints the SKILL.md instructs the agent to call. Requiring a NemoVideo token is proportionate for this functionality.

Instruction Scope

Instructions are detailed and narrowly scoped to NemoVideo's API: create/refresh anonymous tokens, create sessions, upload files, submit render jobs, read SSE, and poll state. They do not instruct reading unrelated system files. Minor inconsistency: the YAML frontmatter lists a config path (~/.config/nemovideo/) but the runtime instructions do not explain what, if anything, should be read from or written to that path.

Install Mechanism

Instruction-only skill with no install spec and no code files — nothing is downloaded or written to disk by the skill itself beyond normal transient session state. This is the lowest-risk install model.

Credentials

Only NEMO_TOKEN is required (declared as primaryEnv), which matches the API calls. The extra metadata-configPath requirement in the frontmatter is unexplained and may imply optional local config access; the SKILL.md itself also supports generating a short-lived anonymous token if NEMO_TOKEN is absent.

Persistence & Privilege

The skill is not always-enabled and does not request elevated platform privileges. It asks to persist session_id/token-like values for session management (expected for a remote-render workflow). Autonomous invocation is allowed by default but is not combined with other concerning requests.

Assessment

This skill appears to do what it says: it will send your uploaded video and support message to NemoVideo's API (mega-api-prod.nemovideo.ai) and return rendered MP4s or support responses. Before installing or using it, consider: 1) privacy — video/audio you upload will leave your machine and be processed by NemoVideo; do not upload sensitive content unless you trust that service. 2) token handling — the skill asks for a NEMO_TOKEN (you can supply your own) and can generate a short-lived anonymous token for you; if you supply a persistent token, treat it like any API secret. 3) the frontmatter mentions a local config path (~/.config/nemovideo/) that the instructions do not clearly use—ask the publisher how local config is used or stored if that concerns you. 4) verify the domain (mega-api-prod.nemovideo.ai) is the official NemoVideo endpoint if you rely on this service. If you are comfortable with those points and with uploading files to NemoVideo, the skill is internally consistent.

Getting Started

Got support request to work with? Send it over and tell me what you need — I'll take care of the customer support routing.

Try saying:

• "contact a question about billing or a bug in the editor into a 1080p MP4"
• "how do I contact NemoVideo support about my AI video editor?"
• "reaching NemoVideo support for AI video editor help for existing NemoVideo users"

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 Contact Number — Get Help From NemoVideo Support

Drop your support request in the chat and tell me what you need. I'll handle the customer support routing on cloud GPUs — you don't need anything installed locally.

Here's a typical use: you send a a question about billing or a bug in the editor, ask for how do I contact NemoVideo support about my AI video editor?, and about under a minute later you've got a MP4 file ready to download. The whole thing runs at 1080p by default.

One thing worth knowing — live chat on the NemoVideo dashboard is usually faster than email support.

Matching Input to Actions

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

All calls go to https://mega-api-prod.nemovideo.ai. The main endpoints:

1. Session — POST /api/tasks/me/with-session/nemo_agent with {"task_name":"project","language":"<lang>"}. Gives you a session_id.
2. Chat (SSE) — POST /run_sse with session_id and your message in new_message.parts[0].text. Set Accept: text/event-stream. Up to 15 min.
3. Upload — POST /api/upload-video/nemo_agent/me/<sid> — multipart file or JSON with URLs.
4. Credits — GET /api/credits/balance/simple — returns available, frozen, total.
5. State — GET /api/state/nemo_agent/me/<sid>/latest — current draft and media info.
6. Export — POST /api/render/proxy/lambda with render ID and draft JSON. Poll GET /api/render/proxy/lambda/<id> every 30s for completed status and download URL.

Formats: 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-video-editor-contact-number, 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).

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.

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)

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

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.

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

Common Workflows

Quick edit: Upload → "how do I contact NemoVideo support about my AI video editor?" → Download MP4. Takes under a minute 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 "how do I contact NemoVideo support about my AI video editor?" — 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.