Editor Ipad

v1.0.0

Skip the learning curve of professional editing software. Describe what you want — trim the clip, add transitions, and export for Instagram — and get edited...

⭐ 0· 55·0 current·0 all-time

by@mory128

OpenClaw Prompt Flow

Install with OpenClaw

Best for remote or guided setup. Copy the exact prompt, then paste it into OpenClaw for mory128/editor-ipad.

Previewing Install & Setup.

Prompt PreviewInstall & Setup

Install the skill "Editor Ipad" (mory128/editor-ipad) from ClawHub.
Skill page: https://clawhub.ai/mory128/editor-ipad
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 editor-ipad

ClawHub CLI

Package manager switcher

npx clawhub@latest install editor-ipad

Security Scan

VirusTotal

Benign

View report →

OpenClaw

Suspicious

medium confidence

✓

Purpose & Capability

Name/description: remote mobile video editing for iPad. Declared primary credential NEMO_TOKEN and runtime endpoints in SKILL.md all relate to a cloud video processing API — this is proportionate to the stated purpose.

ℹ

Instruction Scope

Instructions only call the service's REST endpoints and require uploading user media, creating sessions, and polling render status — all expected. The SKILL.md explicitly says not to print tokens or raw JSON. No instructions ask the agent to read unrelated system files or other credentials.

✓

Install Mechanism

Instruction-only skill with no install spec and no bundled code or binaries — lowest-risk install model. All runtime behavior is network calls to the listed API host.

Credentials

The skill requires a single API credential (NEMO_TOKEN), which is appropriate. However, the SKILL.md frontmatter also lists a config path (~/.config/nemovideo/) while the registry metadata said no required config paths — this mismatch is unexplained and means the skill may read or look for local config. Confirm why local config access is needed and whether the skill will read or write files there.

✓

Persistence & Privilege

always:false and standard autonomous invocation settings. Nothing requests permanent system-level privileges or modifications to other skills. Autonomous invocation is permitted by default (normal), but always:false reduces persistent presence risk.

What to consider before installing

This skill appears to be a thin client for a cloud video-editing API and asks for one credential (NEMO_TOKEN) — which is reasonable for the described function. Before installing: 1) Verify the service domain (mega-api-prod.nemovideo.ai) and the skill author — the registry lists an owner ID but no homepage; confirm you trust that backend. 2) Note the discrepancy: SKILL.md frontmatter mentions ~/.config/nemovideo/ (local config access) while registry metadata lists no config paths — ask the author why the skill needs local config access and what it stores/reads there. 3) If you try it, prefer using the anonymous/free token flow (the skill can request a short-lived anonymous token) instead of providing long-lived account credentials. 4) Be aware you will be uploading media to a third-party service; do not upload sensitive or private videos unless you trust the provider. 5) If you need higher assurance, request the maintainer to provide: a) a documented privacy/data-retention policy for uploaded media, b) a canonical homepage or source repo, and c) clarification about the local config path usage. If those are not provided, treat this skill as potentially risky and avoid supplying sensitive content or permanent credentials.

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

Runtime requirements

✂️ Clawdis

EnvNEMO_TOKEN

Primary envNEMO_TOKEN

latestvk970hghf2tkdkvc8zrcnmqedbx8511c2

55downloads

0stars

1versions

Updated 1w ago

v1.0.0

MIT-0

Getting Started

Got video clips to work with? Send it over and tell me what you need — I'll take care of the AI mobile editing.

Try saying:

"edit a 2-minute video recorded on iPhone into a 1080p MP4"
"trim the clip, add transitions, and export for Instagram"
"editing videos on iPad without desktop software for iPad 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.

Editor iPad — Edit and Export Videos on iPad

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

A quick example: upload a 2-minute video recorded on iPhone, type "trim the clip, add transitions, and export for Instagram", 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 on mobile connections.

Matching Input to Actions

User prompts referencing editor ipad, 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.

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

Header	Value
`X-Skill-Source`	`editor-ipad`
`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.

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

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.

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)

Common Workflows

Quick edit: Upload → "trim the clip, add transitions, and export for Instagram" → 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.

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "trim the clip, add transitions, and export for Instagram" — concrete instructions get better results.

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

Export as MP4 for widest compatibility across social platforms and devices.

Comments

Loading comments...