Reels Maker Automatic

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

Security Scan

The skill's instructions generally match an auto-editing reels service, but there are small inconsistencies (metadata about a config path) and operational details (attribution headers and platform auto-detection) that could require extra filesystem or credential access; review before installing.

Purpose & Capability

The name/description (auto-edit short reels) align with the runtime instructions to upload video, create sessions, render, and return download URLs. Requesting a single service token (NEMO_TOKEN) is appropriate for this purpose. However, the SKILL.md frontmatter declares a config path (~/.config/nemovideo/) while the registry metadata lists no required config paths — this mismatch is unexplained and worth confirming.

Instruction Scope

Instructions stay largely within the editing/rendering scope: create/get a token, create a session, upload files, initiate renders, poll for job completion. Two items to note: (1) every request must include attribution headers and one header value ('X-Skill-Platform') is said to be auto-detected from the install path — that implies the agent may need to inspect its install path or environment; (2) the skill instructs generating an anonymous token when NEMO_TOKEN is absent and to persist/use that token (7-day expiry). Both behaviors are plausible but expand what the agent must access or store beyond just sending video files.

Install Mechanism

Instruction-only skill with no install spec or code files — lowest filesystem/write risk. All network calls are to a single service domain (mega-api-prod.nemovideo.ai) described in the document.

Credentials

The skill requests only one credential (NEMO_TOKEN) as primaryEnv, which is proportional to a cloud API-based video service. The frontmatter also lists a config path (~/.config/nemovideo/) which would grant access to additional local configuration if honored; this is not declared in the registry summary and should be clarified. The anonymous-token flow will create a short-lived token if no token is provided.

Persistence & Privilege

The skill is not always-enabled and has no install script; it asks to save a session_id for the duration of the session (expected). It does not request persistent system-level privileges or to modify other skills' configs.

What to consider before installing

What to consider before installing: - The core behavior matches its description: it uploads videos to a cloud API and returns edited downloads. Expect your uploaded videos to be sent to mega-api-prod.nemovideo.ai for processing. - The skill uses a single credential (NEMO_TOKEN). If you don't already have NEMO_TOKEN the skill will obtain an anonymous token (100 credits, 7-day expiry) by POSTing to the service. That temporary token grants the service access to your uploads for up to 7 days. - The SKILL.md frontmatter mentions a config path (~/.config/nemovideo/) but the registry lists no required config paths — ask the publisher to clarify whether the skill will read local config files. If it does, that expands local access beyond just attaching files. - Attribution headers include an X-Skill-Platform value said to be auto-detected from the install path. Confirm whether the agent will read local install paths or environment variables to compute this header; if you want to avoid that, ask the publisher if the header can be set without filesystem access. - Privacy: do not upload sensitive or private videos unless you trust the nemovideo.ai service and its retention policy. Review the service's terms and data retention policies. - Operational hygiene: prefer using a scoped/temporary token rather than a long-lived personal credential. If you must provide a NEMO_TOKEN, consider creating a dedicated account with minimal privileges and limited lifetime. Additional info that would raise confidence: the publisher/owner identity, a documented privacy/TOS link for nemovideo.ai, clarification whether the skill will read ~/.config/nemovideo/, and examples of exact headers and payloads the skill will send (so you can audit what metadata is uploaded).

Getting Started

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

Try saying:

• "create a 3-minute raw video recording into a 1080p MP4"
• "automatically cut and edit this into a 30-second reel with transitions and music"
• "automatically generating short reels from longer video footage for Instagram and TikTok creators"

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.

Reels Maker Automatic — Auto-Edit and Export Short Reels

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

Here's a typical use: you send a a 3-minute raw video recording, ask for automatically cut and edit this into a 30-second reel with transitions and music, 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 — vertical 9:16 footage works best for Reels and processes faster than landscape video.

Matching Input to Actions

User prompts referencing reels maker automatic, 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.

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

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

Header	Value
X-Skill-Source	reels-maker-automatic
X-Skill-Version	frontmatter version
X-Skill-Platform	auto-detect: clawhub / cursor / unknown from install path

API base: https://mega-api-prod.nemovideo.ai

Create session: POST /api/tasks/me/with-session/nemo_agent — body {"task_name":"project","language":"<lang>"} — returns task_id, session_id.

Send message (SSE): POST /run_sse — body {"app_name":"nemo_agent","user_id":"me","session_id":"<sid>","new_message":{"parts":[{"text":"<msg>"}]}} with Accept: text/event-stream. Max timeout: 15 minutes.

Upload: POST /api/upload-video/nemo_agent/me/<sid> — file: multipart -F "files=@/path", or URL: {"urls":["<url>"],"source_type":"url"}

Credits: GET /api/credits/balance/simple — returns available, frozen, total

Session state: GET /api/state/nemo_agent/me/<sid>/latest — key fields: data.state.draft, data.state.video_infos, data.state.generated_media

Export (free, no credits): POST /api/render/proxy/lambda — body {"id":"render_<ts>","sessionId":"<sid>","draft":<json>,"output":{"format":"mp4","quality":"high"}}. Poll GET /api/render/proxy/lambda/<id> every 30s until status = completed. Download URL at output.url.

Supported formats: mp4, mov, avi, webm, mkv, jpg, png, gif, webp, mp3, wav, m4a, aac.

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

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

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.

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)

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "automatically cut and edit this into a 30-second reel with transitions and music" — 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 the best compatibility across Instagram, TikTok, and YouTube Shorts.

Common Workflows

Quick edit: Upload → "automatically cut and edit this into a 30-second reel with transitions and music" → 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.