Story Video

create images or clips into narrative story video with this skill. Works with MP4, MOV, JPG, PNG files up to 500MB. social media creators use it for turning...

Security Scan

The skill's requirements and instructions mostly align with its stated purpose (cloud video rendering) and request only one credential (NEMO_TOKEN), but there are a few minor metadata inconsistencies and normal privacy considerations to review before use.

Purpose & Capability

The skill is a cloud-backed video rendering tool and only requests a single service token (NEMO_TOKEN), which is coherent. Minor inconsistency: the skill frontmatter mentions a config path (~/.config/nemovideo/) while the registry metadata reported no required config paths.

Instruction Scope

SKILL.md confines runtime actions to the nemo service: checking/obtaining NEMO_TOKEN, creating sessions, uploading media, SSE chat, and export polling. It does not instruct reading arbitrary system files or unrelated credentials. It does instruct automatic anonymous-token acquisition if env var missing, which is consistent with the cloud workflow.

Install Mechanism

Instruction-only skill with no install spec or downloadable artifacts — lowest install risk.

Credentials

Only NEMO_TOKEN is required (declared as primaryEnv), which is proportional. The frontmatter's configPaths entry suggests potential local config access (may contain tokens), but the SKILL.md does not explicitly instruct reading that path — this mismatch should be clarified.

Persistence & Privilege

The skill is not always-enabled and does not request system-wide persistence or modify other skills. It keeps session state for its own operations, which is appropriate for a cloud-rendering workflow.

Assessment

This skill will send your uploaded media and requests to a third‑party API (https://mega-api-prod.nemovideo.ai) and uses a service token (NEMO_TOKEN). Before installing, consider: 1) only provide a long‑lived NEMO_TOKEN if you trust the provider; prefer allowing the skill to obtain an anonymous short‑lived token if you want limited exposure; 2) the skill may reference a local config path in its metadata (~/.config/nemovideo/) — confirm whether it actually reads that path if you keep secrets there; 3) the skill will transmit files (up to 500MB) off your device — avoid sending sensitive or private material unless you accept the provider's privacy policy; 4) no code is installed locally and the skill runs via network calls, so the main risk is data sent to the external service. If any of these concerns are unacceptable, do not install or provide a persistent token.

Getting Started

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

Try saying:

• "create my images or clips"
• "export 1080p MP4"
• "turn my photos and audio into"

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.

Story Video — Turn Photos Into Story Videos

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

Here's a typical use: you send a five travel photos and a voice note, ask for turn my photos and audio into a short narrative story video with transitions and music, and about 1-2 minutes later you've got a MP4 file ready to download. The whole thing runs at 1080p by default.

One thing worth knowing — adding a voiceover or audio clip helps the AI pace transitions more naturally.

Matching Input to Actions

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

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

1. Session — POST /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. Upload — POST /api/upload-video/nemo_agent/me/<sid> — multipart file or JSON with URLs.
4. Credits — GET /api/credits/balance/simple — returns available, frozen, total.
5. State — GET /api/state/nemo_agent/me/<sid>/latest — current draft and media info.
6. Export — POST /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.

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

Header	Value
X-Skill-Source	story-video
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.

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)

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

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.

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

Common Workflows

Quick edit: Upload → "turn my photos and audio into a short narrative story video with transitions and music" → 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 "turn my photos and audio into a short narrative story video with transitions and music" — 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 social platforms and devices.