Gif Video Maker Free Download

v1.0.0

convert images or video clips into shareable MP4 videos with this skill. Works with GIF, MP4, MOV, WebM files up to 200MB. social media creators use it for c...

0· 73·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 mhogan2013-9/gif-video-maker-free-download.

Previewing Install & Setup.
Prompt PreviewInstall & Setup
Install the skill "Gif Video Maker Free Download" (mhogan2013-9/gif-video-maker-free-download) from ClawHub.
Skill page: https://clawhub.ai/mhogan2013-9/gif-video-maker-free-download
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 gif-video-maker-free-download

ClawHub CLI

Package manager switcher

npx clawhub@latest install gif-video-maker-free-download
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
Name/description, required env var (NEMO_TOKEN), and the SKILL.md all describe using the same nemovideo cloud API for video rendering. The declared API endpoints, required Authorization header, and upload/render flows are consistent with a remote conversion service.
Instruction Scope
The runtime instructions focus on creating/using an anonymous or existing NEMO_TOKEN, opening a session, uploading media, reading SSE render progress, and polling state. They instruct network calls to the stated API and file uploads for user media. The instructions do not request unrelated system files, shell history, or other credentials.
Install Mechanism
No install spec or code files are present (instruction-only). Nothing is downloaded or written by an installer in the metadata, which minimizes on-disk risk.
Credentials
Only NEMO_TOKEN is declared as required and is directly used for API auth, which is proportionate. SKILL.md also provides an anonymous-token flow to obtain a token if absent. The metadata lists a config path (~/.config/nemovideo/) but the instructions do not explicitly require reading arbitrary local config — this is likely intended for storing session/token data but should be confirmed by the maintainer.
Persistence & Privilege
The skill is not always-enabled and does not request elevated platform privileges or attempt to modify other skills. It describes saving session_id and using session tokens for rendering, which is normal for a session-based API client.
Assessment
This skill acts as a thin client for the nemovideo cloud service: it will upload any media you send to that third-party API and will use or generate a NEMO_TOKEN to authenticate. Before installing, consider whether you are comfortable uploading the types of files you will send (no special handling of sensitive data is described). If you want to limit impact: (1) create a dedicated/throwaway account or anonymous token rather than using personal service credentials, (2) avoid uploading sensitive images/audio, (3) verify the api domain (mega-api-prod.nemovideo.ai) and the service's privacy policy, and (4) confirm where session tokens are stored (the metadata lists ~/.config/nemovideo/) and whether you can remove them later. Overall the skill is coherent with its stated purpose and does not request unrelated secrets or installs.

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

Runtime requirements

🎞️ Clawdis
EnvNEMO_TOKEN
Primary envNEMO_TOKEN
latestvk972nnxwttrny33chkxeg0rbwd8581m4
73downloads
0stars
1versions
Updated 6d ago
v1.0.0
MIT-0

Getting Started

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

Try saying:

  • "convert my images or video clips"
  • "export 1080p MP4"
  • "convert this GIF into an MP4"

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.

GIF Video Maker Free Download — Convert GIFs to MP4 Videos

Drop your images or video clips in the chat and tell me what you need. I'll handle the GIF to video conversion on cloud GPUs — you don't need anything installed locally.

Here's a typical use: you send a a 10-frame looping GIF animation, ask for convert this GIF into an MP4 video with sound, and about 20-40 seconds later you've got a MP4 file ready to download. The whole thing runs at 1080p by default.

One thing worth knowing — shorter GIFs under 5 seconds convert in under 10 seconds.

Matching Input to Actions

User prompts referencing gif video maker free download, 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.

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

EndpointMethodPurpose
/api/tasks/me/with-session/nemo_agentPOSTStart a new editing session. Body: {"task_name":"project","language":"<lang>"}. Returns session_id.
/run_ssePOSTSend 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>POSTUpload a file (multipart) or URL.
/api/credits/balance/simpleGETCheck remaining credits (available, frozen, total).
/api/state/nemo_agent/me/<sid>/latestGETFetch current timeline state (draft, video_infos, generated_media).
/api/render/proxy/lambdaPOSTStart 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:

HeaderValue
X-Skill-Sourcegif-video-maker-free-download
X-Skill-Versionfrontmatter version
X-Skill-Platformauto-detect: clawhub / cursor / unknown from install path

Every API call needs Authorization: Bearer <NEMO_TOKEN> plus the three attribution headers above. If any header is missing, exports return 402.

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

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.

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

Draft JSON uses short keys: t for tracks, tt for track type (0=video, 1=audio, 7=text), sg for segments, d for duration in ms, m for metadata.

Example timeline summary:

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 → "convert this GIF into an MP4 video with sound" → 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.

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "convert this GIF into an MP4 video with sound" — concrete instructions get better results.

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

Export as MP4 for widest compatibility across all platforms.

Comments

Loading comments...