Free Wechat Video

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

Security Scan

The skill is an instruction-only wrapper for a third-party video-editing API (nemovideo.ai) and its declared requirements largely match its stated purpose, though there are a few small inconsistencies and privacy considerations to review before use.

Purpose & Capability

Name/description (WeChat-focused video editing) align with the SKILL.md instructions which call a remote video-editing API and require a NEMO_TOKEN. One inconsistency: the registry metadata lists no required config paths, but the SKILL.md frontmatter includes a configPaths entry (~/.config/nemovideo/). This is plausible but mismatched metadata that should be corrected.

Instruction Scope

The SKILL.md instructs the agent to create sessions, upload user video files, start render jobs, poll status, and stream SSE — all consistent with a cloud video service. It also instructs the agent to automatically obtain an anonymous token if NEMO_TOKEN is missing and to 'keep technical details out of the chat' (which is a UX choice but reduces transparency). The agent is not told to read unrelated local files or secrets. The requirement to auto-detect X-Skill-Platform from an install path may be problematic for an instruction-only skill with no install path.

Install Mechanism

No install spec or code is present (instruction-only), so nothing is written to disk. This is the lowest-risk install model.

Credentials

Only one credential is requested (NEMO_TOKEN) which is proportionate for a cloud API. The SKILL.md also documents how to obtain an anonymous token if none is provided — reasonable for usability. No unrelated secrets (AWS keys, SSH keys, etc.) are requested.

Persistence & Privilege

The skill does not request always:true, does not ask to modify other skills, and provides no install-time persistence. Autonomous invocation is allowed (platform default) but not combined with elevated privileges.

Assessment

This skill sends uploaded videos to an external service (mega-api-prod.nemovideo.ai) and will use NEMO_TOKEN if present or automatically fetch an anonymous token. Before installing or using: (1) confirm you are comfortable uploading the specific videos (avoid sensitive/private content), (2) verify the external service/endpoint and its privacy terms (the skill source is unknown and no homepage is provided), (3) note the small metadata mismatch (SKILL.md references ~/.config/nemovideo/ while registry metadata does not) and the instruction to hide technical details from chat — ask the agent to explicitly tell users when files are being uploaded and where, and (4) if you require auditability, request the skill log or show network actions rather than suppressing them. If any of these are unacceptable, do not install or run the skill.

Getting Started

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

Try saying:

• "create a 30-second MP4 clip for a WeChat Moments post into a 1080p MP4"
• "trim this video and add subtitles for WeChat sharing"
• "creating short shareable videos for WeChat Moments or chats for WeChat users and 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 WeChat Video — Create and Share WeChat Videos

Drop your video clips in the chat and tell me what you need. I'll handle the AI video creation on cloud GPUs — you don't need anything installed locally.

Here's a typical use: you send a a 30-second MP4 clip for a WeChat Moments post, ask for trim this video and add subtitles for WeChat sharing, and about 30-60 seconds later you've got a MP4 file ready to download. The whole thing runs at 1080p by default.

One thing worth knowing — keep videos under 25MB for smooth WeChat sharing without compression issues.

Matching Input to Actions

User prompts referencing free wechat video, 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	free-wechat-video
X-Skill-Version	frontmatter version
X-Skill-Platform	auto-detect: clawhub / cursor / unknown from install path

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 Codes

• 0 — success, continue normally
• 1001 — token expired or invalid; re-acquire via /api/auth/anonymous-token
• 1002 — session not found; create a new one
• 2001 — out of credits; anonymous users get a registration link with ?bind=<id>, registered users top up
• 4001 — unsupported file type; show accepted formats
• 4002 — file too large; suggest compressing or trimming
• 400 — missing X-Client-Id; generate one and retry
• 402 — free plan export blocked; not a credit issue, subscription tier
• 429 — rate limited; wait 30s and retry 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)

Common Workflows

Quick edit: Upload → "trim this video and add subtitles for WeChat sharing" → 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.

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "trim this video and add subtitles for WeChat sharing" — concrete instructions get better results.

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

Export as MP4 with H.264 codec for best compatibility with WeChat playback.