Juan 22 Video Generator Free

v1.0.0

Turn a series of product photos or short clips into 1080p generated MP4 videos just by typing what you need. Whether it's generating videos from images or cl...

0· 69·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 tk8544-b/juan-22-video-generator-free.

Previewing Install & Setup.
Prompt PreviewInstall & Setup
Install the skill "Juan 22 Video Generator Free" (tk8544-b/juan-22-video-generator-free) from ClawHub.
Skill page: https://clawhub.ai/tk8544-b/juan-22-video-generator-free
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 juan-22-video-generator-free

ClawHub CLI

Package manager switcher

npx clawhub@latest install juan-22-video-generator-free
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
Name/description and runtime instructions align: a cloud video-generation skill that needs a NEMO_TOKEN and talks to nemovideo.ai. One minor inconsistency: the registry metadata lists no required config paths, but the SKILL.md frontmatter includes configPaths ("~/.config/nemovideo/"). That mismatch is likely an authoring oversight rather than malicious, but it should be clarified.
Instruction Scope
SKILL.md keeps scope to uploading media, creating sessions, streaming SSE edits, polling render status, and exporting results to an external API. It also instructs the agent to (a) check NEMO_TOKEN, (b) if missing, generate a UUID and call an anonymous-token endpoint to obtain a token, and (c) read the skill's own frontmatter and the install path to set attribution headers. These are expected for the stated purpose, but the anonymous-token fetch and automatic network activity are operational details users should be aware of (uploads and media are sent to an external service).
Install Mechanism
Instruction-only skill with no install spec or code files — low install risk. Nothing is downloaded or written by an installer in the package itself.
Credentials
Only NEMO_TOKEN is declared as required and used for API authorization; this is appropriate for a cloud-rendering service. The skill will also auto-obtain an anonymous NEMO_TOKEN if none is present (network call), which is consistent with its design but worth noting if you prefer explicit credential control.
Persistence & Privilege
Skill does not request always:true and does not modify other skills or system-wide settings. It keeps session_id for operation lifetime (normal) and does not claim persistent elevated privileges.
Assessment
This skill appears to do what it says: it uploads images/clips to an external nemovideo.ai service and returns rendered MP4s. Before installing, consider: (1) Privacy: any media you upload goes to an external backend — do not upload sensitive images. (2) Tokens: the skill will use NEMO_TOKEN if you provide one, otherwise it will automatically request an anonymous token from https://mega-api-prod.nemovideo.ai; if you prefer control, set NEMO_TOKEN yourself. (3) Metadata mismatch: the SKILL.md lists a config path (~/.config/nemovideo/) even though registry metadata did not — ask the author to clarify whether the skill will read that directory. (4) Verify the service's legitimacy and privacy/terms for content storage and retention. If any of the above are unacceptable, do not install or restrict the skill's network access.

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

Runtime requirements

🎬 Clawdis
EnvNEMO_TOKEN
Primary envNEMO_TOKEN
latestvk975hrhqjevs2t0jnesdzqbqb584ydjh
69downloads
0stars
1versions
Updated 1w ago
v1.0.0
MIT-0

Getting Started

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

Try saying:

  • "generate my images or clips"
  • "export 1080p MP4"
  • "generate a free video from my"

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.

Juan 22 Video Generator Free — Generate Videos From Images Free

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

Say you have a series of product photos or short clips and want to generate a free video from my images with music and transitions — the backend processes it in about 1-2 minutes and hands you a 1080p MP4.

Tip: shorter clips and fewer images process faster and reduce wait time.

Matching Input to Actions

User prompts referencing juan 22 video generator free, 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.

All calls go to https://mega-api-prod.nemovideo.ai. The main endpoints:

  1. SessionPOST /api/tasks/me/with-session/nemo_agent with {"task_name":"project","language":"<lang>"}. Gives you a session_id.
  2. Chat (SSE)POST /run_sse with session_id and your message in new_message.parts[0].text. Set Accept: text/event-stream. Up to 15 min.
  3. UploadPOST /api/upload-video/nemo_agent/me/<sid> — multipart file or JSON with URLs.
  4. CreditsGET /api/credits/balance/simple — returns available, frozen, total.
  5. StateGET /api/state/nemo_agent/me/<sid>/latest — current draft and media info.
  6. ExportPOST /api/render/proxy/lambda with render ID and draft JSON. Poll GET /api/render/proxy/lambda/<id> every 30s for completed status and download URL.

Formats: 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: juan-22-video-generator-free
  • X-Skill-Version: from frontmatter version
  • X-Skill-Platform: detect from install path (~/.clawhub/clawhub, ~/.cursor/skills/cursor, else 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.

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)

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

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.

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

Common Workflows

Quick edit: Upload → "generate a free video from my images with music and transitions" → 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 "generate a free video from my images with music and transitions" — concrete instructions get better results.

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

Export as MP4 for widest compatibility across platforms.

Comments

Loading comments...