Kre Video

Turn a 60-second raw phone recording into 1080p edited video clips just by typing what you need. Whether it's creating polished videos from raw footage or qu...

Security Scan

The skill's requests and runtime instructions align with its stated purpose (cloud video editing) but there are small metadata inconsistencies and the skill will upload user video files and use a bearer token for a third‑party API — review before sending sensitive content.

Purpose & Capability

Name/description (AI cloud video editing) match the runtime instructions and required credential (NEMO_TOKEN). One inconsistency: the registry metadata reported no required config paths, but the SKILL.md frontmatter lists a config path (~/.config/nemovideo/), which suggests the skill might read or write a local config directory even though the top-level manifest did not declare it.

Instruction Scope

SKILL.md confines actions to creating sessions, uploading user-provided video files, streaming SSE messages, polling session/state endpoints, and exporting results via the listed API. It does not direct reading arbitrary system files or unrelated env vars. It does instruct uploads of local files (multipart -F "files=@/path"), so user files will be transmitted to the third-party API.

Install Mechanism

No install spec or code is present (instruction-only), so nothing is written to disk by an installer. Low install surface.

Credentials

Only one credential (NEMO_TOKEN) is declared as required, which is proportionate to a cloud-rendering service. The SKILL.md also documents an anonymous-token flow to acquire a short-lived token. The earlier-mentioned discrepancy about a config path in the SKILL.md frontmatter (but not in the registry metadata) is worth noting because it implies possible local config reads/writes for token caching.

Persistence & Privilege

always:false (no forced persistence). The skill can be invoked autonomously (default platform behavior) but does not request unusual platform privileges or permanent presence. It does not ask to modify other skills or system-wide settings.

Assessment

This skill appears to do what it says: it will upload videos you provide to mega-api-prod.nemovideo.ai and use a NEMO_TOKEN bearer token to create and retrieve rendered videos. Before installing/using it: 1) Only upload content you are comfortable sending to a third party and check whether the vendor/service is trustworthy (no homepage or publisher info is provided). 2) Expect the skill to call network endpoints and to store session IDs (the SKILL.md suggests a local config path for caching even though the manifest omitted it) — if you don't want local config read/write, ask the publisher or avoid use. 3) If you prefer minimal exposure, use the anonymous-token flow or a limited/throwaway token and revoke it after use. 4) The skill will not install binaries, but it will transmit your files and tokens to the listed domain — verify the domain (mega-api-prod.nemovideo.ai) and privacy terms. 5) Because the package source and homepage are unknown, exercise caution and consider testing with non-sensitive sample clips first. I rated confidence medium because the skill is internally consistent but the lack of publisher/homepage and the metadata/configPath mismatch reduce confidence; provide the publisher or repo info to raise confidence.

Getting Started

Send me your raw video clips and I'll handle the AI video creation. Or just describe what you're after.

Try saying:

• "create a 60-second raw phone recording into a 1080p MP4"
• "create a short highlight video with music and transitions"
• "creating polished videos from raw footage for content 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.

Kre Video — Create and Export Polished Videos

Send me your raw video clips and describe the result you want. The AI video creation runs on remote GPU nodes — nothing to install on your machine.

A quick example: upload a 60-second raw phone recording, type "create a short highlight video with music and transitions", and you'll get a 1080p MP4 back in roughly 30-60 seconds. All rendering happens server-side.

Worth noting: shorter input clips under 2 minutes yield the fastest results.

Matching Input to Actions

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

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

Header	Value
X-Skill-Source	kre-video
X-Skill-Version	frontmatter version
X-Skill-Platform	auto-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.

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.

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.

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)

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

Common Workflows

Quick edit: Upload → "create a short highlight video with music and transitions" → 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 "create a short highlight video with music and transitions" — concrete instructions get better results.

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

Export as MP4 for widest compatibility.