Free Image Editing

v1.0.0

Skip the learning curve of professional editing software. Describe what you want — remove the background, adjust brightness, and add text overlay — and get e...

⭐ 0· 103·0 current·0 all-time

by@vynbosserman65

OpenClaw Prompt Flow

Install with OpenClaw

Best for remote or guided setup. Copy the exact prompt, then paste it into OpenClaw for vynbosserman65/free-image-editing.

Previewing Install & Setup.

Prompt PreviewInstall & Setup

Install the skill "Free Image Editing" (vynbosserman65/free-image-editing) from ClawHub.
Skill page: https://clawhub.ai/vynbosserman65/free-image-editing
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

Canonical install target

openclaw skills install vynbosserman65/free-image-editing

ClawHub CLI

Package manager switcher

npx clawhub@latest install free-image-editing

Security Scan

VirusTotal

Benign

View report →

OpenClaw

Benign

medium confidence

ℹ

Purpose & Capability

Name/description (image editing/export to video) aligns with the runtime instructions that call an external rendering API and upload image/video/audio files. However the SKILL.md frontmatter declares a required config path (~/.config/nemovideo/) while the registry metadata earlier showed no required config paths — this mismatch is inconsistent and should be clarified.

ℹ

Instruction Scope

The SKILL.md explicitly instructs the agent to upload user files and stream edits via SSE to mega-api-prod.nemovideo.ai, create sessions, poll render status, and — if no env token is present — obtain an anonymous token by POSTing a generated client UUID. Those actions are within scope for a remote editing service, but they do require transmitting user images/audio/video to a third-party service; the instructions do not attempt to read unrelated local files or other credentials.

✓

Install Mechanism

Instruction-only skill with no install spec or code files — no local binaries or archives are downloaded or written by the skill itself, which reduces installation risk.

ℹ

Credentials

The only declared required env var is NEMO_TOKEN (primary credential), which is appropriate for a remote API. The skill also implements an anonymous-token flow so it can operate without a pre-provided token. There is a minor mismatch between the registry's declared required config paths (none) and the SKILL.md frontmatter listing ~/.config/nemovideo/ — this could indicate sloppy metadata or an unannounced local config dependency.

✓

Persistence & Privilege

The skill does not request always:true and does not modify system-wide settings; it operates per-session against an external API and does not request elevated agent presence.

Assessment

This skill sends any images, audio, or video you upload to an external service (mega-api-prod.nemovideo.ai) for processing. Only install/use it if you trust that service and are comfortable with those uploads. Do not place a long-lived NEMO_TOKEN in an environment you don't control unless you trust the publisher; prefer using the anonymous-token flow for sensitive use, and verify the domain and privacy/retention policy of nemovideo.ai. Also ask the publisher to clarify the config-path discrepancy (~/.config/nemovideo/ listed in SKILL.md but not in registry metadata) before granting broad access.

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

Runtime requirements

🖼️ Clawdis

EnvNEMO_TOKEN

Primary envNEMO_TOKEN

latestvk97138nrcgam780cb3jm15s1jd8589z4

103downloads

0stars

1versions

Updated 6d ago

v1.0.0

MIT-0

Getting Started

Ready when you are. Drop your images or photos here or describe what you want to make.

Try saying:

"edit a product photo or personal snapshot into a 1080p MP4"
"remove the background, adjust brightness, and add text overlay"
"editing and animating images into shareable video content for social media 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.

Free Image Editing — Edit Images and Export Videos

Send me your images or photos and describe the result you want. The AI image editing runs on remote GPU nodes — nothing to install on your machine.

A quick example: upload a product photo or personal snapshot, type "remove the background, adjust brightness, and add text overlay", and you'll get a 1080p MP4 back in roughly 20-40 seconds. All rendering happens server-side.

Worth noting: smaller image files process faster and produce cleaner output.

Matching Input to Actions

User prompts referencing free image editing, 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.

Headers are derived from this file's YAML frontmatter. X-Skill-Source is free-image-editing, 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).

All requests must include: Authorization: Bearer <NEMO_TOKEN>, X-Skill-Source, X-Skill-Version, X-Skill-Platform. Missing attribution headers will cause export to fail with 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 "remove the background, adjust brightness, and add text overlay" — concrete instructions get better results.

Max file size is 200MB. Stick to JPG, PNG, WEBP, GIF for the smoothest experience.

Export as MP4 for widest compatibility across platforms.

Common Workflows

Quick edit: Upload → "remove the background, adjust brightness, and add text overlay" → Download MP4. Takes 20-40 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...