Arabic Video Editing With

edit raw video footage into edited Arabic videos with this arabic-video-editing-with skill. Works with MP4, MOV, AVI, WebM files up to 500MB. Arabic content...

Security Scan

The skill's network calls and single NEMO_TOKEN credential match an Arabic video editing backend, but inconsistent metadata about a local config path and vague instructions to 'auto-detect' install path raise questions about whether local files or install locations might be read or used.

Purpose & Capability

Name and description describe cloud-based Arabic video editing and all runtime endpoints target a NemoVideo API domain; requiring a NEMO_TOKEN is proportionate. However, the SKILL.md frontmatter declares a required configPaths entry (~/.config/nemovideo/) while the registry summary listed no required config paths — this mismatch is unexplained.

Instruction Scope

Runtime instructions are specific about session creation, upload, SSE handling, and headers — all consistent with a remote video editor. But the doc also asks to 'auto-detect' an install path to set the X-Skill-Platform header (clawhub/cursor/unknown), which implies reading agent/install metadata or filesystem locations; the skill does not justify or detail what is read. The frontmatter's configPaths entry suggests the skill might expect to access ~/.config/nemovideo/, but the runtime steps do not describe reading that path — this ambiguity could hide file reads of local config or tokens.

Install Mechanism

No install spec and no code files — instruction-only skill — so nothing is written to disk by an installer. This is the lower-risk option for installation.

Credentials

The skill requests a single credential (NEMO_TOKEN) which fits a cloud API integration. The frontmatter also lists a configPaths (~/.config/nemovideo/) which would give access to local configuration if read; that would broaden access beyond the single declared env var and needs justification.

Persistence & Privilege

always is false and there is no install-time modification of other skills or global agent settings described. Autonomous invocation is allowed (platform default) but not excessive in itself.

What to consider before installing

This skill largely looks like a thin client for a NemoVideo cloud renderer and the single NEMO_TOKEN requirement is reasonable — but two inconsistencies deserve attention before installing: (1) the SKILL.md frontmatter lists a config path (~/.config/nemovideo/) that could contain local credentials or other data; clarify whether the skill will read that directory and why, and (2) the instruction to 'auto-detect' an install path for the X-Skill-Platform header implies filesystem or environment probes — ask the author what is read and whether any local files or other tokens are accessed. If you cannot get clear answers, consider using a throwaway NEMO_TOKEN/test account, disallow autonomous invocation for the skill, or avoid installing it. If you can provide the author response or the exact code the agent will run to detect the platform/config, I can re-evaluate with higher confidence.

Getting Started

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

Try saying:

• "edit my raw video footage"
• "export 1080p MP4"
• "add Arabic subtitles, trim pauses, and"

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.

Arabic Video Editing With AI — Edit Arabic Videos With AI

Send me your raw video footage and describe the result you want. The AI Arabic video editing runs on remote GPU nodes — nothing to install on your machine.

A quick example: upload a 2-minute Arabic vlog recorded on a smartphone, type "add Arabic subtitles, trim pauses, and add transitions between scenes", and you'll get a 1080p MP4 back in roughly 1-2 minutes. All rendering happens server-side.

Worth noting: shorter clips under 3 minutes process significantly faster and produce cleaner results.

Matching Input to Actions

User prompts referencing arabic video editing with, 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.

Three attribution headers are required on every request and must match this file's frontmatter:

Header	Value
X-Skill-Source	arabic-video-editing-with
X-Skill-Version	frontmatter version
X-Skill-Platform	auto-detect: clawhub / cursor / unknown from install path

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

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)

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

SSE Event Handling

Event	Action
Text response	Apply GUI translation (§4), present to user
Tool call/result	Process internally, don't forward
heartbeat / empty data:	Keep waiting. Every 2 min: "⏳ Still working..."
Stream closes	Process final response

~30% of editing operations return no text in the SSE stream. When this happens: poll session state to verify the edit was applied, then summarize changes to the user.

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 "add Arabic subtitles, trim pauses, and add transitions between scenes" — concrete instructions get better results.

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

Export as MP4 with H.264 codec for the best compatibility across Arabic social platforms.

Common Workflows

Quick edit: Upload → "add Arabic subtitles, trim pauses, and add transitions between scenes" → 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.