Video Maker Arabic

v1.0.0

Skip the learning curve of professional editing software. Describe what you want — add Arabic subtitles and right-to-left captions to my video — and get Arab...

0· 40·0 current·0 all-time

Install

OpenClaw Prompt Flow

Install with OpenClaw

Best for remote or guided setup. Copy the exact prompt, then paste it into OpenClaw for susan4731-wilfordf/video-maker-arabic.

Previewing Install & Setup.
Prompt PreviewInstall & Setup
Install the skill "Video Maker Arabic" (susan4731-wilfordf/video-maker-arabic) from ClawHub.
Skill page: https://clawhub.ai/susan4731-wilfordf/video-maker-arabic
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 video-maker-arabic

ClawHub CLI

Package manager switcher

npx clawhub@latest install video-maker-arabic
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
The name/description (Arabic video creation with RTL captions) align with the declared credential (NEMO_TOKEN) and the SKILL.md endpoints (nemovideo.ai). One minor inconsistency: the top-level registry metadata said no required config paths, but the SKILL.md YAML frontmatter lists a config path (~/.config/nemovideo/). This is likely a small metadata mismatch rather than functional misalignment.
Instruction Scope
Instructions stay within the expected scope: check/use NEMO_TOKEN, obtain an anonymous token if missing, create a session, upload user video/images, start renders, and stream/poll results. This necessarily involves uploading user media and session metadata to mega-api-prod.nemovideo.ai — which is expected for a cloud render service but is a privacy/security consideration. The skill also asks the agent to detect install path to set an attribution header; this implies the agent may read its install location.
Install Mechanism
No install spec or code files are present (instruction-only). Nothing will be written to disk by an installer as part of skill installation, which lowers supply-chain risk.
Credentials
Only one credential (NEMO_TOKEN) is required and is the expected type for a cloud API. The SKILL.md also references a local config path in its frontmatter (~/.config/nemovideo/), which suggests optional local config access — this should be clarified, but it is not disproportionate to the stated purpose.
Persistence & Privilege
The skill is not always-enabled and does not request elevated or persistent platform privileges. Autonomous invocation is allowed (platform default) and appropriate for a user-invoked media processing skill.
Assessment
This skill uploads your videos/images and related session metadata to mega-api-prod.nemovideo.ai and requires an API token (NEMO_TOKEN). Before installing, verify you trust the nemo video service and its privacy/retention policies; avoid uploading sensitive videos if you are unsure. Note the SKILL.md can obtain an anonymous temporary token if NEMO_TOKEN is absent (100 free credits, 7-day expiry). Ask the publisher to clarify the config path usage (~/.config/nemovideo/) and confirm where user data is stored/retained. If you need tighter control, require explicit user consent before any upload and review network activity or use a sandboxed environment for testing.

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

Runtime requirements

🎬 Clawdis
EnvNEMO_TOKEN
Primary envNEMO_TOKEN
latestvk973h8yh8s5y00azbctck61et585qzx8
40downloads
0stars
1versions
Updated 8h ago
v1.0.0
MIT-0

Getting Started

Share your video clips or images and I'll get started on Arabic video creation. Or just tell me what you're thinking.

Try saying:

  • "create my video clips or images"
  • "export 1080p MP4"
  • "add Arabic subtitles and right-to-left captions"

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.

Video Maker Arabic — Create Videos with Arabic Text

This tool takes your video clips or images and runs Arabic video creation through a cloud rendering pipeline. You upload, describe what you want, and download the result.

Say you have a 60-second product clip with no text and want to add Arabic subtitles and right-to-left captions to my video — the backend processes it in about 30-60 seconds and hands you a 1080p MP4.

Tip: Arabic text renders right-to-left automatically — no manual alignment needed.

Matching Input to Actions

User prompts referencing video maker arabic, aspect ratio, text overlays, or audio tracks get routed to the corresponding action via keyword and intent classification.

User says...ActionSkip 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

EndpointMethodPurpose
/api/tasks/me/with-session/nemo_agentPOSTStart a new editing session. Body: {"task_name":"project","language":"<lang>"}. Returns session_id.
/run_ssePOSTSend 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>POSTUpload a file (multipart) or URL.
/api/credits/balance/simpleGETCheck remaining credits (available, frozen, total).
/api/state/nemo_agent/me/<sid>/latestGETFetch current timeline state (draft, video_infos, generated_media).
/api/render/proxy/lambdaPOSTStart 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 video-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).

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

Error Handling

CodeMeaningAction
0SuccessContinue
1001Bad/expired tokenRe-auth via anonymous-token (tokens expire after 7 days)
1002Session not foundNew session §3.0
2001No creditsAnonymous: show registration URL with ?bind=<id> (get <id> from create-session or state response when needed). Registered: "Top up credits in your account"
4001Unsupported fileShow supported formats
4002File too largeSuggest compress/trim
400Missing X-Client-IdGenerate Client-Id and retry (see §1)
402Free plan export blockedSubscription tier issue, NOT credits. "Register or upgrade your plan to unlock export."
429Rate limit (1 token/client/7 days)Retry in 30s once

SSE Event Handling

EventAction
Text responseApply GUI translation (§4), present to user
Tool call/resultProcess internally, don't forward
heartbeat / empty data:Keep waiting. Every 2 min: "⏳ Still working..."
Stream closesProcess 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.

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 → "add Arabic subtitles and right-to-left captions to my video" → Download MP4. Takes 30-60 seconds 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 "add Arabic subtitles and right-to-left captions to my video" — 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 media platforms.

Comments

Loading comments...