With Ai Ai

v1.0.0

Get AI-processed videos ready to post, without touching a single slider. Upload your video clips (MP4, MOV, AVI, WebM, up to 500MB), say something like "enha...

⭐ 0· 85·0 current·0 all-time

by@mhogan2013-9

OpenClaw Prompt Flow

Install with OpenClaw

Best for remote or guided setup. Copy the exact prompt, then paste it into OpenClaw for mhogan2013-9/with-ai-ai.

Previewing Install & Setup.

Prompt PreviewInstall & Setup

Install the skill "With Ai Ai" (mhogan2013-9/with-ai-ai) from ClawHub.
Skill page: https://clawhub.ai/mhogan2013-9/with-ai-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 with-ai-ai

ClawHub CLI

Package manager switcher

npx clawhub@latest install with-ai-ai

Security Scan

VirusTotal

Benign

View report →

OpenClaw

Benign

high confidence

ℹ

Purpose & Capability

The name/description (AI video enhancement) match the declared need for a service token (NEMO_TOKEN) and the SKILL.md describes upload, session creation, SSE, and export endpoints for a remote rendering service. One incoherence: registry metadata reported 'Required config paths: none' while the skill frontmatter includes a configPaths entry (~/.config/nemovideo/). This is likely a minor metadata mismatch but should be clarified.

✓

Instruction Scope

SKILL.md instructs the agent to obtain or use NEMO_TOKEN, create sessions, upload files, stream SSE, poll state, and include attribution headers. All of these actions are within the stated purpose (upload/process/download video). The skill tells the agent to store session_id and token for future requests — expected for a sessioned API — and to avoid showing raw tokens to users.

✓

Install Mechanism

No install spec or code files are present (instruction-only). This is low-risk: nothing will be automatically downloaded or written to disk by an installer.

ℹ

Credentials

The only required credential is NEMO_TOKEN (declared as the primary credential), which is proportional to a cloud video processing integration. The skill will generate an anonymous token automatically if NEMO_TOKEN isn't present — this behavior is explained in the instructions and is reasonable. The earlier metadata/configPaths mismatch is the only proportionality oddity (skill frontmatter lists a config path even though registry said none).

✓

Persistence & Privilege

The skill is not always-on and does not request elevated platform privileges. It does instruct the agent to persist session_id/token for session management, which is normal for an API-backed tool and confined to its own session state.

Assessment

This skill uploads your videos to a remote service (mega-api-prod.nemovideo.ai) and uses a bearer token (NEMO_TOKEN) to authenticate; if you don't provide one it will create a short-lived anonymous token for you. Before installing, consider: 1) Privacy: your video/audio will be transmitted to and processed by a third party—review their privacy/terms and avoid uploading sensitive content. 2) Credentials: provide a token only if you trust the service; otherwise let the skill use the anonymous token or create a throwaway account. 3) Metadata mismatch: the registry vs. SKILL.md disagree about a config path (~/.config/nemovideo/); ask the publisher to clarify whether the skill will read or write that config directory. 4) No installer or code is included, which reduces supply-chain risk, but also means there is no published source/homepage to audit—prefer skills with a verifiable homepage or repo. If you need higher assurance, request the skill's source or a publisher identity before using it with private content or a production token.

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

Runtime requirements

🤖 Clawdis

EnvNEMO_TOKEN

Primary envNEMO_TOKEN

latestvk97fhwy3ck1xzmh5mrr1pgepa584n1jk

85downloads

0stars

1versions

Updated 2w ago

v1.0.0

MIT-0

Getting Started

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

Try saying:

"enhance a 2-minute raw video clip into a 1080p MP4"
"enhance this video with AI and improve quality automatically"
"improving and editing videos using AI automation for content creators"

First-Time Connection

When a user first opens this skill, connect to the processing backend automatically. Briefly let them know (e.g. "Setting up...").

Authentication: Check if NEMO_TOKEN is set in the environment. If it is, skip to step 2.

Obtain a free token: Generate a random UUID as client identifier. POST to https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with header X-Client-Id set to that UUID. The response data.token is your NEMO_TOKEN — 100 free credits, valid 7 days.
Create a session: POST to https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Authorization: Bearer <token>, Content-Type: application/json, and body {"task_name":"project","language":"<detected>"}. Store the returned session_id for all subsequent requests.

Keep setup communication brief. Don't display raw API responses or token values to the user.

With AI — Edit Videos Using AI

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

Say you have a 2-minute raw video clip and want to enhance this video with AI and improve quality automatically — the backend processes it in about 30-60 seconds and hands you a 1080p MP4.

Tip: shorter clips under 60 seconds process significantly faster.

Matching Input to Actions

User prompts referencing with ai 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.

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

Header	Value
`X-Skill-Source`	`with-ai-ai`
`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)

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "enhance this video with AI and improve quality automatically" — 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.

Common Workflows

Quick edit: Upload → "enhance this video with AI and improve quality automatically" → 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...