En Espanol Editor Ai

v1.0.0

Cloud-based en-espanol-editor-ai tool that handles adding Spanish subtitles to videos. Upload MP4, MOV, AVI, WebM files (up to 500MB), describe what you need...

⭐ 0· 66·0 current·0 all-time

bypeandrover adam@peand-rover

OpenClaw Prompt Flow

Install with OpenClaw

Best for remote or guided setup. Copy the exact prompt, then paste it into OpenClaw for peand-rover/en-espanol-editor-ai.

Previewing Install & Setup.

Prompt PreviewInstall & Setup

Install the skill "En Espanol Editor Ai" (peand-rover/en-espanol-editor-ai) from ClawHub.
Skill page: https://clawhub.ai/peand-rover/en-espanol-editor-ai
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 en-espanol-editor-ai

ClawHub CLI

Package manager switcher

npx clawhub@latest install en-espanol-editor-ai

Security Scan

VirusTotal

Suspicious

View report →

OpenClaw

Benign

medium confidence

✓

Purpose & Capability

Name/description (Spanish subtitle editor) align with the instructions: upload videos, start sessions, send SSE messages, render, and download results. The single required env var (NEMO_TOKEN) is appropriate for calling the external API.

ℹ

Instruction Scope

Instructions tell the agent to POST files and metadata to an external API, generate an anonymous token if no NEMO_TOKEN exists, save session_id, stream SSE, and poll render status — all consistent with a cloud render pipeline. The SKILL.md also instructs reading this file's YAML frontmatter at runtime and detecting install path to set attribution headers; that implies filesystem inspection which is beyond pure network calls and may not be available in all runtimes.

✓

Install Mechanism

No install spec or code is included (instruction-only), so nothing will be written to disk by an installer. This is the lowest-risk install model.

✓

Credentials

Only one credential is required (NEMO_TOKEN) and the instructions provide a flow to create an anonymous token when absent. No unrelated secrets or multiple credentials are requested.

✓

Persistence & Privilege

Skill is not always-enabled and doesn't request special platform privileges. It does ask to 'save session_id' (expected for sessions) but does not instruct modifying other skills or system-wide settings.

Assessment

This skill appears coherent for a cloud-based Spanish subtitle/video editor and only requires a single service token (NEMO_TOKEN). Before installing: (1) confirm you trust the endpoint domain (mega-api-prod.nemovideo.ai) because using the skill will upload video and audio to that service; (2) understand NEMO_TOKEN (or an anonymous token generated by the skill) will be sent as Bearer auth for every API call; (3) note the skill may attempt to read its YAML frontmatter and detect install paths — that implies limited filesystem access — make sure you’re comfortable with that behavior in your environment; (4) verify the provider’s privacy/retention policy for uploaded media if you’re sending sensitive videos. If any of these are unacceptable, do not install or run the skill until you have more information about the service and hosting.

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

Runtime requirements

🇪🇸 Clawdis

EnvNEMO_TOKEN

Primary envNEMO_TOKEN

latestvk9739qwpx5n6gz0fv8dd367gmn84jrh7

66downloads

0stars

1versions

Updated 2w ago

v1.0.0

MIT-0

Getting Started

Ready when you are. Drop your video clips here or describe what you want to make.

Try saying:

"add a 2-minute tutorial video in English into a 1080p MP4"
"add subtitles in Spanish to my video"
"adding Spanish subtitles to videos for content creators"

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.

En Español Editor AI — Add Spanish Subtitles to Videos

This tool takes your video clips and runs Spanish subtitle generation through a cloud rendering pipeline. You upload, describe what you want, and download the result.

Say you have a 2-minute tutorial video in English and want to add subtitles in Spanish to my video — the backend processes it in about 30-60 seconds and hands you a 1080p MP4.

Tip: shorter clips under 3 minutes generate Spanish subtitles fastest.

Matching Input to Actions

User prompts referencing en espanol editor 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.

Base URL: https://mega-api-prod.nemovideo.ai

Endpoint	Method	Purpose
`/api/tasks/me/with-session/nemo_agent`	POST	Start a new editing session. Body: `{"task_name":"project","language":"<lang>"}`. Returns `session_id`.
`/run_sse`	POST	Send 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>`	POST	Upload a file (multipart) or URL.
`/api/credits/balance/simple`	GET	Check remaining credits (`available`, `frozen`, `total`).
`/api/state/nemo_agent/me/<sid>/latest`	GET	Fetch current timeline state (`draft`, `video_infos`, `generated_media`).
`/api/render/proxy/lambda`	POST	Start 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.

Skill attribution — read from this file's YAML frontmatter at runtime:

X-Skill-Source: en-espanol-editor-ai
X-Skill-Version: from frontmatter version
X-Skill-Platform: detect from install path (~/.clawhub/ → clawhub, ~/.cursor/skills/ → cursor, else 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

Code	Meaning	Action
0	Success	Continue
1001	Bad/expired token	Re-auth via anonymous-token (tokens expire after 7 days)
1002	Session not found	New session §3.0
2001	No credits	Anonymous: show registration URL with `?bind=<id>` (get `<id>` from create-session or state response when needed). Registered: "Top up credits in your account"
4001	Unsupported file	Show supported formats
4002	File too large	Suggest compress/trim
400	Missing X-Client-Id	Generate Client-Id and retry (see §1)
402	Free plan export blocked	Subscription tier issue, NOT credits. "Register or upgrade your plan to unlock export."
429	Rate limit (1 token/client/7 days)	Retry in 30s once

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.

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)

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "add subtitles in Spanish 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 platforms.

Common Workflows

Quick edit: Upload → "add subtitles in Spanish 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.

Comments

Loading comments...