Maker Arabic

Turn a 60-second product demo video into 1080p Arabic-language videos just by typing what you need. Whether it's creating Arabic-language videos with text an...

Security Scan

The skill appears to do what it says (upload video, create Arabic renders) and only requests one token, but there are small inconsistencies about required config paths and the instructions ask the agent to make network calls and potentially probe install/config paths — things you should confirm before installing or handing over tokens.

Purpose & Capability

The declared purpose (server-side Arabic video rendering) matches the runtime actions (session creation, upload, render, export) and the single declared secret (NEMO_TOKEN) is appropriate. However, the SKILL.md frontmatter references a required config path (~/.config/nemovideo/) while the registry metadata lists no required config paths — an inconsistency that should be clarified.

Instruction Scope

The instructions direct the agent to use NEMO_TOKEN if present or obtain an anonymous token by POSTing to an external API, create sessions, upload user video files, stream SSE, poll render status, and include attribution headers. Those network operations are expected for this service, but the doc also implies detecting an install path to set X-Skill-Platform (which would require probing local paths) and references a config directory in its metadata — the agent may therefore be directed to access local filesystem state beyond simply reading one env var.

Install Mechanism

Instruction-only skill with no install spec and no code files. Nothing is written to disk by an installer here — lowest install risk.

Credentials

Only NEMO_TOKEN is requested as the primary credential, which is proportional for a third-party API. Be aware that the skill instructs the agent to include that token on every request to https://mega-api-prod.nemovideo.ai (i.e., the token will be sent to that domain).

Persistence & Privilege

always:false and no install actions; skill does not request persistent presence or elevated platform privileges in the manifest. Nothing indicates it will modify other skills or system-wide settings.

What to consider before installing

This skill is mostly coherent for its stated purpose (remote Arabic video rendering) and only needs one API token, but check these before installing: 1) Clarify the config-path discrepancy — SKILL.md frontmatter mentions ~/.config/nemovideo/ even though the registry shows no required config paths. Confirm whether the agent will read that directory or any other local files. 2) Understand that any video files and any NEMO_TOKEN you provide will be sent to https://mega-api-prod.nemovideo.ai; do not provide long-lived or highly-privileged credentials unless you trust the service. 3) If you want to test safely, let the skill obtain an anonymous starter token (the instructions support that) rather than providing a personal token, and verify the domain and privacy/retention policy for uploaded videos. 4) If you need stronger assurance, ask the skill author for a privacy/security statement or an official homepage/release repository (none is provided).

Getting Started

Send me your video clips and I'll handle the Arabic video creation. Or just describe what you're after.

Try saying:

• "create a 60-second product demo video into a 1080p MP4"
• "create a video with Arabic text, voiceover, and subtitles"
• "creating Arabic-language videos with text and subtitles for Arabic content creators"

Getting Connected

Before handling any user request, establish a connection to the backend API. Show a brief status like "Connecting...".

If NEMO_TOKEN is in the environment, use it directly and create a session. Otherwise, acquire a free starter token:

• Generate a UUID as client identifier
• POST to https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with the X-Client-Id header
• The response includes a token with 100 free credits valid for 7 days — use it as NEMO_TOKEN

Then create a session by POSTing to https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Bearer authorization and body {"task_name":"project","language":"en"}. The session_id in the response is needed for all following requests.

Tell the user you're ready. Keep the technical details out of the chat.

Maker Arabic — Create Arabic Language Videos

Send me your video clips and describe the result you want. The Arabic video creation runs on remote GPU nodes — nothing to install on your machine.

A quick example: upload a 60-second product demo video, type "create a video with Arabic text, voiceover, and subtitles", and you'll get a 1080p MP4 back in roughly 1-2 minutes. All rendering happens server-side.

Worth noting: right-to-left Arabic text renders correctly — no manual alignment needed.

Matching Input to Actions

User prompts referencing maker arabic, 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 maker-arabic, 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).

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

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

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "create a video with Arabic text, voiceover, and subtitles" — 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 Arabic social platforms.

Common Workflows

Quick edit: Upload → "create a video with Arabic text, voiceover, and subtitles" → 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.